[x3d-public] renewed development of X3D JSON support

[Brutzman, Donald (Don) (CIV)]

The Altova XML Spy generated schema is not a solution, it is an example showing design patterns that may be useful.

Am pretty busy with X3D4 issues and Web3D 2021 Conference preparations.

If you find a flaw in the autogenerated examples that doesn’t match our design, I can adjust the conversion pattern and regenerate all the examples overnight.

Not sure what you mean by “solution for the web” since running inside a browser is nice but not required; also not a very practical test technique.

There are several dozen tools supporting JSON schema, when we winnowed those down to those supporting latest JSON schema, we should be able to get test harnesses working with node.js and Java Ant.

Step by step we will eventually achieve this.  Please take care of yourself, thanks John.

From: John Carlson <yottzumm at gmail.com>
Sent: Wednesday, October 13, 2021 4:31 PM
To: Brutzman, Donald (Don) (CIV) <brutzman at nps.edu>; X3D Graphics public mailing list <x3d-public at web3d.org>
Subject: Re: renewed development of X3D JSON support

Don, hoping you can start working on Java solutions, so far I’ve worked on JavaScript and python.   Everit is broken and I haven’t tried working on other Java packages .   Your generated schemas do not play well with Ajv.   All examples are broken.   I have achieved pretty good results with my X3D JSON Schema in non-strict mode in JavaScript, but a solution for the web is required.   I have forgotten my python results, I switched validation packages in Python.   I have a test.py in  X3DJSONLD/src/main/python/test.py.

My carpal tunnel flared up to the worst level ever.

On Tue, Oct 12, 2021 at 4:31 AM John Carlson <yottzumm at gmail.com<mailto:yottzumm at gmail.com>> wrote:
Here are the validaton problems with the converted with the x3D JSON
schema converted from X3D XML schema:

$ bash validate.sh 2>&1|grep Failed" "validation|wc

    3823   38270 2619431
$ bash validate.sh 2>&1|grep "Invalid regular expression"|wc

    3823   38270 2619431

3823 files fail validation with regexp errors.  Probably in the
converted X3D JSON schema, would be my guess.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20211014/1cb062a3/attachment-0001.html>