Difference between revisions of "X3D version 4.0 Development"

From Web3D.org
Jump to: navigation, search
m
(link arc)
Line 2: Line 2:
  
 
* 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_HTML5 HTML5], [http://www.w3.org/community/declarative3d/ Declarative 3D], [http://www.x3dom.org X3DOM]
* Major technology under consideration: Augmented Reality Continuum (ARC)
+
* 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
 
* 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
 
* Normalizing interaction semantics with HTML5 might further open up X3D for Web authors

Revision as of 01:04, 20 June 2013

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

  • Major technology under consideration: HTML5, Declarative 3D, X3DOM
  • Major technology under consideration: 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 contact us if you think additional technologies need to be considered. X3D futures planning is currently a Web3D Consortium member-only activity.

Backwards and forward compatibility

  • A major benefit of using the X3D standard is full backwards compatibility with prior VRML97 and X3D content
  • Continued growth for the current X3D architecture continues with X3D version 3.4 Development
  • Our goal is to maximize, but not necessarily require, backwards compatibility in version 4.0
    • A great majority of X3D nodes and features are likely achievable without change
    • Some X3D features may require import/export conversion for compatibility (ROUTEs and sensors perhaps)
    • A few features might be refactored, deprecated or obsoleted (none yet identified)

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