<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>Vince, Don,</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Note that I’ve detected a possible problem with STEP -> JSON conversion. See detail below. Please insure that converted STEP files pass X3D Validator, if you haven’t already. If they do, then we will address the standard, or the JSON schema. Thanks!</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Draft07 schemas are here: <a href="https://github.com/coderextreme/x3droundtrip/tree/master/stdschemabackup">https://github.com/coderextreme/x3droundtrip/tree/master/stdschemabackup</a>. These should be the standard 3.3 JSON schema plus my changes for draft07, and additions for XvlShell and headlight (3.0). I believe the draft04 X3D JSON schema is a backup in that folder for your reference.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Result of running with everit validator attached.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>90 of these errors have to do with geoSystem, which we’ve likely seen before—I don’t know the detail however, I just think there’s probably still an “N” (north) in these files.</p><p class=MsoNormal>63 have to do with -shape[containerField] containing (Group), which are probably new, possible issues with Schema—add Group, or STEP converter—use Transform, not Group???? I’ll let people who are closer to the X3D standard figure this one out.</p><p class=MsoNormal>23 are -14 in NancyDivingProtoInstances.json I’m not sure this file is up-to-date with the X3D XML file. Let’s see if this file is getting updated by the process of conversion.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>220 total lines.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Please send potential schema changes through a pull request (change all schemas affected) and email the group as well. Thanks!</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Once we have a handle on these, we will move to the generated draft07 schema (which I modified to put the draft07 at the top <span style='font-family:"Segoe UI Emoji",sans-serif'>☹</span>). Note that my schema has half the error reports <span style='font-family:"Segoe UI Emoji",sans-serif'>😊</span> <span style='font-family:"Segoe UI Emoji",sans-serif'>☹</span>, the error reports are quite different (none of the above are mentioned—whoops!), so we have a lot of work to do.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>John<o:p></o:p></p></div></body></html>