[x3d-public] X3D JSON schema validation problems: @class and IMPORT/EXPORTattributes

[John Carlson]

Don writes:
Thanks Roy.  This will be good to sort out more closely.  I don't think this draft JSON specification is entirely correct; IMPORT and EXPORT statements can appear multiple times and anywhere in the scene graph, not just with the Scene (root) element.  Good practice for DEF readability/confirmation is to put each of them near their corresponding Inline node, but that isn't explicitly required.

I don’t know about the specification, but the JSON schema supports IMPORT/EXPORT in other places, namely -children and -allNodes (and perhaps other places).

I believe the problem was that you use an object, and not an array in X3dToJson.xslt output. Perhaps we need to discuss how that array is formed, like -children or like ROUTE/meta/field etc?

John

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20170710/a89156c1/attachment.html>