[x3d-public] Refinement of X3D JSON

John Carlson yottzumm at gmail.com
Wed Jul 24 07:53:14 PDT 2019

I think what you may run into is identical meta, component and unit keys which erase each other. JSON != Python.

We can try such a thing with the other encodings, Python, Java, JavaScript, but I think JSON may be a special beast.

I certainly hope we do not repeat a previous discussion of this “feature” of JavaScript.  I tried searching for “Crockford” in my email, but couldn’t narrow down specifics yet

Waiting on your JSON example to critique.


Sent from Mail for Windows 10

From: John Carlson
Sent: Wednesday, July 24, 2019 9:30 AM
To: Brutzman, Donald (Don) (CIV)
Cc: X3D Graphics public mailing list
Subject: Refinement of X3D JSON


How would you suggest carrying meta, component and unit into an XML document if the text isn’t present in the JSON?

Please show a JSON example, of HelloWorldProgramOutput.json with your new scheme.



Sent from Mail for Windows 10

From: John Carlson
Sent: Tuesday, July 23, 2019 7:14 PM
To: Brutzman, Donald (Don) (CIV); Peitso, Loren (CIV); Masaki Aono
Cc: X3D Graphics public mailing list
Subject: RE: native Python package for X3D

>John, please notice that I think a refinement in X3D JSON encoding is possible.  The X3D 'head' statement can only accept three other statements, meta component and unit.  Rather than separate field names for each, we should just lump them together under 'children' just as occurs with Scene.

So children of head?  I’ll have to think about that.  I agree that I’ve probably special case coded most of that.  Probably won’t be a problem if I remove the special case coding.   Just a lot of testing needs to be done.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20190724/e3679818/attachment.html>

More information about the x3d-public mailing list