[x3d-public] Deprecating X3D JSON Schema

[John Carlson]

“Probably it would be easy to pull nodes out of X3DUOM and equivalent nodes
out of my (JSON Schema) ‘templates.’  That is actually a really good idea.
Don, let me know if this seems like an agreeable path forward for JSON and
JSON Schema.”

It appears something like this was already done for VRML.

So I have two paths before me, creating a full X3D VRML grammar from
X3DUOM, or creating a mapping from X3DUOM to JSON schema by pulling out
equivalent nodes out of each.

Which has higher priority in your mind?  I am well on the way to the first,
but it relies on an  ANTLR grammar (Is there a spec or standard?) generated
from X3DUOM and other sources by a Python script.  The second seems more
green field and suitable to automation.

We already have a VRML grammar.  I might be able to add property ordering
to JSON schema, if I can find it in XML Schema or X3DUOM.  My tendency is
to go with XML Schema for JSON.

Specifically with VRML, I am looking to pull out OrientationInterpolators
and providing options for transforming the SFRotation keyValue values
(scaling by -1).


John



On Tue, Dec 19, 2023 at 9:16 PM Brutzman, Donald (Don) (CIV) <
brutzman at nps.edu> wrote:

> John, sorry but I just am not understanding your message.
>
>
>
> X3dTidy.xslt is a stylesheet that fixes up .x3d files.
>
>
>
> “Deprecation” is a term used when a feature is expected to be removed from
> a language or API.
>
>
>
> JSON encoding validated by JSON schema is part of our plan for the coming
> year, as part of a new specification.
>
>
>
> We have long been waiting for JSON Schema draft to become an IETF
> standard, and also waiting for supporting Java tools that work so that we
> might apply to our X3D Examples.
>
>
>
> When we can finally go forward, we can automate production of your draft
> JSON Schema templates using X3DUOM for exactness and long-term stability.
>
>
>
> If the JSON schema draft is frozen, we might consider doing all this in
> 2024 sometime.
>
>
>
> None of this is new information.  If it would help everyone’s shared
> understanding to discuss these necessary steps together on a regular Friday
> X3D Working Group call, am happy to do so.
>
>
>
> Thanks for willingness to advance JSON Schema for X3D, when we can
> accomplish that successfully.
>
>
>
> 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
> https://faculty.nps.edu/brutzman
>
>
>
> *From:* x3d-public <x3d-public-bounces at web3d.org> *On Behalf Of *John
> Carlson via x3d-public
> *Sent:* Tuesday, December 19, 2023 6:12 PM
> *To:* X3D Graphics public mailing list <x3d-public at web3d.org>
> *Cc:* John Carlson <yottzumm at gmail.com>
> *Subject:* [x3d-public] Deprecating X3D JSON Schema
>
>
>
> I plan on deprecating X3D JSON Schema in favor of XML Schema as soon as
> x3d-tidy outputs JSON in correct order (or I modify X3DJSONLD) and I figure
> out how to validate DOM in ECMAScript.  This has been accomplished in Java,
> so I’m hoping this will be easy in ECMAScript.  If someone wants to donate
> code to the cause, welcome!
>
>
>
> John
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20231222/7b0b20a0/attachment-0001.html>