[x3d-public] Minutes from today's X3D meeting on JSON

[Leonard Daly]

Here are the draft minutes from today's X3D Working Group meeting on the 
X3D JSON encoding. Please reply to the list if you have anything to add. 
We plan on having another meeting in about a month (most likely April 9 
or 16). An announcement will be sent the end of March/beginning of April.


*X3D Working Group Meeting*

*Wednesday, 2015-03-11*

*  *

*  *

*Attendees:*  Leonard Daly, John Carlson, Roy Walmsley, Cecile Muller, Dick Puk, Anita Havele, Don Brutzman, Nicholas Polys (late)**

Topic:*Open Discussion on JSON Encoding*

/Meeting started at 8:06/

1.Introductions (All)

2.Statement of current encoding [5 minutes]

2.1.References

2.1.1.http://www.web3d.org/wiki/index.php/X3D_JSON_Encoding

2.1.2.http://web3d.org/pipermail/x3d-public_web3d.org/2015-March/003254.html

2.1.3.See 
http://web3d.org/pipermail/x3d-public_web3d.org/2015-March/thread.html#start 
for all thread messages in March 2015.

2.2.Effort requires lots of good people working together.

2.3.Attempting to add another isomorphic encoding (JSON)

2.4.Explicitly defining every field or use “inherent” information

2.5.Douglas Crockford’s book was very important to the latest revision

2.5.1.http://javascript.crockford.com/

2.5.2.https://www.youtube.com/watch?v=v2ifWcnQs6M

2.5.3.http://www.amazon.com/JavaScript-Good-Parts-Douglas-Crockford/dp/0596517742

2.6.Comments are not allowed within JSON. Need to construct containers 
(objects) to hold them to support isomorphic translation to other encodings.

2.7.Array vs. singleton – still an open problem

2.7.1.Currently load XML into memory

2.7.2.Inspect for multiple elements at a single level

2.7.3.Open issue for memory-limited parsers

3.Discussion of issues relating to (2) [25 minutes]

3.1.John’s comments

3.1.1.Use X3DOM, d3.js together

3.1.2.Able to create converter back to X3D

3.1.3.Issue with handling of default values, specifically defaultColor

3.1.4.Working on bijective transformations on all various encodings

3.1.5.Need to resolve inclusion or exclusion of X3D default values

3.1.5.1.Convert to X3D encoding – probably not

3.1.5.2.Use in non-X3D environment – probably needed

3.2.Cecile’s comments

3.2.1.Make it like VRML, but in JSON

3.2.2.Customers prefer JSON because it is “easier” to work with 
(probably easier to read over XML).

3.2.3.Issue with PROTOs and scripts

3.3.Comments in X3D

3.3.1.JSON does not handle internal comments

3.3.2.X3D comments are at the top level are easy to handle

3.3.3.Internal (between fields, nodes, etc.) have issues

3.3.4.Necessary to have comments to support isomorphic transformations

4.Discussion of possible solutions [15 minutes]

4.1.Need to compare to Collada JSON

/Meeting ended at 9:07/





-- 
*Leonard Daly*
X3D Co-Chair
Cloud Consultant
President, Daly Realism - /Creating the Future/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-public_web3d.org/attachments/20150311/95985754/attachment-0001.html>