<html xmlns:v="urn:schemas-microsoft-com:vml" 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:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle21
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1346402299;
mso-list-type:hybrid;
mso-list-template-ids:1201984914 1376816380 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;
mso-fareast-font-family:Calibri;
mso-bidi-font-family:Calibri;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link="#0563C1" vlink="#954F72" style='word-wrap:break-word'><div class=WordSection1><p class=MsoNormal>Thanks for inquiry about bulk validation possibilities… Recently got update to Altova XMLSpy 2022 Enterprise Edition.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>As before, this include capability to<o:p></o:p></p><ul style='margin-top:0in' type=disc><li class=MsoListParagraph style='margin-left:0in;mso-list:l0 level1 lfo1'>Convert XML Schema to/from JSON Schema<o:p></o:p></li><li class=MsoListParagraph style='margin-left:0in;mso-list:l0 level1 lfo1'>https://www.altova.com/manual/XMLSpy/spyenterprise/urefconvert_xmlschematojsonschema.html<o:p></o:p></li></ul><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Using default settings with “latest JSON schema” selected, the current X3D 4.0 XML Schema converted to JSON and update saved at<o:p></o:p></p><ul style='margin-top:0in' type=disc><li class=MsoListParagraph style='margin-left:0in;mso-list:l0 level1 lfo1'>https://www.web3d.org/specifications/x3d-4.0-JSONSchema.autogenerated.json <o:p></o:p></li></ul><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Please advise if you want different settings applied. Should be interesting to compare their version with your version.<o:p></o:p></p><p class=MsoNormal><br>I suspect that bulk validation will be possible… Just checked the XMLSpy project files autogenerated with each X3D Examples archive, will improve them and then try…<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>… fixed, adding entry for JSON models to catalog. Bulk validation supported! Screenshot attached.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Am now updating all catalogs and running a full rebuild of latest X3dToJson.xslt conversions.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Looks like we are back in business! Have fun comparing/debugging/improving X3D JSON Schema and conversion patterns…<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><div style='mso-element:para-border-div;border:none;border-bottom:solid windowtext 1.5pt;padding:0in 0in 1.0pt 0in'><p class=MsoNormal style='border:none;padding:0in'>XMLSpy error log follows. Again, this is using their autogenerated X3D JSON schema, not yours. Onward we go.<o:p></o:p></p><p class=MsoNormal style='border:none;padding:0in'><o:p> </o:p></p></div><p class=MsoNormal>File C:\x3d-code\www.web3d.org\x3d\content\examples\X3dForWebAuthors\HelloWorld.json is not valid.<o:p></o:p></p><p class=MsoNormal> Property '-children' is not allowed here because schema property 'additionalProperties' is false.<o:p></o:p></p><p class=MsoNormal> Hint: A matching entry in 'properties' or 'patternProperties' is needed to successfully validate this object.<o:p></o:p></p><p class=MsoNormal> Error location: X3D / Scene / -children<o:p></o:p></p><p class=MsoNormal> Details<o:p></o:p></p><p class=MsoNormal> Property 'Scene' is not valid.<o:p></o:p></p><p class=MsoNormal> Property 'X3D' is not valid.<o:p></o:p></p><p class=MsoNormal> Property '-children' is not allowed here because schema property 'additionalProperties' is false.<o:p></o:p></p><p class=MsoNormal> Hint: A matching entry in 'properties' or 'patternProperties' is needed to successfully validate this object.<o:p></o:p></p><p class=MsoNormal> Error location: X3D / head / -children<o:p></o:p></p><p class=MsoNormal> Details<o:p></o:p></p><p class=MsoNormal> Property 'head' is not valid.<o:p></o:p></p><p class=MsoNormal> Property 'X3D' is not valid.<o:p></o:p></p><p class=MsoNormal> Property 'encoding' is not allowed here because schema property 'additionalProperties' is false.<o:p></o:p></p><p class=MsoNormal> Hint: A matching entry in 'properties' or 'patternProperties' is needed to successfully validate this object.<o:p></o:p></p><p class=MsoNormal> Error location: X3D / encoding<o:p></o:p></p><p class=MsoNormal> Details<o:p></o:p></p><p class=MsoNormal> Property 'X3D' is not valid.<o:p></o:p></p><p class=MsoNormal> Property '@xsd:noNamespaceSchemaLocation' is not allowed here because schema property 'additionalProperties' is false.<o:p></o:p></p><p class=MsoNormal> Hint: A matching entry in 'properties' or 'patternProperties' is needed to successfully validate this object.<o:p></o:p></p><p class=MsoNormal> Error location: X3D / @xsd:noNamespaceSchemaLocation<o:p></o:p></p><p class=MsoNormal> Details<o:p></o:p></p><p class=MsoNormal> Property 'X3D' is not valid.<o:p></o:p></p><p class=MsoNormal> Property 'JSON schema' is not allowed here because schema property 'additionalProperties' is false.<o:p></o:p></p><p class=MsoNormal> Hint: A matching entry in 'properties' or 'patternProperties' is needed to successfully validate this object.<o:p></o:p></p><p class=MsoNormal> Error location: X3D / JSON schema<o:p></o:p></p><p class=MsoNormal> Details<o:p></o:p></p><p class=MsoNormal> Property 'X3D' is not valid.<o:p></o:p></p><div style='mso-element:para-border-div;border:none;border-bottom:solid windowtext 1.5pt;padding:0in 0in 1.0pt 0in'><p class=MsoNormal style='border:none;padding:0in'><o:p> </o:p></p></div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New"'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New"'>all the best, Don<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New"'>-- <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New"'>Don Brutzman Naval Postgraduate School, Code USW/Br brutzman@nps.edu<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New"'>Watkins 270, MOVES Institute, Monterey CA 93943-5000 USA +1.831.656.2149<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New"'>X3D graphics, virtual worlds, Navy robotics https://</span> <span style='font-size:10.0pt;font-family:"Courier New"'>faculty.nps.edu/brutzman<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b>From:</b> x3d-public <x3d-public-bounces@web3d.org> <b>On Behalf Of </b>John Carlson<br><b>Sent:</b> Sunday, March 20, 2022 12:34 PM<br><b>To:</b> X3D Graphics public mailing list <x3d-public@web3d.org><br><b>Subject:</b> [x3d-public] Paths forward, Java for JSON Schema<o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>So if we want a Java solution for JSON Schema 2020-12, what do we do?<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>AFAIK, Khronos supports 2020-12 with glTF 2, but glTF has been web-oriented, so no need for Java, TIKO.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Can we do some kind of bulk JSON validation with XMLSpy?<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Should we just skip Java-based JSON validation based on other’s code, and hope we can accomplish validation on our own? I have been relying on X3DJSAIL.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>John<o:p></o:p></p></div></div></body></html>