[x3d-public] Schema versus semantic validator

[John Carlson]

I am thinking a semantic validator for X3D JSON may be more valuable than JSON schema.  What do you think, and what’s the potential for writing such a thing?

John

Sent from Mail for Windows 10

From: Roy Walmsley
Sent: Monday, July 10, 2017 1:05 PM
To: 'John Carlson'; 'Don Brutzman'
Cc: 'X3D Graphics public mailing list'
Subject: RE: X3D JSON schema validation problems: @class andIMPORT/EXPORTattributes

John and Don,

Yes, thanks for pointing ROUTE out as an exemplar.

On reflection, perhaps we can make IMPORT and EXPORT objects, not arrays. Should be easy enough.

Also, the wording in the draft 19776-5 needs improvement, since these statements can appear in other places. Need to see if this also applies to other statements. I think my wording arose from trying to cover all the properties of the Scene object, without thinking through the implications sufficiently.

I’ve changed the JSON schema, and attached a copy for you guys to check before I commit to SourceForge, just in case we get unexpected hiccups.

All the best,

Roy

From: John Carlson [mailto:yottzumm at gmail.com] 
Sent: 10 July 2017 17:38
To: Don Brutzman <brutzman at nps.edu>; Roy Walmsley <roy.walmsley at ntlworld.com>
Cc: 'X3D Graphics public mailing list' <x3d-public at web3d.org>
Subject: RE: X3D JSON schema validation problems: @class and IMPORT/EXPORTattributes


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/5946a282/attachment.html>