[X3D-Public] X3D Schema updates, autogenerating Java SAI appendices, node inventory update
brutzman at nps.edu
Sun Oct 5 17:29:43 PDT 2014
Lots of useful updates can be found on the X3D Specifications: XML Schema and DOCTYPE Validation page.
a. X3D Schema update activity:
6 October 2014, brutzman
Major addition to all versions:
- Inserted annotation appinfo elements/attributes for inputOnly, outputOnly and
SFNode/MFNode fields in concrete node interfaces, now allowing API autogeneration.
This additional type/accessType/default detail does not affect XML validation.
Tested through generation of Java Scene Authoring Interface (SAI) specification
appendices using stylesheets/BuildSpecificationLanguageBindingJava.xslt conversion.
- Annotation attribute otherInterfaces refactored as additionalInterface
- Future work: autogenerate native Java interfaces as standalone source code library.
Schema validation modifications:
- CollisionSensor object model corrected to extend X3DSensorNode vice X3DChildNode
- GeoLOD object model corrected to extend X3DChildNode, X3DBoundedObject vice X3DChildNode
- StaticGroup object model corrected as X3DChildNode, X3DBoundedObject
- MultiTexture node: omitted erroneous/extraneous 'transparent' field
- TextureCoordinateGenerator node: added enumeration type textureCoordinateGeneratorModeValues
Full documentation updates have been autogenerated for the XML Schema and DOCTYPE validators.
b. The X3D Java Scene Access Interface (SAI) appendices are now being autogenerated.
* Annex B Abstract node Interfaces
* Annex C Concrete node interfaces
The current X3D Java Binding specification is online at
These will get submitted as part of a Java SAI Committee Draft (CD) update to ISO following working-group discussion, likely topic during this Wednesday's teleconference.
Review feedback on the interface patterns will be welcome - we probably should schedule a teleconference on this. Revisions are easily incorporated for consensus points.
c. Future TODO: autogenerating independent source interfaces.
The node-generation blocks will someday be adapted to create a package of actual source-code interfaces for compilation validation. This will help tools and authors looking for a lightweight way to compile Script code written in Java.
The review of best practices will be done in comparison to the Xj3D interfaces. Changes should be vetted by implementation and evaluation. Currently there are some variations in there that deserve further analysis.
Further Xj3D development information is available at
d. Also updated the X3D Node Inventory Comparison spreadsheet.
X3DOM progress continues, there is now 62% support for X3D version 3.3 (155 of 251 nodes).
Have fun with X3D!
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