Difference between revisions of "X3D JSON Encoding"
From Web3D.org
(→Discussion points) |
(→References) |
||
| Line 37: | Line 37: | ||
* XML to JSON Converter (provides option to assign a prefix to JSON attributes, default is @ character) [http://www.freeformatter.com/xml-to-json-converter.html] | * XML to JSON Converter (provides option to assign a prefix to JSON attributes, default is @ character) [http://www.freeformatter.com/xml-to-json-converter.html] | ||
* Apache Camel, XML JSON Data Format (camel-xmljson) [http://camel.apache.org/xmljson.html] | * Apache Camel, XML JSON Data Format (camel-xmljson) [http://camel.apache.org/xmljson.html] | ||
| + | * JSON Definition [http://json.org/] | ||
| + | * JSON Data Interchange Format [http://www.ecma-international.org/publications/files/ECMA-ST/ECMA-404.pdf] | ||
* JSON Markup Language (JsonML) [http://www.jsonml.org/] | * JSON Markup Language (JsonML) [http://www.jsonml.org/] | ||
* XSLTJSON: Transforming XML to JSON using XSLT [http://www.bramstein.com/projects/xsltjson/] | * XSLTJSON: Transforming XML to JSON using XSLT [http://www.bramstein.com/projects/xsltjson/] | ||
Revision as of 15:40, 10 September 2014
Preliminary notes on the creation of an X3D JSON encoding.
- This page is to understand the conversion process so that a high-quality encoding definition can be created
- Don Brutzman started a thread on the X3D-Public list.
Conversion Considerations
Primary design criterion: round-trippable lossless representation of X3D scene.
Conversion approach of greatest practical interest: XML to/from JSON. Issues:
- How to convert attribute names to distinguish them from child elements
- JSON handling of container elements to preserve parent/child relationships, distinguishing child elements from attributes
- Creation of JSON elements with datatypes appropriate to content (e.g., integer, float, strings, etc.)
- Both X3D and JSON can include comments, and so need an option for inclusion (by default) or removal (optional) of comments in order to ensure 100% round-trip conversion capabilities.
- Support for singleton (self-closing) XML tags also needs to be considered
- Inclusion and preservation of embedded XML namespace information in an XML (.x3d) document
Discussion points
Here are suggested discussion points for the X3D teleconference and future followups.
- What are the use cases for having X3D JSON available in JavaScript? It would be good to spell them out and understand them well.
- Is there a good/consistent way for X3DOM to utilize such capabilities?
- Is there a way for Three.js X3D loader, or other javascript libraries, to utilize such capabilities?
- Is there a single authoritative reference for JSON itself? and for JSON-XML conversions?
- Compare compression size and decompression speed of a TestMesh.x3d.json.gz to TestMesh.x3db and TestMesh.x3d.exi (EXI will likely win because it includes data typing)
- Once a canonical form for X3D as JSON is established, add conversion capabilities to X3D-Edit and also autoconvert, test and publish JSON for all of the 3800+ scenes in the X3D Examples Archives
- Decide if this capability needs to be defined in one of the X3D standards, or perhaps as an X3D best practice.
- Probably lots more... What else?
Contributors
- LD - Leonard Daly
- DPB - Don Brutzman
References
- XML to JSON Converter (provides option to assign a prefix to JSON attributes, default is @ character) [3]
- Apache Camel, XML JSON Data Format (camel-xmljson) [4]
- JSON Definition [5]
- JSON Data Interchange Format [6]
- JSON Markup Language (JsonML) [7]
- XSLTJSON: Transforming XML to JSON using XSLT [8]
- Converting Between XML and JSON [9]
- XML/JSON Perl Converter [10]
- IBM's PHP converter [11]
- Java Converter [12]
- Google Code Library [13]
