<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>Given the univerified fixes to the X3DUOM 3.0, I was able to autogenerate X3D JSON Schemas under draft07 JSON schema and the various versions of the X3D standard and check into sourceforge (sorry don, I didn’t think it would hurt, and it seems like a good way to get thing to you. Here they are:</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><a href="https://sourceforge.net/p/x3d/code/HEAD/tree/www.web3d.org/specifications/x3d-3.0-JSONSchema.json">https://sourceforge.net/p/x3d/code/HEAD/tree/www.web3d.org/specifications/x3d-3.0-JSONSchema.json</a><o:p></o:p></p><p class=MsoNormal><a href="https://sourceforge.net/p/x3d/code/HEAD/tree/www.web3d.org/specifications/x3d-3.1-JSONSchema.json">https://sourceforge.net/p/x3d/code/HEAD/tree/www.web3d.org/specifications/x3d-3.1-JSONSchema.json</a><o:p></o:p></p><p class=MsoNormal><a href="https://sourceforge.net/p/x3d/code/HEAD/tree/www.web3d.org/specifications/x3d-3.2-JSONSchema.json">https://sourceforge.net/p/x3d/code/HEAD/tree/www.web3d.org/specifications/x3d-3.2-JSONSchema.json</a><o:p></o:p></p><p class=MsoNormal><a href="https://sourceforge.net/p/x3d/code/HEAD/tree/www.web3d.org/specifications/x3d-4.0-JSONSchema.json">https://sourceforge.net/p/x3d/code/HEAD/tree/www.web3d.org/specifications/x3d-4.0-JSONSchema.json</a><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Please check for accuracy and completeness. Thanks! I will too!<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>The 3.3 version will come along later, and is also important, but these versions are equally important.<o:p></o:p></p><p class=MsoNormal><br>I will let don check in the 3.0 X3DUOM and then I will regenerate the X3D JSON Schema 3.0. Right now, the X3DUOM for 3.0 and the X3D JSON schema for 3.0 do not match up.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>John<o:p></o:p></p></div></body></html>