Difference between revisions of "X3D version 3.4 Development"

From Web3D.org
Jump to: navigation, search
m
Line 8: Line 8:
 
* '''Appearance'''
 
* '''Appearance'''
 
** '''Materials''': advanced parameters
 
** '''Materials''': advanced parameters
** [[X3D Multitexture | Multitexture]] is undergoing review for correctness, completeness and conformance of rendering example scenes
+
** [[X3D Multitexture | Multitexture]]: review for correctness, completeness and conformance of rendering example scenes
 
** '''Rendering''': bump maps, shadows
 
** '''Rendering''': bump maps, shadows
 
** [http://www.web3d.org/files/specifications/19775-1/V3.3/Part01/components/shaders.html Shaders]: improved support and better interoperability, library of examples
 
** [http://www.web3d.org/files/specifications/19775-1/V3.3/Part01/components/shaders.html Shaders]: improved support and better interoperability, library of examples

Revision as of 16:10, 2 October 2013

X3D version 3.4 Development efforts are evolutionary improvements to the widely proven X3D Graphics architecture.

Web3D Consortium working groups currently define specification goals and requirements. We publicly reviewed these goals during Web3D 2013 and SIGGRAPH 2013 conference meetings this summer.

Topics on this list are not guaranteed to be completed - work proceeds based on Web3D Consortium Member priorities.

All suggestions and recommendations are welcome. Component improvements and additions are approved by Web3D Consortium members.

Please contact us if you think additional technologies need to be considered.

Backwards and forward compatibility

Thanks to careful design and insistence on implementation/evaluation, the X3D International Standard has maintained both steady growth and interoperability ever since Virtual Reality Modeling Language (VRML) in 1997. This track record of stability and innovation is among the best in the 3D graphics industry.

X3D version 4.0 Development efforts are focused on HTML5/Declarative 3D/X3DOM and Augmented Reality Continuum (ARC) technologies, which may require architectural changes. Some new technologies may get pushed from 4.0 to 3.4 (or back again) after careful consideration by the respective working groups.

  • As with all other X3D components, all work is defined in the abstract specification has corresponding file encodings (.x3d .x3dv .x3db) and language bindings (ECMAScript and Java).
  • Compatibility concerns include evolutionary efforts to upgrade the X3D Compressed Binary Encoding (CBE), as described in the X3D Compressed Binary Encoding Call For Contributions.

Schedule

  • X3D CADInterchange/Mobile Profile goal. Working on implementations now, target completion December 2013.
  • X3D Compressed Binary Encoding (CBE) goal. Finish draft by December 2013, review completeness of geometric compression contributions.
  • X3D version 3.4 goal. Review progress in one year at SIGGRAPH 2014, members decide if work continues or draft specification proceeds to ISO.