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

[Don Brutzman]

Yes again, thanks for that comparison with ROUTE.  Am understanding better now, sorry for not understanding at first.  Looks like I need to fix the X3dToJson.xslt converter then... if that is how we are landing.

On 7/10/2017 10:05 AM, Roy Walmsley wrote:
> 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
> 


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