[x3d-public] X3D schema, DTD updates: new ClassicVRML encoding, inputOnly/outputOnly fields now complete

Don Brutzman brutzman at nps.edu
Mon Jun 8 21:05:05 PDT 2015

Lots of scrutiny and activity have resulted in numerous constructive changes to the X3D Schema and X3D DTD.

New autogenerated product, includes both node signatures and example use:

	X3D Part 2: ClassicVRML encoding specification:
	Clause 6 Encoding of nodes.

Additional progress: the inputOnly, outputOnly fields are now completely defined, allowing complete definition of X3D Scene Access Interface (SAI) for Java.

	Java Binding Annex B Abstract node interfaces

	Java Binding Annex C Concrete node interfaces

X3D Schema update activity:
8 June 2015, walmsley brutzman
- (v3.1+) Added axisRotation to CylinderSensor and PlaneSensor.
- geoSystemType is MFString, not SFString
- Added numerous accessType inputOnly/outputOnly annotation appinfo entries to facilitate API autogeneration
- Removed redundant node annotation appinfo entries when already included by inherited node type
- Note that CADAssembly children ViewpointGroup and OrthoViewpoint require Navigation component level 3,
   which is higher than Viewpoint provided in CADInterchange profile
- removed SquadOrientationInterpolator closed field, erroneous; added normalizeVelocity field
- removed texCoord field from NurbsPatchSurface, duplicative with X3DNurbsSurfaceGeometryNode
- removed texCoord and controlPointfields from NurbsTrimmedSurface, duplicative with X3DNurbsSurfaceGeometryNode
- NurbsCurve2D is not a renderable geometry node, removed from geometry content model.
- ComposedCubeMapTexture contained-element field name corrected from "topUrl" to "top"
- Added missing fields: SurfaceEmitter coordIndex, VolumeEmitter internal
- BoundaryEnhancementVolumeStyle content model fixed/simplified
- fixed capitalization, spelling etc. of detected errors in field-name enumerations for each accessType;
   added corresponding annotation/appinfo inputOnly/outputOnly events
- detected, fixed irregular use of commas and [brackets] in elements with multiple X3D element defaults
- fixed Layer content model, allowing zero or more children
- ensured all annotation/appinfo SFNode/MFNode inputOnly, outputOnly events have default type included
- refactored Programmable Shaders component nodes, minimized use of mixed content (contained CDATA text)
- (v3.2+) CollisionCollection base type X3DNode, default containerField="collider"
- moved fraction_changed from X3DTimeDependentNode to TimeSensor
- TODO noted problem: actual containerField for AudioClip is "source" not "children"
- (v3.2+) Contact base type X3DNode, matching spec
- (v3.1+) LocalFog is not bindable, implements X3DChildNode with additionalInterface X3DFogObject
- (v3.2+) LayoutGroup additionalInterface X3DGroupingNode, TODO review content-model collisions if direct inheritance used
- (v3.1+) Text node added outputOnly event "origin", lineBounds is type MFVec2f
- Resolved appinfo fields for X3DSoundSourceNode and X3DTimeDependentNode
- Removed duplicate appinfo set_bind field from GeoViewpoint inherited from X3DBindableNode
- (V3.2+) Added missing children, addChildren, and RemoveChildren fields to LayoutGroup
- (V3.2+) Added missing containerField to Contact
- Add missing MedicalInterchange profile
- Added QA test, ensured that MFString default values are quoted

X3D DTD update activity:
8 June 2015, walmsley brutzman
- corrected MultiTexture not part of Texture2DNodes, instead part of AppearanceChildNodes etc.
- (v3.3+) corrected content model for VolumeStyle nodes, omitting MultiTexture
- (v3.2+) CollisionCollection default containerField="collider"
- Added MedicalInterchange profile

These assets can be found on the X3D Specifications: XML Schema and DOCTYPE Validation page.


Full documentation updates have been autogenerated for the XML Schema and DOCTYPE, available for X3D versions 3.0 through 3.4.  Recommended version:


The X3D Working Group also maintains the X3D Graphics Standards: Specification Relationships diagram up to date, showing the roadmap for all major planned work.


Please note that X3D version 3.4 is experimental and supports specification development.

Changes are tested through validation regression testing of 3800+ open source X3D scenes.

     X3D Resources: Examples

     X3D Resources: Quality Assurance (QA)

Corresponding updates have also been made to:

     X3D Tooltips

Refreshes will soon follow to:

     X3D Validator

     X3D-Edit Authoring Tool

Several further changes are under investigation on the mailing lists:
- Content model for IndexLineSet, LineSet and PointSet.
- Content model for LayoutGroup.
- Interface hierarchy for AudioClip and MovieTexture.

Feedback welcome, thanks for all testing and contributions.  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 mailing list