[x3d-public] [x3d] X3DUOM and validation of dangling references?

Brutzman, Donald (Don) (CIV) brutzman at nps.edu
Sat Sep 29 12:55:24 PDT 2018


On 9/29/2018 9:44 AM, John Carlson wrote:
> Hmm.   It looks like some nodes may be referenced before they are declared?  Not sure yet.   I thought IFS was in all versions?  I will have to check.   Sorry for not checking it right away.

Hi John.  I think the root cause was simply schema document maintenance for each version.  I do diffs between each successive version 3.0 thru 4.0 to ensure consistent, these must have crept backwards from a future version.  Since the errors were in our custom annotations, other strong-validation checks didn't find them.

Master list of all node and field versions is provided in X3D specification:

	X3D Part 1: Architecture and base components, Annex Z, Version content
	http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/versionContent.html

... which reveals that FogCoord and X3DVertexAttribute are both introduced in X3D v3.1, and so should not be referenced in X3D v3.0.

No other versionitis problems found throughout all the schemas.  As expected, no similar problems found in DTDs.

Your detecting this particular problem enabled me to (a) fix it, (b) confirm no other related dangling-reference errors were occurring, and (c) add further tests to ensure that it doesn't occur again.

Updates applied, changes checked into sourceforge version control, and results are being deployed now.  Again thanks.

	X3D Specifications: Schema and DOCTYPE Validation
	http://www.web3d.org/specifications

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