[x3d-public] X3D minutes 17 MAR 2023: Web3D 2023 Conference Call for Participation CFP, X3D 4.0 editorial comments review
John Carlson
yottzumm at gmail.com
Sat Mar 18 19:09:33 PDT 2023
I am puzzling about how we might validate NavigationInfo.type with XML
schema. Seems like we’ll have to write our own validation rule or provide
a pattern. Which is fine. Goes in X3DJSAIL and friends. My point is we
can import additional rules beyond schema into a binding to provide
extended validation.
While we are discussing JSON schema standards, glTF moves on. With HTML5,
people can invent their own standards. I agree that HTML5/JavaScript is a
mess. Do we have a replacement, or are we going to get sucked into it? I
do like X_ITE. I’m not sure if ES6X3D is a good goal. I’m finding ES6
painful compared to node.js.
React Server Components (RSC) applied to 3D, anyone? Validation?
RSC+Three.js?
Just what is Meta-verse planning? I don’t even know the landscape of the
Metaverse at this point, but Meta’s current web offerings scare (RSC) me.
I think everyone’s fleeing from complexity at this point, right into the
hands of GPT-4. I have not seen any React written with GPT though.
More things to search upon.
Eventually, I’ll write some 3D extensions to bash. I wonder if neovim/lua
will take 3D extensions?
John
On Sat, Mar 18, 2023 at 9:59 AM Brutzman, Donald (Don) (CIV) <
brutzman at nps.edu> wrote:
> Hi John, thanks for your helpful note. Am happy to reply that nearly all
> of these questions have answers online.
>
>
>
> The following mantis issue (which you refer to) is a placeholder, awaiting
> an informal comment made last week. It was added in case there are
> unresolved issues. One way or another it will be handled in the next few
> weeks.
>
> - https://www.web3d.org/member-only/mantis/view.php?id=1437
>
>
>
> geosystem enumeration values are indeed documented formally. Links:
>
>
>
> - X3D Specifications: Schema and DOCTYPE Validation
> - https://www.web3d.org/specifications
> -
> https://www.web3d.org/specifications/X3dSchemaDocumentation4.0/x3d-4.0.html
> -
> https://www.web3d.org/specifications/X3dSchemaDocumentation4.0/x3d-4.0_geoSystemType.html#LinkA2
> -
> https://www.web3d.org/specifications/X3dSchemaDocumentation4.0/x3d-4.0_geoSystemSpatialReferenceFrameValues.html#Link9E
> - Similarly look for geoSystemType and
> geoSystemSpatialReferenceFrameValues in X3DUOM at
> - https://www.web3d.org/specifications/X3dUnifiedObjectModel-4.0.xml
> - We should have formal mappings for these in X3DJSAIL Java, X3DPSAIL
> x3d.py Python, and our JSON encoding, so that X3D programmers do not have
> to rely on string spelling. Wasn’t able to check this, possible followup
> improvement.
>
>
>
> Example excerpt from X3DUOM (with original definitions in X3D XM Schema):
>
>
>
> <SimpleType name="geoSystemSpatialReferenceFrameValues"
> baseType="xs:NMTOKEN" appinfo="geoSystemSpatialReferenceFrameValues are
> allowed enumeration values of spatial reference frames and earth
> ellipsoids, providing first value for geoSystem field. This list is
> unbounded, additional enumeration values are allowed." documentation=
> https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-DIS/Part01/components/geospatial.html#Spatialreferenceframes
> >
>
> <enumeration value="GD" appinfo="Geodetic spatial reference frame
> (latitude/longitude), to be followed by ellipsoid"/>
>
> <enumeration value="UTM" appinfo="Universal Transverse Mercator. One
> further required argument must be supplied for UTM in order to specify the
> zone number (1..60) with optional suffix of "S" may be appended in order to
> specify that the coordinates are in the southern hemisphere. Optional
> arguments can follow."/>
>
> <enumeration value="GC" appinfo="Earth-fixed Geocentric with respect to
> the WGS84 ellipsoid. No additional arguments are supported."/>
>
> <enumeration value="GDC" appinfo="Synonymous to GD, but may be subject to
> future deprecation"/>
>
> <enumeration value="GCC" appinfo="Synonymous to GC, but may be subject to
> future deprecation"/>
>
> </SimpleType>
>
>
>
> As ever for JSON, we await long-promised standardization of a JSON Schema
> before finalizing an X3D JSON Schema.
>
> - https://json-schema.org
>
>
>
> For your comment about N and Northern Hemisphere, please see the X3D
> Architecture specification.
>
>
>
> - 25.2.3 Specifying a spatial reference frame
> -
> https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-IS.review/Part01/components/geospatial.html#SpecifyingSpatialReferenceFrame
> - Excerpted:
> - " *UTM*" - Universal Transverse Mercator. One further required
> argument shall be supplied for UTM in order to specify the zone number
> (1..60). This is given in the form "Z<n>", where <n> is the zone number. An
> optional argument of "S" may be supplied in order to specify that the
> coordinates are in the southern hemisphere (otherwise, northern hemisphere
> will be assumed). A further optional argument may be used to specify the
> ellipsoid using one of the ellipsoid codes that are defined in Table
> 25.3
> <https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-IS.review/Part01/components/geospatial.html#t-earthellipsoids>.
> If no ellipsoid is specified, then "WE" is assumed ( *i.e.*, the WGS84
> ellipsoid). An optional "WGS84" string can be specified if you wish all
> elevations to relative to the WGS84 geoid ( *i.e.*, mean sea level
> (see Table 25.4
> <https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-IS.review/Part01/components/geospatial.html#t-earthgeoids>));
> otherwise, all elevations will be relative to the ellipsoid. An example
> spatial reference frame definition of this format is [ "UTM", "Z10",
> "S", "WGS84" ], for a southern hemisphere UTM spatial reference frame
> in zone 10 with all elevations being with respect to mean sea level.
>
>
>
> *From:* John Carlson <yottzumm at gmail.com>
> *Sent:* Saturday, March 18, 2023 1:23 AM
> *To:* Brutzman, Donald (Don) (CIV) <brutzman at nps.edu>
> *Subject:* Re: [x3d-public] X3D minutes 17 MAR 2023: Web3D 2023
> Conference Call for Participation CFP, X3D 4.0 editorial comments review
>
>
>
> Here’s where geoSystem is discussed, pulled from below. I couldn’t even
> tell what exactly the issue was?
>
>
>
>
> https://www.web3d.org/member-only/mantis/login_page.php?return=%2Fmember-only%2Fmantis%2Fview.php%3Fid%3D1437
>
>
>
> This should be dropped unless there’s unresolved issues.
>
>
>
> Two issues come to mind: making geoSystem a string or enum in JSON so that
> it can be validated with our tools. Can someone offer a solution here?
> A report on validating geoSystem would be helpful. How might we take an
> XML Schema pattern and put it in X3DUOM? Is that it?
>
>
>
> Two, Northern Hemisphere or “N” should be allowed and defaulted.
>
>
>
> On Fri, Mar 17, 2023 at 12:09 PM Brutzman, Donald (Don) (CIV) <
> brutzman at nps.edu> wrote:
>
> Attendees: William Glascoe, Anita Havele, Vince Marchetti, Dick Puk, Doug
> Sanden, Don Brutzman.
>
>
>
> The X3D Working Group meets weekly on Fridays 09-1000 Pacific on Web3D
> Consortium zoom channel. Telcon information:
>
> -
> https://us02web.zoom.us/j/81634670698?pwd=a1VPeU5tN01rc21Oa3hScUlHK0Rxdz09
> <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fus02web.zoom.us%2Fj%2F81634670698%3Fpwd%3Da1VPeU5tN01rc21Oa3hScUlHK0Rxdz09&data=05%7C01%7Cbrutzman%40nps.edu%7C17ca92de311849fc6b6d08db278a139f%7C6d936231a51740ea9199f7578963378e%7C0%7C0%7C638147246992876041%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=b9DUscaJ9e3LWUhWPaiYRBGPoO%2FVVcPvL3%2FDFY7DnPw%3D&reserved=0>
> - https://zoom.us/j/148206572
> <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fzoom.us%2Fj%2F148206572&data=05%7C01%7Cbrutzman%40nps.edu%7C17ca92de311849fc6b6d08db278a139f%7C6d936231a51740ea9199f7578963378e%7C0%7C0%7C638147246992876041%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=4DlFF0swOJzeGnksEuxZREwOr9BoaT9ElmBj1Ye%2FtMw%3D&reserved=0>
> Password 483805
> - https://www.web3d.org/member/teleconference-information
>
>
>
> 1. *X3D 2023 goals.* Our primary activities for X3D Working Group in
> 2023 are focused on broad and correct deployment.
>
>
>
> a. Encourage consistent rendering, interaction and usage for the many
> tremendous capabilities in X3D4.
>
> b. Update ISO specifications and implementations for multiple
> programming languages and file encodings to match X3D4.
>
>
>
>
>
> 1. *Web3D 2023 Conference*
>
>
>
> Call for papers now available. What a powerful program!
>
>
>
> - Web3D 2023, 9-11 October 2023, Vicomtech
> - San Sebastian Spain, In-person and Online
> - https://web3d.siggraph.org
> <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fweb3d.siggraph.org%2F&data=05%7C01%7Cbrutzman%40nps.edu%7C17ca92de311849fc6b6d08db278a139f%7C6d936231a51740ea9199f7578963378e%7C0%7C0%7C638147246993033114%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=C8ZSjOcIyR1MGEsfxuqq37MCHGeVB3i5KeaPkfuZXVs%3D&reserved=0>
> - https://web3d.siggraph.org/cfp
> <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fweb3d.siggraph.org%2Fcfp&data=05%7C01%7Cbrutzman%40nps.edu%7C17ca92de311849fc6b6d08db278a139f%7C6d936231a51740ea9199f7578963378e%7C0%7C0%7C638147246993033114%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=RoxH4TXHDCAp056f4srbq152YKtWPv8erMfCwqmsM0I%3D&reserved=0>
>
>
>
> *Towards interconnectivity of Metaverses*
>
> The purpose of the 28th International ACM Conference on 3D Web Technology
> (Web3D 2023) is to study and share the principles and the latest
> advancements in connected 3D universes. Provide navigation metaphors that
> allow users to move seamlessly from one virtual world to another.
>
> The goal of the conference and of the Web3D community, which has a rich
> history of developing technologies that enable the creation, transmission,
> access, interaction, sharing, and visualization of 3D universes. Bringing
> together a diverse group of individuals to share innovative and influential
> thoughts on how the metaverse can revolutionize the future of
> communications. This includes topics such as 3D applications and services
> accessible through a wide range of devices, from simple mobile phones to
> more complex systems such as AR/VR headsets, and heavily populated virtual
> worlds, especially those connected through high-speed, low-latency networks.
>
> The 28th International ACM Conference on 3D Web Technology (Web3D 2023) is
> a major event for the Metaverse community. Sponsored by ACM SIGGRAPH, in
> cooperation with Web3D Consortium and supported by Eurographics, this
> conference is hosted by Vicomtech and brings together experts from around
> the world to discuss the latest research, development, and practices
> related to the Metaverse.
>
> It will be really interested if we can start collecting and disseminating
> 3D models as part of the publication process. Anyone interested?
>
>
>
>
>
> 1. *X3D 4.0 editors-draft IS.review preparation now in progress*
>
>
>
> Have begun applying changes from editors review of DIS spec, in
> preparation for final IS submission to ISO. Many changes are complete,
> several pending ISO comments require lengthy double-checking. Marked-up
> specification draft visible at
>
>
>
> -
> https://www.web3d.org/specifications/X3Dv4Draft/ISO-IEC19775-1v4-IS.review
>
>
>
> As before, each comment is being resolved in Mantis. Mantis issues are
> not closed until reviewed together. Specification changes are checked
> into GitHub.
>
>
>
> - Mantis issue resolution
> - https://www.web3d.org/member-only/mantis/view_all_bug_page.php
>
>
>
> - Review draft
> -
> https://github.com/Web3DConsortium/X3D/tree/master/ISO-IEC19775/ISO-IEC19775-1/ISO-IEC19775-1v4.0/ISO-IEC19775-1v4-IS.review
> <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FWeb3DConsortium%2FX3D%2Ftree%2Fmaster%2FISO-IEC19775%2FISO-IEC19775-1%2FISO-IEC19775-1v4.0%2FISO-IEC19775-1v4-IS.review&data=05%7C01%7Cbrutzman%40nps.edu%7C17ca92de311849fc6b6d08db278a139f%7C6d936231a51740ea9199f7578963378e%7C0%7C0%7C638147246993033114%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=kIvCeFkagOTmzYgy7hnEuITXwgA9DCu4gOYydedQUE0%3D&reserved=0>
>
>
>
> - Editors comments
> -
> https://github.com/Web3DConsortium/X3D/blob/master/ISO-IEC19775/ISO-IEC19775-1/ISO-IEC19775-1v4.0/ISO-IEC19775-1v4-DIS.ISO/Disposition%20of%20Comments%20on%20ISO_IEC_DIS_19775-1_(Ed_4).pdf
> <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FWeb3DConsortium%2FX3D%2Fblob%2Fmaster%2FISO-IEC19775%2FISO-IEC19775-1%2FISO-IEC19775-1v4.0%2FISO-IEC19775-1v4-DIS.ISO%2FDisposition%2520of%2520Comments%2520on%2520ISO_IEC_DIS_19775-1_(Ed_4).pdf&data=05%7C01%7Cbrutzman%40nps.edu%7C17ca92de311849fc6b6d08db278a139f%7C6d936231a51740ea9199f7578963378e%7C0%7C0%7C638147246993033114%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=7NVBVUQV1osZoVQr%2Bdc33AcNS90JDvQHcBIL9jQdVnI%3D&reserved=0>
>
>
>
> When these changes are all complete and reviewed satisfactorily, I will
> again fire up the build scripts to scrub all style markup appropriately, to
> create a separate pristine version for ISO submission.
>
>
>
>
>
> 1. *X3D4 Sound Component review*
>
>
>
> - Minutes 3 MAR 2023: X3D4 Sound Component and W3C Audio API review
> -
> https://web3d.org/pipermail/x3d-public_web3d.org/2023-March/018574.html
>
>
>
> Dick Puk sent a message to Web3D member-only X3D list about only accepting
> editorial/errata changes at this late date of X3D 4.0 finalization.
> Thanks for that.
>
>
>
> - [x3d] Recent discussions about changes to the X3D 4.0 Sound Component
>
>
>
> Issues that will get resolved in this final editing phase:
>
>
>
> - clarifications needed in prose for 16.4.13 ListenerPointSource and
> 16.4.18 SpatialSound nodes.
> - https://www.web3d.org/member-only/mantis/view.php?id=1436
> - “If the *dopplerEnabled* field is TRUE, then sound sources which are
> moving spatially in the transformation hierarchy, relative to the location
> of the ListenerPointSource node, shall be modified by applying
> velocity-induced frequency shifts corresponding to Doppler effect.”
>
>
>
> - Correcting mistaken type, also for specification consistency: SFTime
> - DynamicsCompressor : X3DSoundProcessingNode {
>
> SFFloat [in,out] attack 0.003 [0,∞)
>
> SFTime [in,out] release 0.25 [0,∞)
>
> - https://www.web3d.org/member-only/mantis/view.php?id=1436
>
>
>
> - Convolver buffer[] array is quite difficult to use, allowing
> AudioClip as an alternative seems like an obvious (previously overlooked)
> remedy.
> - We decided to wait and fix it later, along with other likely
> refinements to the Sound component, to best align with Web Audio API.
> It is related to handling of multiple-channel sound sources.
>
>
>
> - SFInt32 number of channels to go with buffer in Convolver?
> - This is not explicitly described in specification, but implicit in
> handling of the child nodes (such as BufferAudioSource).
> - Need for editorial clarification accepted.
> - We will look in Web Audio API and see if there is useful prose to
> paraphrase in Convolver that helps to clarify the handling of
> number-of-channel questions. Otherwise we’ll create appropriate prose.
> Doug has next crack at this.
>
>
>
> As described in previous meetings, I will be looking for one or two
> co-chairs who can begin documenting Web3D Best Practices and suggested new
> capabilities for X3D 4.0. As ever, discussion on x3d-public mailing list
> and synopses in Mantis Issue Tracker will be the means for ensuring that
> all good consensus approaches are captured and advanced.
>
>
>
>
>
> 1. *Comment reconciliation*
>
>
>
> Dick Puk and I will review correct completion and resolve each of the
> following applied comments.
>
>
>
> Id
>
> Project
>
> Tags
>
> Status
>
> Severity
>
> Summary
>
> 1436
>
> X3D
>
> V4.0 Resolution
>
> assigned
>
> minor
>
> Sound component editorial clarifications
>
> 1435
>
> X3D
>
> V4.0 Resolution
>
> assigned
>
> minor
>
> cross-link AcousticProperties from Sound component to Shape component
>
> 1434
>
> X3D
>
> V4.0 Resolution
>
> assigned
>
> minor
>
> DIS editors disposition: annex citations
>
> 1433
>
> X3D
>
> V4.0 Resolution
>
> assigned
>
> minor
>
> DIS editors disposition: glossary, replace 'abbreviations' with
> 'abbreviated terms'
>
> 1432
>
> X3D
>
> V4.0 Resolution
>
> assigned
>
> minor
>
> DIS editors disposition: clause 3, definitions introductory paragraph
>
> 1431
>
> X3D
>
> V4.0, V4.0 Resolution
>
> assigned
>
> minor
>
> indicating references are required
>
> 1430
>
> X3D
>
> V4.0 Resolution
>
> assigned
>
> minor
>
> DIS editors disposition: general comment 10, references introductory
> paragraph
>
> 1429
>
> X3D
>
> V4.0 Resolution
>
> assigned
>
> minor
>
> DIS editors disposition: general comment 9, foreward, additional note on
> feedback
>
> 1428
>
> X3D
>
> V4.0 Resolution
>
> assigned
>
> minor
>
> DIS editors disposition: general comment 8, foreword list of changes
>
> 1427
>
> X3D
>
> V4.0 Resolution
>
> assigned
>
> minor
>
> DIS editors disposition: general comment 7 Foreword boilerplate
>
> 1426
>
> X3D
>
> V4.0 Resolution
>
> assigned
>
> minor
>
> DIS editors disposition: general comment 5, title structure
>
> 1425
>
> X3D
>
> V4.0 Resolution
>
> assigned
>
> minor
>
> DIS editors disposition: general comment 4, code font
>
> 1424
>
> X3D
>
> V4.0 Resolution
>
> assigned
>
> minor
>
> DIS editors disposition: general comment 3, Introduction and TOC
>
> 1423
>
> X3D
>
> V4.0 Resolution
>
> assigned
>
> minor
>
> DIS editors disposition: general comment 2, correct verbal forms
>
> 1422
>
> X3D
>
> V4.0 Resolution
>
> assigned
>
> minor
>
> DIS editors disposition: general comment 1 "this document"
>
> 1420
>
> X3D
>
> V4.0 Resolution, V4.1
>
> assigned
>
> major
>
> Missing 5 enumeration sets (and likely fields) from Web Audio interfaces
>
> 1419
>
> X3D
>
> V4.0 Resolution
>
> assigned
>
> minor
>
> rename “Texture Projector component” as “Texture Projection component”
>
> 1418
>
> X3D
>
> V4.0 Resolution
>
> assigned
>
> major
>
> Ambiguity about texture coordinate generation
>
> 1417
>
> X3D
>
> V4.0 Resolution
>
> assigned
>
> minor
>
> versionContent document-index table incomplete
>
> 1415
>
> X3D
>
> V4.0 Resolution
>
> assigned
>
> minor
>
> 26.3.4 HAnimMotion field issues: name, skeletalConfiguration,
> totalNumberFrames
>
> 1414
>
> X3D
>
> V4.0 Resolution
>
> assigned
>
> minor
>
> 26.3.4 HAnimMotion node signatures
>
> 1413
>
> X3D
>
> V4.0 Resolution
>
> assigned
>
> text
>
> Misspelled node name: IndexedFanSet should be IndexedTriangleFanSet
>
> 1411
>
> X3D
>
> V4.0 Resolution
>
> assigned
>
> minor
>
> enumeration values for Web Audio nodes do not follow CAPITALIZATION
> conventions
>
> 1410
>
> X3D
>
> V4.0 Resolution
>
> assigned
>
> major
>
> HAnimHumanoid skin definitions need to assign textures via Shape, Group,
> Switch etc.
>
> 1408
>
> X3D
>
> V4.0 Resolution
>
> assigned
>
> feature
>
> CollisionCollection and HAnimMotion nodes are each missing description
> field
>
> 1407
>
> X3D
>
> V4.0 Resolution
>
> assigned
>
> minor
>
> Collision element (and other elements) missing description field in
> Version Content
>
> 1406
>
> X3D
>
> V4.0 Resolution
>
> assigned
>
> minor
>
> 25.3.6 GeoOrigin description is awkwardly phrased
>
> 1405
>
> X3D
>
> V4.0 Resolution
>
> assigned
>
> minor
>
> 39.3.2 X3DDamperNode has erroneous extra characters
>
> 1404
>
> X3D
>
> V4.0 Resolution
>
> assigned
>
> minor
>
> 39.4.6 OrientationDamper, incorrect word 'orientation' vice 'rotation'
>
> 1403
>
> X3D
>
> V4.0 Resolution
>
> assigned
>
> minor
>
> Insufficient description for HAnimJoint
>
> 1402
>
> X3D
>
> V4.0 Resolution
>
> assigned
>
> minor
>
> Insufficient description for HAnimSegment
>
> 1401
>
> X3D
>
> V4.0 Resolution, V4.1
>
> assigned
>
> minor
>
> formally adding values to align X3D4 LineProperties with Quality
> Information Framework (QIF) specification
>
> 1398
>
> X3D
>
> V4.0 Resolution
>
> assigned
>
> minor
>
> OrthoViewpoint fieldOfView type needs to be SFVec4f, not MFFloat
>
>
>
>
>
>
>
> - Nicholas do you have a geosystem prose refinement for us?
> - https://www.web3d.org/member-only/mantis/view.php?id=1437
>
>
>
> Great meeting, thanks everyone.
>
>
>
> Color note: don’t forget to wear green on Saint Patrick’s Day… your
> avatar too. March the 17th – Sleep the 18th. [image: Shamrock]
>
>
>
> Have fun with X3D 4.0! 8)
>
>
>
> all the best, Don
>
> --
>
> Don Brutzman Naval Postgraduate School, Code USW/Br
> brutzman at nps.edu
>
> Watkins 270, MOVES Institute, Monterey CA 93943-5000 USA +1.831.656.2149
>
> X3D graphics, virtual worlds, navy robotics, data
> http://faculty.nps.edu/brutzman
>
>
>
> _______________________________________________
> x3d-public mailing list
> x3d-public at web3d.org
> http://web3d.org/mailman/listinfo/x3d-public_web3d.org
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20230318/503612d9/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 1171 bytes
Desc: not available
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20230318/503612d9/attachment-0001.png>
More information about the x3d-public
mailing list