Difference between revisions of "X3D JSON Encoding"
From Web3D.org
| Line 3: | Line 3: | ||
** Initial message [http://web3d.org/pipermail/x3d-public_web3d.org/2014-July/002854.html] | ** Initial message [http://web3d.org/pipermail/x3d-public_web3d.org/2014-July/002854.html] | ||
** July's thread listing [http://web3d.org/pipermail/x3d-public_web3d.org/2014-July/thread.html] | ** July's thread listing [http://web3d.org/pipermail/x3d-public_web3d.org/2014-July/thread.html] | ||
| − | + | = Conversion Issues = | |
* How to convert attribute names to distinguish them from child elements | * How to convert attribute names to distinguish them from child elements | ||
* Handling of container elements | * Handling of container elements | ||
Revision as of 23:09, 19 August 2014
Preliminary notes on the creation of an X3D JSON encoding.
Conversion Issues
- How to convert attribute names to distinguish them from child elements
- Handling of container elements
- Creation of JSON elements with datatypes appropriate to content (e.g., integer, float, strings, etc.)
- Inclusion of XML namespaces
- Handing of comments in the source
- Don reported that self-closing tags are not missing from his test runs
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 Markup Language (JsonML) [5]
- XSLTJSON: Transforming XML to JSON using XSLT [6]
- Converting Between XML and JSON [7]
- XML/JSON Perl Converter [8]
- IBM's PHP converter [9]
- Java Converter [10]
- Google Code Library [11]
