[x3d-public] Refinement of X3D JSON

[Brutzman, Donald (Don) (CIV)]

Thanks for clear thinking on this John.  Quite right, I agree.  Looks good as is.

	X3D JSON Encoding
	https://www.web3d.org/wiki/index.php/X3D_JSON_Encoding

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


On 7/24/2019 7:53 AM, John Carlson wrote:
> 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.
> 
> John
> 
> Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10
> 
> *From: *John Carlson <mailto:yottzumm at gmail.com>
> *Sent: *Wednesday, July 24, 2019 9:30 AM
> *To: *Brutzman, Donald (Don) (CIV) <mailto:brutzman at nps.edu>
> *Cc: *X3D Graphics public mailing list <mailto:x3d-public at web3d.org>
> *Subject: *Refinement of X3D JSON
> 
> Don,
> 
> 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.
> 
> Thanks,
> 
> John
> 
> Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10
> 
> *From: *John Carlson <mailto:yottzumm at gmail.com>
> *Sent: *Tuesday, July 23, 2019 7:14 PM
> *To: *Brutzman, Donald (Don) (CIV) <mailto:brutzman at nps.edu>; Peitso, Loren (CIV) <mailto:lepeitso at nps.edu>; Masaki Aono <mailto:aono at tut.jp>
> *Cc: *X3D Graphics public mailing list <mailto:x3d-public at web3d.org>
> *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.
> 
> John
> 


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