[x3d-public] Eye trouble; standard JSON and standard Python both

[Don Brutzman]

Hi John, thanks for your many efforts.

We do hope for standard JSON and standard Python both.

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.

[1] JSON Schema "The current version is 2019-09!"
     https://json-schema.org

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.

When it is stable, we can finish the job and our X3D JSON work will essentially be complete.

[2] X3D to JSON Stylesheet Converter
     https://www.web3d.org/x3d/stylesheets/X3dToJson.html

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.

[3] X3D Specifications: Schema and DOCTYPE Validation
     https://www.web3d.org/specifications

[4] X3D Graphics Standard: Specification Relationships
     https://www.web3d.org/specifications/X3dSpecificationRelationships.png
     https://www.web3d.org/specifications/X3dSpecificationRelationships.pdf

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.)

[5] X3D Unified Object Model (X3DUOM)
     https://www.web3d.org/specifications/X3DUOM.html

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.

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.

Have fun with X3D4!   8)

On 4/23/2020 9:59 AM, John Carlson wrote:
> We might as well focus on non-standard JSON schema, if we're going to focus on non-standard Python...
> 
> (heh!)
> 
> John
> 
> On Thu, Apr 23, 2020 at 11:36 AM John Carlson <yottzumm at gmail.com <mailto:yottzumm at gmail.com>> wrote:
> 
>     I was generating JSON schema, and I got
> 
>       $ sh generateSchema.sh
>     .0
>     .1
>     .2
> 
>     And I went, WTF? Then, apparently my vision cleared and I saw:
> 
>     $ sh generateSchema.sh
>     3.0
>     3.1
>     3.2
>     3.3
>     4.0
> 
>     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).
> 
>     Thanks,
> 
>     John
> 
> 
> _______________________________________________
> x3d-public mailing list
> x3d-public at web3d.org
> http://web3d.org/mailman/listinfo/x3d-public_web3d.org
> 

all the best, Don
-- 
Don Brutzman  Naval Postgraduate School, Code USW/Br       brutzman at nps.edu
Watkins 270,  MOVES Institute, Monterey CA 93943-5000 USA   +1.831.656.2149
X3D graphics, virtual worlds, navy robotics http://faculty.nps.edu/brutzman