[x3d-public] X3D minutes7 May 2021: X3D4 architecture ballot, HAnimJoint stiffness, unquoted MFString values

Don Brutzman brutzman at nps.edu
Fri May 7 15:04:43 PDT 2021

I hope that everyone is well.

1. New business


a. JSON Schema automation of John Carlson patterns.

* [x3d-public] JSON schema or ECMAScript API first?

b. X3D-Edit 4 beta testing: standalone application is improving, embedded NetBeans modules still broken.

* X3D-Edit 4.0 Authoring Tool for Extensible 3D (X3D) Graphics


2. X3D4 Architecture committee draft (CD) ballot comments submitted to ISO/IEC SC24.

- Preparation: ISO editors (Puk, Brutzman) to keep adding draft prose to Mantis
- Preparation: X3D working group will be asked to consider technical issues.
- The sheer volume of comments means that editors resolution will take some time.
- Expectation once ballots received and comments addressed: either another round of CD, or next Draft International Specification (DIS).

Discuss expected delays in SAI specifications: original 19775-2 then language bindings and file encodings won't be able to occur on the original fast timeline we had hoped for.  Must address X3D4 Architecture first.


3. XMP metadata examples, working to match corresponding Semantic Web queries

We explored a variety of capabilities being explored.

* https://x3dgraphics.com/examples/X3dForWebAuthors/Chapter15Metadata/XmpMetadataEmbeddedIndex.html

* https://x3dgraphics.com/examples/X3dForWebAuthors/Chapter15Metadata/XmpMetadataSupportX3D.pptx

Vince examples

* https://www.dropbox.com/s/amrsl4wur8092sv/Alternative%20XMP%20to%20X3D%20results.txt?dl=0

Vince noted how XMP is not about a file per se, but is actually about a resource.  Often they are the same but not always, for example when the XMP resource consists of multiple data files/sources.

It is interesting to think about how we might map multiple XMP "packet" (i.e. the XMP term for metadata structures) within X3D directly, just as can be done for JPEG audio video etc.

Interesting progress/challenges!


4. Mantis issue review.

a. HAnimJoint stiffness field, SFVec3f rather than MFFloat, correct default

* https://www.web3d.org/member-only/mantis/view.php?id=1113
* https://www.web3d.org/member-only/mantis/view.php?id=1116

- make X3D spec consistent with HAnim, both for type SFVec3f and value [0 0 0]
- always a 3-tuple, default 0 0 0 (not 1 1 1 which is immovable stiffness)
- improved wording in HAnim spec for clarity

Please expect corresponding changes to X3D XML Schema and DTD, X3DUOM etc. with testing in progress...

Found that only change needed in these tools was default values, now checked in and deploying tonight.


b. Unquoted SFString values in MFString attributes for XML encoding

Multiple experimental examples in the MetadataSet/MetadataString for XMP above.

No need to rush this - will pursue next week.


Step by step.  Have fun with X3D!  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 http://faculty.nps.edu/brutzman

More information about the x3d-public mailing list