[x3d-public] comments in USE nodes

John Carlson yottzumm at gmail.com
Tue Oct 24 22:38:29 PDT 2017


One of these errors brought up an issue:  We should probably allow -children along with @USE if the children are comments.   What do you think?  Can someone craft a schema item that I can put into all nodes?  Making it a ref would reduce the amount of code.

This may be a standards issue, whether to allow comments in USE nodes.

Here’s a start:

                        "oneOf": [
                                {
                                        "type": "object",
                                        "properties": {
                                                "@USE": {
                                                        "type": "string"
                                                },
			    “-children”: {
                                        "type": "array",
                                        "minItems": 1,
                                        "items": {
                                                "type": "object",
                                                "properties": {
                                                        "#comment": {
                                                                "type": "string"
                                                        }
                                                },
                                                "additionalProperties": false
		          }
		   }
                                        },
                                        "required": [
                                            "@USE"
                                        ],
                                        "additionalProperties": false
                                },

Sent from Mail for Windows 10

From: John Carlson
Sent: Wednesday, October 25, 2017 1:18 AM
To: Don Brutzman; x3d-public at web3d.org; Roy Walmsley
Subject: RE: Here are the org.everit JSON schema verifier errors with theX3DResource Examples files recently converted to JSON.

json-schema 3.3 Validation error org.everit.json.schema.ValidationException: #/X3D/Scene/-children/3/Group: #: only 1 subschema matches out of 2 C:/x3d-code/www.web3d.org/x3d/content/examples/Savage/CommunicationsAndSensors/Sonobuoys/SonobuoyFieldScenario.json
json-schema 3.3 Validation error org.everit.json.schema.ValidationException: #/X3D/Scene/-children/5/Switch: #: only 1 subschema matches out of 2 C:/x3d-code/www.web3d.org/x3d/content/examples/Savage/CommunicationsAndSensors/Sonobuoys/SonobuoyFieldScenario.json
json-schema 3.3 Validation error org.everit.json.schema.ValidationException: #/X3D/Scene/-children/6/Group: #: only 1 subschema matches out of 2 C:/x3d-code/www.web3d.org/x3d/content/examples/Savage/CommunicationsAndSensors/Sonobuoys/SonobuoyFieldScenario.json
json-schema 3.3 Validation error org.everit.json.schema.ValidationException: #/X3D/Scene/-children/8/Group: #: only 1 subschema matches out of 2 C:/x3d-code/www.web3d.org/x3d/content/examples/Savage/CommunicationsAndSensors/Sonobuoys/SonobuoyFieldScenario.json

@USE and @name in ProtoInstance (several) – search for USE


json-schema 3.3 Validation error org.everit.json.schema.ValidationException: #/X3D/Scene/-children/0/NavigationInfo: #: only 1 subschema matches out of 2 C:/x3d-code/www.web3d.org/x3d/content/examples/Savage/GroundVehicles/Jeep/Jeep.json
json-schema 3.3 Validation error org.everit.json.schema.ValidationException: #/X3D/Scene/-children/10/Transform: #: only 1 subschema matches out of 2 C:/x3d-code/www.web3d.org/x3d/content/examples/Savage/GroundVehicles/Jeep/Jeep.json
json-schema 3.3 Validation error org.everit.json.schema.ValidationException: #/X3D/Scene/-children/12/Inline: #: only 1 subschema matches out of 2 C:/x3d-code/www.web3d.org/x3d/content/examples/Savage/GroundVehicles/Jeep/Jeep.json

“EXAMINE ANY” is a single SFString in an MFString in NavigationInfo @type

json-schema 3.3 Validation error org.everit.json.schema.ValidationException: #/X3D/Scene/-children/1/ExternProtoDeclare/@url: 2 schema violations found C:/x3d-code/www.web3d.org/x3d/content/examples/Savage/ShipsMilitary/Frigate-MEKO200-Greece/MEKO200.json
json-schema 3.3 Validation error org.everit.json.schema.ValidationException: #/X3D/Scene/-children/2/Transform: #: only 1 subschema matches out of 2 C:/x3d-code/www.web3d.org/x3d/content/examples/Savage/ShipsMilitary/Frigate-MEKO200-Greece/MEKO200.json

Both @USE (FAT_SHAFT) and -children in a Shape. (comment)

json-schema 3.3 Validation error org.everit.json.schema.ValidationException: #/X3D/Scene/-children/1/NavigationInfo: #: only 1 subschema matches out of 2 C:/x3d-code/www.web3d.org/x3d/content/examples/Vrml2Sourcebook/Siggraph98Course/SubWorld.json
json-schema 3.3 Validation error org.everit.json.schema.ValidationException: #/X3D/Scene/-children/6/Group: #: only 1 subschema matches out of 2 C:/x3d-code/www.web3d.org/x3d/content/examples/Vrml2Sourcebook/Siggraph98Course/SubWorld.json
json-schema 3.3 Validation error org.everit.json.schema.ValidationException: #/X3D/Scene/-children/18/Transform: #: only 1 subschema matches out of 2 C:/x3d-code/www.web3d.org/x3d/content/examples/Vrml2Sourcebook/Siggraph98Course/SubWorld.json
json-schema 3.3 Validation error org.everit.json.schema.ValidationException: #/X3D/Scene/-children/19/Transform: #: only 1 subschema matches out of 2 C:/x3d-code/www.web3d.org/x3d/content/examples/Vrml2Sourcebook/Siggraph98Course/SubWorld.json
json-schema 3.3 Validation error org.everit.json.schema.ValidationException: #/X3D/Scene/-children/20/Transform: #: only 1 subschema matches out of 2 C:/x3d-code/www.web3d.org/x3d/content/examples/Vrml2Sourcebook/Siggraph98Course/SubWorld.json

ALL is invalid NavigationInfo @type.


json-schema 3.3 Validation error org.everit.json.schema.ValidationException: #/X3D/Scene/-children/4/HAnimHumanoid: #: 0 subschemas matched instead of one C:/x3d-code/www.web3d.org/x3d/content/examples/X3dForAdvancedModeling/MotionAnimation/BvhConversion1.json


l_middistal_tip, r_middistal_tip, vl5_to_Chest2, Chest_to_LeftCollar, LeftCollar, Chest_to_RightCollar, RightCollar, Chest2_to_Neck,  Neck, Chest2 are illegal @name’s

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20171025/10b21ce3/attachment-0001.html>


More information about the x3d-public mailing list