[x3d-public] The following files do not pass the new, generated X3D 3.3JSONschema (yay, we caught some more)

[John Carlson]

Roy, could you look through the attached bug reports and possibly find issues with old schema or more likely, the examples?  Again, you problem need to go to the deepest error, as ajv currently bubbles up errors.  I believe these are all false negatives in the new schema or object model, and we will likely need to address them in the object model in some cases (geoSystem and maybe metadata).  Once geoSystem is handled, I will move on to other areas of the schema (metadata) and try to fix those.  But if you could look at them and tell me why the new schema is passing them, possibly improperly, that would be appreciated.

Here are the paths related to metadata:

dataPath: X3D > Scene > -children > 0 > Group > -metadata > MetadataSet
 dataPath: X3D > Scene > -children > 0 > Group > -metadata > MetadataSet > -metadata > MetadataString
 dataPath: X3D > Scene > -children > 0 > Group > -metadata > MetadataSet > -value > 0 > MetadataDouble
 dataPath: X3D > Scene > -children > 0 > Group > -metadata > MetadataSet > -value > 1 > MetadataFloat
 dataPath: X3D > Scene > -children > 0 > Group > -metadata > MetadataSet > -value > 2 > MetadataInteger
 dataPath: X3D > Scene > -children > 0 > Group > -metadata > MetadataSet > -value > 3 > MetadataSet
 dataPath: X3D > Scene > -children > 1 > ProtoDeclare > ProtoBody > -children > 4 > Group > -metadata > MetadataSet
 dataPath: X3D > Scene > -children > 11 > ProtoDeclare > ProtoBody > -children > 1 > Group > -children > 2 > Group > -metadata > MetadataString
 dataPath: X3D > Scene > -children > 12 > Group > -children > 1 > Transform > -metadata > MetadataFloat > -metadata > MetadataDouble
 dataPath: X3D > Scene > -children > 13 > ProtoDeclare > ProtoBody > -children > 1 > Group > -children > 2 > Group > -metadata > MetadataString
 dataPath: X3D > Scene > -children > 3 > ProtoDeclare > ProtoBody > -children > 1 > Group > -children > 2 > Group > -metadata > MetadataString
 dataPath: X3D > Scene > -children > 5 > ProtoDeclare > ProtoBody > -children > 1 > Group > -children > 2 > Group > -metadata > MetadataString
 dataPath: X3D > Scene > -children > 7 > ProtoDeclare > ProtoBody > -children > 1 > Group > -children > 2 > Group > -metadata > MetadataString
 dataPath: X3D > Scene > -children > 9 > ProtoDeclare > ProtoBody > -children > 1 > Group > -children > 2 > Group > -metadata > MetadataString
John

Sent from Mail for Windows 10

From: John Carlson
Sent: Tuesday, October 24, 2017 8:32 AM
To: Don Brutzman; Roy Walmsley; x3d-public at web3d.org
Subject: RE: The following files do not pass the new, generated X3D 3.3JSONschema (yay, we caught some more)

These are the files which don’t pass the old schema. These may be places were we can improve the new schema, because it passes them.


C:/x3d-code/www.web3d.org/x3d/content/examples/Basic/development/MetadataExamples.json
C:/x3d-code/www.web3d.org/x3d/content/examples/Basic/development/RenderingComponentPrototypes.json
C:/x3d-code/www.web3d.org/x3d/content/examples/Basic/development/TestMetadataNodes.json
C:/x3d-code/www.web3d.org/x3d/content/examples/Basic/Geospatial/Squaw.json
C:/x3d-code/www.web3d.org/x3d/content/examples/Basic/Geospatial/SquawLOD000.json
C:/x3d-code/www.web3d.org/x3d/content/examples/Basic/Geospatial/SquawLOD001.json
C:/x3d-code/www.web3d.org/x3d/content/examples/Basic/Geospatial/SquawLOD002.json
C:/x3d-code/www.web3d.org/x3d/content/examples/Basic/Geospatial/SquawLOD003.json
C:/x3d-code/www.web3d.org/x3d/content/examples/Basic/Geospatial/SquawLOD004.json
C:/x3d-code/www.web3d.org/x3d/content/examples/Basic/Geospatial/SquawLOD005.json
C:/x3d-code/www.web3d.org/x3d/content/examples/Basic/Geospatial/SquawLOD006.json
C:/x3d-code/www.web3d.org/x3d/content/examples/Basic/Geospatial/SquawLOD007.json
C:/x3d-code/www.web3d.org/x3d/content/examples/Basic/Geospatial/SquawLOD008.json
C:/x3d-code/www.web3d.org/x3d/content/examples/Basic/Geospatial/SquawLOD009.json
C:/x3d-code/www.web3d.org/x3d/content/examples/Basic/Geospatial/SquawLOD010.json
C:/x3d-code/www.web3d.org/x3d/content/examples/Basic/Geospatial/SquawLOD011.json
C:/x3d-code/www.web3d.org/x3d/content/examples/Basic/Geospatial/SquawLOD012.json
C:/x3d-code/www.web3d.org/x3d/content/examples/Basic/Geospatial/SquawLOD013.json
C:/x3d-code/www.web3d.org/x3d/content/examples/Basic/Geospatial/SquawLOD014.json
C:/x3d-code/www.web3d.org/x3d/content/examples/Basic/Geospatial/SquawLOD015.json
C:/x3d-code/www.web3d.org/x3d/content/examples/Basic/Geospatial/SquawLOD016.json
C:/x3d-code/www.web3d.org/x3d/content/examples/Basic/LatticeXvl/XvlShellModelDolphin.json
C:/x3d-code/www.web3d.org/x3d/content/examples/Basic/LatticeXvl/XvlShellModelHand.json
C:/x3d-code/www.web3d.org/x3d/content/examples/Basic/LatticeXvl/XvlShellModelOctopus.json
C:/x3d-code/www.web3d.org/x3d/content/examples/Basic/LatticeXvl/XvlShellModelStar.json
C:/x3d-code/www.web3d.org/x3d/content/examples/Basic/X3dSpecifications/X3dHeaderPrototypeSyntaxExamples.json
C:/x3d-code/www.web3d.org/x3d/content/examples/X3dForAdvancedModeling/MotionAnimation/BvhConversion1.json
C:/x3d-code/www.web3d.org/x3d/content/examples/X3dForAdvancedModeling/MotionAnimation/BvhConversion1Illustrated.json
C:/x3d-code/www.web3d.org/x3d/content/examples/X3dForAdvancedModeling/MotionAnimation/BvhConversion1Invisible.json
C:/x3d-code/www.web3d.org/x3d/content/examples/X3dForAdvancedModeling/MotionCapture/BvhConversion1Illustrated.json
C:/x3d-code/www.web3d.org/x3d/content/examples/X3dForAdvancedModeling/MotionCapture/BvhConversion1Invisible.json
C:/x3d-code/www.web3d.org/x3d/content/examples/X3dForWebAuthors/Chapter14Prototypes/MaterialModulatorExamples.json
C:/x3d-code/www.web3d.org/x3d/content/examples/X3dForWebAuthors/Chapter15Metadata/MetadataNodeExamples.json

Sent from Mail for Windows 10

From: John Carlson
Sent: Tuesday, October 24, 2017 7:00 AM
To: Don Brutzman; Roy Walmsley; x3d-public at web3d.org
Subject: The following files do not pass the new, generated X3D 3.3 JSONschema (yay, we caught some more)

C:/x3d-code/www.web3d.org/x3d/content/examples/Basic/HumanoidAnimation/BoxManAnimationPanel.json
C:/x3d-code/www.web3d.org/x3d/content/examples/Basic/X3dSpecifications/Robot.json
C:/x3d-code/www.web3d.org/x3d/content/examples/Savage/CommunicationsAndSensors/Sonobuoys/SonobuoyFieldScenario.json
C:/x3d-code/www.web3d.org/x3d/content/examples/Savage/GroundVehicles/Jeep/Jeep.json
C:/x3d-code/www.web3d.org/x3d/content/examples/Savage/ShipsMilitary/Frigate-MEKO200-Greece/MEKO200.json
C:/x3d-code/www.web3d.org/x3d/content/examples/Vrml2Sourcebook/Siggraph98Course/SubWorld.json
C:/x3d-code/www.web3d.org/x3d/content/examples/X3dForAdvancedModeling/MotionCapture/BvhConversion1.json

Attached is the schema for your verification.  There are other files which don’t match the schema.  These are the only once that do past the old schema.

Attached is the schema generator.  You will have to change the locations of the used files.

Please verify with your own JSON schema verfiers.  Next step, move to draft-06, if it adds anything for us.

John


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20171024/111f3ae8/attachment-0001.html>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: results.txt
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20171024/111f3ae8/attachment-0001.txt>