Difference between revisions of "X3D and HTML5 Summary"
From Web3D.org
m |
m |
||
| Line 7: | Line 7: | ||
* Relationships between scene graphs, APIs and render layers; | * Relationships between scene graphs, APIs and render layers; | ||
** Scene graphs are high-level declarative models about how geometry is constructed, colored and animated; these can be expressed as an XML tree | ** Scene graphs are high-level declarative models about how geometry is constructed, colored and animated; these can be expressed as an XML tree | ||
| − | ** APIs are mid-level libraries for programmers to create imperative source code about geometry and animation | + | ** APIs are mid-level libraries for programmers to create imperative source code about geometry and animation (various proprietary codebases, O3D, perhaps WebGL) |
| − | ** Render layers are low-level software libraries that expose the functionality of graphics hardware (e.g. OpenGL, DirectX | + | ** Render layers are low-level software libraries that expose the functionality of graphics hardware (e.g. OpenGL, DirectX) |
| Line 17: | Line 17: | ||
** All three languages have XML encodings | ** All three languages have XML encodings | ||
** Authors want to use these languages for multimedia content in HTML pages | ** Authors want to use these languages for multimedia content in HTML pages | ||
| + | |||
* Simple X3D example and HTML5 examples; (how current integration looks like via object model then to html5) | * Simple X3D example and HTML5 examples; (how current integration looks like via object model then to html5) | ||
| − | ** X3D scene as external reference | + | ** X3D scene as external reference (Anchor link) |
** X3D as embedded object; | ** X3D as embedded object; | ||
** HTML5 with embedded x3d as mixed namespaces; | ** HTML5 with embedded x3d as mixed namespaces; | ||
** Template for demo = html5+x3d event passing connections. | ** Template for demo = html5+x3d event passing connections. | ||
| + | |||
* Recommendations for html5 specification. | * Recommendations for html5 specification. | ||
Revision as of 15:40, 6 October 2009
- Family of X3D Specifications;
- X3D Abstract Specification describes basic functionality
- XML, ClassicVRML, and Compressed Binary Encoding
- Application Programming Interfaces (APIs) Ecmascript (Javascript) and Java
- Relationships between scene graphs, APIs and render layers;
- Scene graphs are high-level declarative models about how geometry is constructed, colored and animated; these can be expressed as an XML tree
- APIs are mid-level libraries for programmers to create imperative source code about geometry and animation (various proprietary codebases, O3D, perhaps WebGL)
- Render layers are low-level software libraries that expose the functionality of graphics hardware (e.g. OpenGL, DirectX)
- Similarities between MathML, SVG, and X3D;
- MathML describes mathematical expressions and then presents a rendering of them
- Scalable Vector Graphics (SVG) describes and presents renderings of 2D shapes, with optional animation
- Extensible 3D (X3D) describes and presents renderings of 2D shapes, with optional animation
- All three languages have XML encodings
- Authors want to use these languages for multimedia content in HTML pages
- Simple X3D example and HTML5 examples; (how current integration looks like via object model then to html5)
- X3D scene as external reference (Anchor link)
- X3D as embedded object;
- HTML5 with embedded x3d as mixed namespaces;
- Template for demo = html5+x3d event passing connections.
- Recommendations for html5 specification.
