<div dir="ltr">From <a href="http://json-schema.org">json-schema.org</a>:<div><br></div><div><h3 id="gmail-the-path-to-standardization" style="margin:0px 0px 15px;padding:0px;font-weight:400;font-size:26px;color:rgb(17,17,17);font-family:-apple-system,BlinkMacSystemFont,"Segoe UI",Roboto,Helvetica,Arial,sans-serif,"Apple Color Emoji","Segoe UI Emoji","Segoe UI Symbol";background-color:rgb(253,253,253)">"The Path to Standardization</h3><p style="margin:0px 0px 15px;padding:0px;color:rgb(17,17,17);font-family:-apple-system,BlinkMacSystemFont,"Segoe UI",Roboto,Helvetica,Arial,sans-serif,"Apple Color Emoji","Segoe UI Emoji","Segoe UI Symbol";font-size:16px;background-color:rgb(253,253,253)">The JSON Schema project intends to shepherd all four draft series to RFC status. Currently, we are continuing to improve our self-published Internet-Drafts. The next step will be to get the drafts adopted by an IETF Working Group. We are actively investigating how to accomplish this.</p><p style="margin:0px 0px 15px;padding:0px;color:rgb(17,17,17);font-family:-apple-system,BlinkMacSystemFont,"Segoe UI",Roboto,Helvetica,Arial,sans-serif,"Apple Color Emoji","Segoe UI Emoji","Segoe UI Symbol";font-size:16px;background-color:rgb(253,253,253)">If you have experience with such things and would like to help, please contact us!"</p><p style="margin:0px 0px 15px;padding:0px;color:rgb(17,17,17);font-family:-apple-system,BlinkMacSystemFont,"Segoe UI",Roboto,Helvetica,Arial,sans-serif,"Apple Color Emoji","Segoe UI Emoji","Segoe UI Symbol";font-size:16px;background-color:rgb(253,253,253)"><br></p><p style="margin:0px 0px 15px;padding:0px;color:rgb(17,17,17);font-family:-apple-system,BlinkMacSystemFont,"Segoe UI",Roboto,Helvetica,Arial,sans-serif,"Apple Color Emoji","Segoe UI Emoji","Segoe UI Symbol";font-size:16px;background-color:rgb(253,253,253)">So perhaps there's not much motivation for tool developers to migrate their tools to the new version?</p><p style="margin:0px 0px 15px;padding:0px;color:rgb(17,17,17);font-family:-apple-system,BlinkMacSystemFont,"Segoe UI",Roboto,Helvetica,Arial,sans-serif,"Apple Color Emoji","Segoe UI Emoji","Segoe UI Symbol";font-size:16px;background-color:rgb(253,253,253)"><br></p><p style="margin:0px 0px 15px;padding:0px;color:rgb(17,17,17);font-family:-apple-system,BlinkMacSystemFont,"Segoe UI",Roboto,Helvetica,Arial,sans-serif,"Apple Color Emoji","Segoe UI Emoji","Segoe UI Symbol";font-size:16px;background-color:rgb(253,253,253)">John</p></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Apr 23, 2020 at 12:47 PM Don Brutzman <<a href="mailto:brutzman@nps.edu">brutzman@nps.edu</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi John, thanks for your many efforts.<br>
<br>
We do hope for standard JSON and standard Python both.<br>
<br>
a. Having a JSON schema generator is very useful. If you think that we can generate v7 for that, well it is something... the main problem is familiar to us, namely that the json-schema project is not progressing very well.<br>
<br>
[1] JSON Schema "The current version is 2019-09!"<br>
<a href="https://json-schema.org" rel="noreferrer" target="_blank">https://json-schema.org</a><br>
<br>
As you likely recall, each time we have checked the tool support has not matched the draft. So even if we generate a JSON Schema (productionizing patterns authored by Roy Walmsley) we can't test it. Not very helpful.<br>
<br>
When it is stable, we can finish the job and our X3D JSON work will essentially be complete.<br>
<br>
[2] X3D to JSON Stylesheet Converter<br>
<a href="https://www.web3d.org/x3d/stylesheets/X3dToJson.html" rel="noreferrer" target="_blank">https://www.web3d.org/x3d/stylesheets/X3dToJson.html</a><br>
<br>
b. As we finish X3D4 this year, the X3D specification efforts will next start stepping through each each of the file encodings and programming language bindings.<br>
<br>
[3] X3D Specifications: Schema and DOCTYPE Validation<br>
<a href="https://www.web3d.org/specifications" rel="noreferrer" target="_blank">https://www.web3d.org/specifications</a><br>
<br>
[4] X3D Graphics Standard: Specification Relationships<br>
<a href="https://www.web3d.org/specifications/X3dSpecificationRelationships.png" rel="noreferrer" target="_blank">https://www.web3d.org/specifications/X3dSpecificationRelationships.png</a><br>
<a href="https://www.web3d.org/specifications/X3dSpecificationRelationships.pdf" rel="noreferrer" target="_blank">https://www.web3d.org/specifications/X3dSpecificationRelationships.pdf</a><br>
<br>
Having X3DUOM keeping the majority of our example implementations exactly in synchronization with each other. (Just today applied a minor tweak, field attributes are now listed with name appearing first to improve readability. Now uploading.)<br>
<br>
[5] X3D Unified Object Model (X3DUOM)<br>
<a href="https://www.web3d.org/specifications/X3DUOM.html" rel="noreferrer" target="_blank">https://www.web3d.org/specifications/X3DUOM.html</a><br>
<br>
Just today the Design Printing Scanning Working Group zoom conference had intensely interesting demos in python, jupyter notebook and C++ showing CAD conversions producing consistent X3D in an HTML page. Way cool.<br>
<br>
So yes, am happy to report that the essential aspects of everything we are working on are indeed getting standardized for best stability and re-use. Any X3D knowledge in one domain is equivalent to the functionality in another domain.<br>
<br>
Have fun with X3D4! 8)<br>
<br>
On 4/23/2020 9:59 AM, John Carlson wrote:<br>
> We might as well focus on non-standard JSON schema, if we're going to focus on non-standard Python...<br>
> <br>
> (heh!)<br>
> <br>
> John<br>
> <br>
> On Thu, Apr 23, 2020 at 11:36 AM John Carlson <<a href="mailto:yottzumm@gmail.com" target="_blank">yottzumm@gmail.com</a> <mailto:<a href="mailto:yottzumm@gmail.com" target="_blank">yottzumm@gmail.com</a>>> wrote:<br>
> <br>
> I was generating JSON schema, and I got<br>
> <br>
> $ sh generateSchema.sh<br>
> .0<br>
> .1<br>
> .2<br>
> <br>
> And I went, WTF? Then, apparently my vision cleared and I saw:<br>
> <br>
> $ sh generateSchema.sh<br>
> 3.0<br>
> 3.1<br>
> 3.2<br>
> 3.3<br>
> 4.0<br>
> <br>
> So....anyone interested in looking at generated JSON schema, even though not many tools are available for 2019-09? I am set up for draft-07 (previous draft).<br>
> <br>
> Thanks,<br>
> <br>
> John<br>
> <br>
> <br>
> _______________________________________________<br>
> x3d-public mailing list<br>
> <a href="mailto:x3d-public@web3d.org" target="_blank">x3d-public@web3d.org</a><br>
> <a href="http://web3d.org/mailman/listinfo/x3d-public_web3d.org" rel="noreferrer" target="_blank">http://web3d.org/mailman/listinfo/x3d-public_web3d.org</a><br>
> <br>
<br>
all the best, Don<br>
-- <br>
Don Brutzman Naval Postgraduate School, Code USW/Br <a href="mailto:brutzman@nps.edu" target="_blank">brutzman@nps.edu</a><br>
Watkins 270, MOVES Institute, Monterey CA 93943-5000 USA +1.831.656.2149<br>
X3D graphics, virtual worlds, navy robotics <a href="http://faculty.nps.edu/brutzman" rel="noreferrer" target="_blank">http://faculty.nps.edu/brutzman</a><br>
</blockquote></div>