<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang=EN-US link=blue vlink="#954F72"><div class=WordSection1><p class=MsoNormal>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?</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>John</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Sent from <a href="https://go.microsoft.com/fwlink/?LinkId=550986">Mail</a> for Windows 10</p><p class=MsoNormal><o:p> </o:p></p><div style='mso-element:para-border-div;border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal style='border:none;padding:0in'><b>From: </b><a href="mailto:roy.walmsley@ntlworld.com">Roy Walmsley</a><br><b>Sent: </b>Monday, July 10, 2017 1:05 PM<br><b>To: </b><a href="mailto:yottzumm@gmail.com">'John Carlson'</a>; <a href="mailto:brutzman@nps.edu">'Don Brutzman'</a><br><b>Cc: </b><a href="mailto:x3d-public@web3d.org">'X3D Graphics public mailing list'</a><br><b>Subject: </b>RE: X3D JSON schema validation problems: @class andIMPORT/EXPORTattributes</p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span lang=EN-GB>John and Don,<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB>Yes, thanks for pointing ROUTE out as an exemplar.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB>On reflection, perhaps we can make IMPORT and EXPORT objects, not arrays. Should be easy enough.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB>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.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB>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.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB>All the best,<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB>Roy<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b>From:</b> John Carlson [mailto:yottzumm@gmail.com] <br><b>Sent:</b> 10 July 2017 17:38<br><b>To:</b> Don Brutzman <brutzman@nps.edu>; Roy Walmsley <roy.walmsley@ntlworld.com><br><b>Cc:</b> 'X3D Graphics public mailing list' <x3d-public@web3d.org><br><b>Subject:</b> RE: X3D JSON schema validation problems: @class and IMPORT/EXPORTattributes<o:p></o:p></p></div></div><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Don writes:<o:p></o:p></p><p class=MsoNormal>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.<br><br>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).<o:p></o:p></p><p class=MsoNormal><br>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?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>John<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>