<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>Please review JSON schemas 3.0-4.0 in the specifications folder. These are old versions. New versions are maintained in X3DJSONLD/src/main/schema, and generated from the shell folder using gen… something. The python called from shell is called etgenerateschema.py found in the python folder.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>If you want to do a smaller schema first, provide a simpler X3DUOM. Thanks!</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:brutzman@nps.edu">Brutzman, Donald (Don) (CIV)</a><br><b>Sent: </b>Monday, June 10, 2019 8:15 AM<br><b>To: </b><a href="mailto:yottzumm@gmail.com">John Carlson</a><br><b>Cc: </b><a href="mailto:x3d-public@web3d.org">X3D Graphics public mailing list</a><br><b>Subject: </b>Re: JSON Schema Work In Progress Feedback and X3D preparations</p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>On 6/9/2019 12:00 PM, John Carlson wrote:</p><p class=MsoNormal>> Note, the next draft will not be called draft-08 when published.</p><p class=MsoNormal>> </p><p class=MsoNormal>> So we should probably stop calling that draft that.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>No worries. Their current labeling is</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal> "Next Draft (by whatever name)"</p><p class=MsoNormal>and</p><p class=MsoNormal> "We have typically referred to this as draft-08"</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>So we can continue to simply use whatever they say their name is. IETF will likely guide them, there are lots of procedures and policies there for draft document naming.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>> See link for more details.</p><p class=MsoNormal>> </p><p class=MsoNormal>> I haven’t seen any software implementations (validators) yet.</p><p class=MsoNormal>> </p><p class=MsoNormal>> Ajv looks like it’s getting a new repository on GitHub.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Agreed that getting good JSON Schema validator support is key next step for our X3D JSON testing. We will be providing them excellent feedback regarding whether it is working.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Wondering, if you want to simplify the editing chores for evolution of our X3D JSON schemas, then if "draft-08" has a lot of changes then we might simply focus on Interchange profile support. That is testable and a lot smaller. Once we have a good design pattern, it is time to "turn the crank" and automate production of full JSON schemas for X3D versions 3.0 thru 4.0.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Once valid schemas are in hand, we then install the revised JSON schema validator of choice, and can then finally apply our already-available automated validation of schemas and 2900 X3D .json models themselves. Boom presto, lather-rinse-repeat until full validity is achieved.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>> FYI,</p><p class=MsoNormal>> </p><p class=MsoNormal>> John</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>thanks for tracking this John!</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>> Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10</p><p class=MsoNormal>> </p><p class=MsoNormal>> *From: *Brutzman, Donald (Don) (CIV) <mailto:brutzman@nps.edu></p><p class=MsoNormal>> *Sent: *Friday, June 7, 2019 7:45 AM</p><p class=MsoNormal>> *To: *X3D Graphics public mailing list <mailto:x3d-public@web3d.org></p><p class=MsoNormal>> *Cc: *John Carlson <mailto:yottzumm@gmail.com></p><p class=MsoNormal>> *Subject: *JSON Schema Work In Progress Feedback</p><p class=MsoNormal>> </p><p class=MsoNormal>> https://json-schema.org/work-in-progress</p><p class=MsoNormal>> </p><p class=MsoNormal>> =======================================</p><p class=MsoNormal>> </p><p class=MsoNormal>> The Next Draft (by whatever name) Is Ready for Final Pre-Publication Review!</p><p class=MsoNormal>> </p><p class=MsoNormal>> The forthcoming draft is now feature-frozen and entering the final four-week feedback period before publication. This final review will last from May 27th to June 24th, 2019.</p><p class=MsoNormal>> </p><p class=MsoNormal>> The timeline may be compressed if, after at least two weeks, there is a clear consensus that the drafts are solid and it would be best to publish sooner rather than later.</p><p class=MsoNormal>> </p><p class=MsoNormal>> The following sorts of feedback are particularly desired:</p><p class=MsoNormal>> </p><p class=MsoNormal>> Clarity, readability, and accessibility to new readers</p><p class=MsoNormal>> </p><p class=MsoNormal>> Contradictions, inconsistencies and other bugs</p><p class=MsoNormal>> </p><p class=MsoNormal>> Anything so egregious that implementation would be infeasible or impossible</p><p class=MsoNormal>> </p><p class=MsoNormal>> New features or major changes to existing features will be deferred to a future draft, and work on the next draft will begin immediately after this one is published.</p><p class=MsoNormal>> </p><p class=MsoNormal>> =======================================</p><p class=MsoNormal>> </p><p class=MsoNormal>> Looks like the time has finally come for work on updating our X3D JSON Schema (originals authored by Roy Walmsley, updates by John Carlson) for JSON draft-08!</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>all the best, Don</p><p class=MsoNormal>-- </p><p class=MsoNormal>Don Brutzman Naval Postgraduate School, Code USW/Br brutzman@nps.edu</p><p class=MsoNormal>Watkins 270, MOVES Institute, Monterey CA 93943-5000 USA +1.831.656.2149</p><p class=MsoNormal>X3D graphics, virtual worlds, navy robotics http://faculty.nps.edu/brutzman</p><p class=MsoNormal><o:p> </o:p></p></div></body></html>