[x3d-public] Status: JSON Schema
yottzumm at gmail.com
Sun Sep 22 16:18:46 PDT 2019
The main JSON schema changes seem to be using $defs for definitions (not required) and format (may need application code to validate URIs).
Send me a meeting date and time, and I will attempt to attend. I have an appointment on Thursday.
I have already implemented $defs changes in the autogenerated schema (not checked in). I have been unable to test this due to the lack of validators. We will not modify Roy’s schema for backwards compatibility I feel.
The autogenerated schema has useful additions over Roy’s schema, including USE handling. I believe we’ve gone through comparing draft-07 and Roy’s schema, and they find “equivalent” invalid documents, ignoring some items in development. My guess is Roy’s schema will be unable to process USE properly, since this is a major change. Most of our documents correctly use USE, so it’s not a problem.
You should probably include this JSON validator in your documentation, if the main X3DJSONLD is not used if it’s too confusing:
https://coderextreme.net/X3DJSONLD/src/main/html/validator.html (3.3 draft-07 validator)
(regression testing is not done after installation, so there may be bugs one can report).
It’s important to note that the Unified Object Model is not a JSON schema according to the recent draft, AFAIK.
If you wish to generate X3D JSON schema from X3DUOM JSON, that will require more work.
I can provide or check in recent X3D JSON schemas, if desired. I’m waiting for 4.0 demand, I guess.
Sent from Mail for Windows 10
From: Brutzman, Donald (Don) (CIV)
Sent: Sunday, September 22, 2019 5:34 PM
To: John Carlson
Cc: X3D Graphics public mailing list
Subject: Re: [x3d-public] Status: JSON Schema
Thanks for noting this advancement John, it is a very useful milestone to us.
When ready we need to go the the latest version, now labeled 2019-09 (published 8 days ago).
There is a helpful-looking section, "Migrating from older drafts"
Our latest version (primarily authored by Roy Walmsley with some updates by you) is available at
The points in the migration sections look pretty straightforward. How about we go through these in another two weeks or so? TODO, lets
a. upgrade current manually produced version of X3D JSON Schema, then
b. autogenerate X3D JSON Schema using X3DUOM.
c. validate with JSON schema tools when available, we can ask around there for support.
d. update all tool support and all models in X3D Examples Archives.
e. outline what ISO/IEC 19776-5 X3D JSON Encoding specification will look like next year.
Additional references, now better organized at:
X3D Specifications: Schema and DOCTYPE Validation
* coderextreme/X3DJSONLD: X3D JSON loader and node.js express web server for serving files from localhost
* X3D to JSON Stylesheet Converter
* Roy Walmsley, Don Brutzman and John Carlson, A JSON Encoding for X3D,
ACM SIGGRAPH Web3D 2016 Conference, Anaheim California USA, 22-24 August 2016 (presentation, .pdf).
Have fun with X3D JSON! 8)
On 9/22/2019 12:15 PM, John Carlson wrote:
> Here is the link to implementations in the meantime.
> *Good Luck!*
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
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the x3d-public