Web3D.org - User contributions [en]

X3D JSON Encoding

2015-04-08T15:50:36Z

Rpuk: /* Standardization */

These are X3D Working Group notes on the creation of an X3D JSON encoding and a corresponding conversion process.

== Design Requirements, Goals and Use Cases ==

Design requirement:
* Round-trippable encoding supporting X3D abstract specification

Design goals:
* Exchange format for a variety of 3D geometry and scene graphs
* Loader for various JavaScript-controlled renderers
* Manipulate a scene graph using JavaScript

Are there any special use cases for having X3D JSON available in JavaScript?
* Are there any use cases that might modify how X3D is represented in JSON?
* If so, it would be good to spell them out and understand them well.
* We want conversion rules to permit implementations that can achieve user goals.

== Initial implementations ==

* Experimental [http://www.web3d.org/x3d/stylesheets/X3dToJson.xslt X3dToJson.xslt] stylesheet converts .x3d into .json encoding. In version control at [https://sourceforge.net/p/x3d/code/HEAD/tree/www.web3d.org/x3d/stylesheets/X3dToJson.xslt sourceforge]
** Current work: lists of comments; field/fieldValue representations for Scripts and prototypes
* Embedded in [https://savage.nps.edu/X3D-Edit/ X3D-Edit] for testing
* Initial Hello World examples deployed ([http://x3dgraphics.com/examples/X3dForAdvancedModeling/HelloWorldScenes/HelloWorld.x3d .x3d]) ([http://x3dgraphics.com/examples/X3dForAdvancedModeling/HelloWorldScenes/HelloWorld.html .html]) ([http://x3dgraphics.com/examples/X3dForAdvancedModeling/HelloWorldScenes/HelloWorld.xhtml x3dom .xhtml]) ([http://x3dgraphics.com/examples/X3dForAdvancedModeling/HelloWorldScenes/HelloWorld.json .json])
* Conversion syntax discussions continue on [http://web3d.org/pipermail/x3d-public_web3d.org/2014-October/002981.html x3dom-developers mail list] (with [http://www.x3dom.org/x3dom/test/functional/flipper.html "dump scene as json" test] by Dr. Yvonne Jung)

== 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. Resolution: "@attributeName".
# JSON handling of container elements to preserve parent/child relationships, distinguishing child elements from attributes Resolution: use SFNode/MFNode field names as unique keys.
# Creation of JSON elements with datatypes appropriate to content (e.g., integer, float, strings, etc.). Note special JSON rules for floats (not equivalent to IEEE floats).
# 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, without loss of generality.
# Inclusion and preservation of embedded XML namespace information in an XML (.x3d) document: might not be necessary or possible.

== Standardization ==

Probably smartest to first start out defining an X3D best practice.

This capability likely needs to be defined as one of the [http://www.web3d.org/specifications/X3dSpecificationRelationships.png X3D standards]. The most probable place to put it is as a new Part 5 to ISO/IEC 19776. In this manner, it would correspond to the XML, Classic VRML, and Compressed Binary encodings.

== Discussion points ==

Here are suggested discussion points for X3D teleconferences and future followups.

# Is there a good/consistent way for X3DOM to utilize such capabilities?
# Is there a way for [http://threejs.org 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? See [6] for the JSON Data Interchange Format, need to confirm no others.
# What is the right file extension? .json, .x3dj or something else
# Can a file reader distinguish the incoming encodings (.x3d .x3dv .x3db .x3de .json) independent of file extension or MIME media type?
# 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 [http://www.web3d.org/x3d-resources/content/examples/X3dResources.html#Examples X3D Examples Archives]
# 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)

Probably lots more... What else?

== References ==

* 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
* JavaScript Object Notation (JSON) Definition http://json.org
* ECMA 404: JSON Data Interchange Format (Final Draft) http://www.ecma-international.org/publications/files/ECMA-ST/ECMA-404.pdf
* JSON Markup Language (JsonML) http://www.jsonml.org/
* XSLTJSON: Transforming XML to JSON using XSLT http://www.bramstein.com/projects/xsltjson
* Converting Between XML and JSON http://www.xml.com/pub/a/2006/05/31/converting-between-xml-and-json.html
* XML/JSON Perl Converter http://search.cpan.org/~ken/XML-XML2JSON-0.06/lib/XML/XML2JSON.pm
* IBM's PHP converter http://www.ibm.com/developerworks/library/x-xml2jsonphp
* Java Converter http://www.json.org/javadoc/org/json/XML.html
* Google Code Library https://code.google.com/p/x2js

'''Mailing list discussions'''
* 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]

X3D JSON Encoding

2015-04-08T15:48:36Z

Rpuk: /* Standardization */

These are X3D Working Group notes on the creation of an X3D JSON encoding and a corresponding conversion process.

== Design Requirements, Goals and Use Cases ==

Design requirement:
* Round-trippable encoding supporting X3D abstract specification

Design goals:
* Exchange format for a variety of 3D geometry and scene graphs
* Loader for various JavaScript-controlled renderers
* Manipulate a scene graph using JavaScript

Are there any special use cases for having X3D JSON available in JavaScript?
* Are there any use cases that might modify how X3D is represented in JSON?
* If so, it would be good to spell them out and understand them well.
* We want conversion rules to permit implementations that can achieve user goals.

== Initial implementations ==

* Experimental [http://www.web3d.org/x3d/stylesheets/X3dToJson.xslt X3dToJson.xslt] stylesheet converts .x3d into .json encoding. In version control at [https://sourceforge.net/p/x3d/code/HEAD/tree/www.web3d.org/x3d/stylesheets/X3dToJson.xslt sourceforge]
** Current work: lists of comments; field/fieldValue representations for Scripts and prototypes
* Embedded in [https://savage.nps.edu/X3D-Edit/ X3D-Edit] for testing
* Initial Hello World examples deployed ([http://x3dgraphics.com/examples/X3dForAdvancedModeling/HelloWorldScenes/HelloWorld.x3d .x3d]) ([http://x3dgraphics.com/examples/X3dForAdvancedModeling/HelloWorldScenes/HelloWorld.html .html]) ([http://x3dgraphics.com/examples/X3dForAdvancedModeling/HelloWorldScenes/HelloWorld.xhtml x3dom .xhtml]) ([http://x3dgraphics.com/examples/X3dForAdvancedModeling/HelloWorldScenes/HelloWorld.json .json])
* Conversion syntax discussions continue on [http://web3d.org/pipermail/x3d-public_web3d.org/2014-October/002981.html x3dom-developers mail list] (with [http://www.x3dom.org/x3dom/test/functional/flipper.html "dump scene as json" test] by Dr. Yvonne Jung)

== 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

== Standardization ==

Probably smartest to first start out defining an X3D best practice.

This capability likely needs to be defined as one of the [http://www.web3d.org/specifications/X3dSpecificationRelationships.png X3D standards]. The most probable place to put it is as a new part to ISO/IEC 19776. In this manner, it would correspond to the XML, Classic VRML, and Compressed Binary encodings.

== Discussion points ==

Here are suggested discussion points for X3D teleconferences and future followups.

# Is there a good/consistent way for X3DOM to utilize such capabilities?
# Is there a way for [http://threejs.org 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? See [6] for the JSON Data Interchange Format, need to confirm no others.
# What is the right file extension? .json, .x3dj or something else
# Can a file reader distinguish the incoming encodings (.x3d .x3dv .x3db .x3de .json) independent of file extension or MIME media type?
# 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 [http://www.web3d.org/x3d-resources/content/examples/X3dResources.html#Examples X3D Examples Archives]
# 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)

Probably lots more... What else?

== References ==

* 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
* JavaScript Object Notation (JSON) Definition http://json.org
* ECMA 404: JSON Data Interchange Format (Final Draft) http://www.ecma-international.org/publications/files/ECMA-ST/ECMA-404.pdf
* JSON Markup Language (JsonML) http://www.jsonml.org/
* XSLTJSON: Transforming XML to JSON using XSLT http://www.bramstein.com/projects/xsltjson
* Converting Between XML and JSON http://www.xml.com/pub/a/2006/05/31/converting-between-xml-and-json.html
* XML/JSON Perl Converter http://search.cpan.org/~ken/XML-XML2JSON-0.06/lib/XML/XML2JSON.pm
* IBM's PHP converter http://www.ibm.com/developerworks/library/x-xml2jsonphp
* Java Converter http://www.json.org/javadoc/org/json/XML.html
* Google Code Library https://code.google.com/p/x2js

'''Mailing list discussions'''
* 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]

Web3D 2014 Workshops on X3D Evolution/Revolution

2014-07-23T23:36:18Z

Rpuk: /* Looking ahead */

The Web3D 2014 Conference [http://web3d2014.web3d.org/program program schedule] includes multiple [http://web3d2014.web3d.org/workshops X3D Workshops on Future Graphics Standards].

''Moderators:'' Don Brutzman (Naval Postgraduate School), Dick Puk (Intelligraphics) and Leonard Daly (Daly Realism).

This page elaborates on the agenda topics. We are collaboratively adding key points. Volunteer scribes will keep minutes so that a workshop report emerges.

== X3D Compressed Binary Encoding (CBE) Geometric-Compression Algorithm Candidates ==

Scheduled time: 0900-1030. Goal outcomes:

=== Review and improve all published plans & milestones ===

=== Review Fraunhofer geometric-compression approach in detail, compare to all of the established X3D metrics ===

=== Summary of Efficient XML Interchange (EXI) data compression and XML Security to replace Fast Infoset (FI) in existing X3D CBE Specification ===

=== Shall we have a public mesh “contest” or “bakeoff” to confirm that your approach is ready for prime time? ===

=== Decide on readiness to proceed with next milestones ===

== X3D 3.4 Evolution ==

Scheduled time: 0900-1030. Goal outcomes:

=== Review all planned technology additions ===

=== Determine technology and specification contributors, responsible working groups ===
* CAD
* H-Anim
* Geospatial

=== X3D JSON ===
* Technical quicklook
* Where to define an encoding in X3D Specifications

=== Achieving two independent implementations and X3D scene conformance tests ===

=== Next steps and 2014 timeline ===

== Lunch discussions ==

Scheduled time: 1200-1300. Participants will order lunch in the morning, sandwiches to be delivered to the meeting room.

== X3D 4.0 / X3DOM / HTML5 Revolution ==

Scheduled time: 1300-1500. Goal outcomes:

=== Review and improve all published plans & milestones ===

=== Confirm status of technology components, add to v3.4 list as appropriate ===

=== Evolution/convergence strategy for X3D 4.0, X3DOM, HTML5 ===

Lots of great progress! What's next? Discussion.

=== Mixed Augmented Reality (MAR) Reference Model ===

Status and plans quicklook.

* ISO SC24/SC29 MAR Joint Ad Hoc Group (JAHG), Gerry Kim and Marius Preda
* X3D MAR implementation exemplar efforts, Gun Lee and Timo Engelke
* Flag any potential conflicts

=== Decide on next steps and milestones for 2014 ===

* Preview: ISO/IEC JTC1 SC24 meeting agenda, 18-22 August 2014, Seattle Washington

== BIM/AEC/AM/CAD Initiatives ==

X3D Computer-Aided Design (CAD) Working Group

* Agenda review and welcome discussion

* Demonstration: [http://www.web3d.org/example/cad-scene-graph-viewer CAD Scene Graph and Part Viewing] (including [http://examples.x3dom.org/cadViewer/slimViewerEngine/index.html direct link])

* Our game plan today: key points, demo, talk! repeat for each topic.

=== Progress and planned work ===

* [http://sourceforge.net/projects/jgeom jgeom] and [http://www.web3d.org/documents/specifications/19775-1/V3.3/Part01/components/nurbs.html X3D NURBS component support]
* [http://www.web3d.org/wiki/index.php/Xj3D_Evolution Xj3D Evolution]

=== Recent activities and developments ===

* Architecture Engineering Construction (AEC)
** AEC Hackathon
** CIS/2

* Building Information Modeling (BIM)
** BimServer by Dave Arendash

* Additive Manufacturing (AM) aka 3D Printing
** Shapeways publication of X3D models
** [http://3dprint.nih.gov NIH 3D Print Exchange]

* Additive Manufacturing File Format (AMFF)
** Track down and link our meeting minutes assessment
** Can we perform this work to map transformations between the two standards?

* Cultural Heritage
** Workshop, keynote, other activity coming up
** Lots of shared imperatives for metadata modeling within X3D scenes

Additional topics welcome

=== Looking ahead ===

For the next year:
* What common work can we do together?
* What is our timetable of goals?
* Who else should we be talking to?
* What new features are needed?

X3D version 4.0 Development

2013-11-13T16:24:00Z

Rpuk:

[[X3D version 4.0 Development]] efforts are considering potentially major additions to the baseline X3D architecture.

* [http://web3d.org/wiki/images/f/f2/X3DOM_4_WebGL_audience_10_2013.pdf Summary slides here (Oct 2013)]
* Major technology under consideration: [http://www.web3d.org/wiki/index.php/X3D_and_HTML5 HTML5], [http://www.w3.org/community/declarative3d/ Declarative 3D], [http://www.x3dom.org X3DOM]
* Major technology under consideration: [http://www.web3d.org/wiki/index.php/X3D_and_Augmented_Reality Augmented Reality Continuum (ARC)]
* Relaxing prior design constraints can enable a broader new basis for X3D integration
* Normalizing interaction semantics with HTML5 might further open up X3D for Web authors

Please [http://www.web3d.org/realtime-3d/contact contact us] if you think additional technologies need to be considered. X3D futures planning is currently a Web3D Consortium member-only activity.

== Backwards and forwards compatibility ==

* A major benefit of using the X3D standard is full backwards compatibility with prior VRML97 and X3D content
* [[X3D version 3.4 Development]] is proceeding in parallel to enable continued evolution of the current X3D architecture
* Our goal is to maximize, but not necessarily require, backwards compatibility in version 4.0 with the version 3.x specifications
** A great majority of X3D nodes and features are likely achievable without change
** Some X3D features may require import/export conversion for compatibility (event model reconciliation, ROUTEs and sensors perhaps)
** A few features might be refactored, deprecated or obsoleted (none yet identified)
* ECMAscript (JavaScript) support needs to be upgraded to new standard: ISO/IEC 16262:2011 Information technology — ECMAScript language specification.

The comprehensive forward compatibility of VRML97 and X3D with later-developed X3D versions shows that careful anticipatory design is achievable.

== Open questions ==
* Are ARC abstract design and X3D AR proposals sufficiently mature to enable integration with HTML5/Declarative 3D/X3DOM issues?
* Are the previously X3D Layer/Layering components compatible with HTML5 overlay model? Are they still needed, perhaps for multiscreen or CAVE support?
* Mashup and interoperability support: is anything else needed for broader use with the Web? YouTube etc.

== Schedule ==
* Active development of X3D and X3DOM content is tracking HTML 5 capabilities now
* We participate and contribute to the W3C Community Group for [http://www.w3.org/community/declarative3d Declarative 3D]

X3D CAD People

2011-12-20T18:27:22Z

Rpuk:

[[X3D CAD]] working group members: please add short-summary descriptions of your interests in X3D CAD efforts.

== Don Brutzman ==

* [http://www.nps.edu Naval Postgraduate School] USA

== William O. Glascoe III==
My interests in X3D are three fold
1. enabler to bridge the "air gap" between the CAD flowing in products' supply chain and the CAD-less consumer chain
2. enabler to bridge the "intellectual gap" between 'patients' and healthcare providers via anthropomorphic interface to health states: past, present and planned
3. catalyst to the DoD perennial challenge of enterprise wide modeling and simulation composition

== Michele Foti ==

== Hyokwang Lee ==

* [http://www.PartDB.com PartDB] and [http://www.web3d.kr Web3D Korea Chapter]

== Vince Marchetti ==

== Christophe Mouton ==

== Marc Petit ==

* [http://france.edf.com Electricite de France (EDF)]

== Dick Puk ==
President, [http://www.igraphics.com Intelligraphics Incorporated], consultants in computer graphics. Also, liaison from ISO/IEC JTC1/SC24 to the Web3D Consortium and editor of the X3D standards. Convener of ISO/IEC JTC1/SC24/WG6.

X3D CAD People

2011-12-20T18:25:30Z

Rpuk:

[[X3D CAD]] working group members: please add short-summary descriptions of your interests in X3D CAD efforts.

== Don Brutzman ==

* [http://www.nps.edu Naval Postgraduate School] USA

== William O. Glascoe III==
My interests in X3D are three fold
1. enabler to bridge the "air gap" between the CAD flowing in products' supply chain and the CAD-less consumer chain
2. enabler to bridge the "intellectual gap" between 'patients' and healthcare providers via anthropomorphic interface to health states: past, present and planned
3. catalyst to the DoD perennial challenge of enterprise wide modeling and simulation composition

== Michele Foti ==

== Hyokwang Lee ==

* [http://www.PartDB.com PartDB] and [http://www.web3d.kr Web3D Korea Chapter]

== Vince Marchetti ==

== Christophe Mouton ==

== Marc Petit ==

* [http://france.edf.com Electricite de France (EDF)]

== Dick Puk ==
President, Intelligraphics Incorporated, consultants in computer graphics. Also, liaison from ISO/IEC JTC1/SC24 to the Web3D Consortium and editor of the X3D standards. Convener of ISO/IEC JTC1/SC24/WG6.