X3D and HTML5 - Revision history

Brutzman: /* Goals: X3D and HTML5 */ note historical

2025-05-16T20:21:10Z

‎Goals: X3D and HTML5: note historical

Anita.havele at 05:22, 17 February 2011

2011-02-17T05:22:10Z

Brutzman: /* Goals: X3D and HTML5 */

2011-02-09T17:41:16Z

‎Goals: X3D and HTML5

Brutzman: /* Goals: X3D and HTML5 */

2011-02-09T17:38:49Z

‎Goals: X3D and HTML5

Brutzman: /* Goals: X3D and HTML5 */

2011-02-09T17:37:51Z

‎Goals: X3D and HTML5

Brutzman: /* Goals: X3D and HTML5 */

2011-02-09T17:33:37Z

‎Goals: X3D and HTML5

Brutzman: /* Goals: X3D and HTML5 */ editorial

2011-02-09T17:33:06Z

‎Goals: X3D and HTML5: editorial

Brutzman: /* Goals: X3D and HTML5 */ rephrase summary of 3 approaches

2011-02-09T17:30:52Z

‎Goals: X3D and HTML5: rephrase summary of 3 approaches

Brutzman: /* Goals: X3D and HTML5 */ status update

2011-02-09T17:28:36Z

‎Goals: X3D and HTML5: status update

Brutzman: /* Goals: X3D and HTML5 */

2011-02-09T17:24:45Z

‎Goals: X3D and HTML5

← Older revision		Revision as of 20:21, 16 May 2025
Line 1:		Line 1:
−	=Goals: X3D and HTML5=	+	[Note: this page is historic, see the [https://www.web3d.org/X3D4 X3D4 page for subsequent progress and success.]
		+
		+
		+	= Design Goals: X3D and HTML5=

	The [http://www.web3D.org/x3d X3D Working Group] has made multiple contributions to the [http://www.w3.org/html/wg W3C HTML Working Group] for the purpose of fully integrating X3D with HTML.		The [http://www.web3D.org/x3d X3D Working Group] has made multiple contributions to the [http://www.w3.org/html/wg W3C HTML Working Group] for the purpose of fully integrating X3D with HTML.

@@ Line 292: / Line 292: @@
 ==X3D and Augmented Reality==
+Coming soon
-TODO build new wiki page with Damon, link to it
 =Future work=
 Some topics might become relevant once HTML5 is established as a formal W3C Recommendation. These are not part of our current planned work.
 * Publishing [http://www.web3d.org/x3d/specifications X3D Specifications] in HTML5
 * Other topics as needed

@@ Line 29: / Line 29: @@
 ** ''Status.'' Deferred until HTML5 working group decides whether or not to provide such a new feature.
-Variations on these approaches are considered as part of [[X3D and HTML5 examples]].
+Example combinations of X3D and HTML (plus variations on these approaches) are considered and demonstrated as part of [[X3D and HTML5 examples]].
 Important new work includes the [http://www.x3DOM.org X3DOM suite] by Fraunhofer, which shows native X3D within an HTML page, runnable in nightly builds for Chrome, Firefox and Safari.  Additional implementations are being considered, and similar solutions are being pursued for Internet Explorer and Opera.

@@ Line 19: / Line 19: @@
 remains online and is available for comment.
-We have pursued three basic approaches to display an X3D scene inside an HTML page.
+We have pursued three basic approaches to display an X3D scene inside an HTML page:
 * '''X3D object in HTML page as an embedded object.''' HTML page includes an [http://dev.w3.org/html5/spec/Overview.html#the-object-element object] element tag that refers to an .x3d scene, implemented via an X3D plugin.  Data can be passed within the page to/from an X3D scene using DOM events.
 ** ''Status.'' This is specification-compliant and demonstrated by multiple plugins.

@@ Line 11: / Line 11: @@
 In order to reach their primary goals in a timely manner, the HTML5 group has decided not to pursue the forms of extensibility that we proposed.
 <!-- TODO add link -->
 Our technical proposal
 [http://www.web3d.org/x3d/content/html5/HTML5RecommendationAdditionsForX3D.html HTML5 Recommendation Additions for X3D]

@@ Line 18: / Line 18: @@
 We have pursued three basic approaches to display an X3D scene inside an HTML page.
-* ''X3D object in HTML page as an embedded object.'' HTML page includes an [http://dev.w3.org/html5/spec/Overview.html#the-object-element object] element tag that refers to an .x3d scene, implemented via an X3D plugin.  Data can be passed within the page to/from an X3D scene using DOM events.
+* '''X3D object in HTML page as an embedded object.''' HTML page includes an [http://dev.w3.org/html5/spec/Overview.html#the-object-element object] element tag that refers to an .x3d scene, implemented via an X3D plugin.  Data can be passed within the page to/from an X3D scene using DOM events.
 ** ''Status.'' This is specification-compliant and demonstrated by multiple plugins.
-* ''X3D directly inline as XML in HTML.'' HTML page directly includes X3D source, likely with an XML namespace prefix, presumably implemented via an X3D plugin or the browser itself.  Again data might be exchanged within the page using DOM events.
+* '''X3D directly inline as XML in HTML.''' HTML page directly includes X3D source, likely with an XML namespace prefix, presumably implemented via an X3D plugin or the browser itself.  Again data might be exchanged within the page using DOM events.
 ** ''Status.'' Experimentally demonstrated as a new capability by [http://www.x3dom.org X3DOM], and now being considered for further implementation and potential standardization in a Mobile and/or Augmented Reality (AR) profile for X3D.
-* ''Canvas3D or special API access.'' HTML page includes some form of [http://dev.w3.org/html5/spec/Overview.html#the-canvas-element canvas] (or maybe <code>Canvas3D</code>) element that allows programmatic access to the page, so that X3D Scene Access Interface (SAI) might draw a bitmap.
+* '''Canvas3D or special API access.''' HTML page includes some form of [http://dev.w3.org/html5/spec/Overview.html#the-canvas-element canvas] (or maybe <code>Canvas3D</code>) element that allows programmatic access to the page, so that X3D Scene Access Interface (SAI) might draw a bitmap.
 ** ''Status.'' Deferred until HTML5 working group decides whether or not to provide such a new feature.

@@ Line 18: / Line 18: @@
 We have pursued three basic approaches to display an X3D scene inside an HTML page.
-* ''(External reference)'' HTML page includes an [http://dev.w3.org/html5/spec/Overview.html#the-object-element object] element tag that refers to an .x3d scene, implemented via an X3D plugin.  Data might be passed within the page using DOM events.  This is specification-compliant and demonstrated by multiple plugins.
+* ''X3D object in HTML page as an embedded object.'' HTML page includes an [http://dev.w3.org/html5/spec/Overview.html#the-object-element object] element tag that refers to an .x3d scene, implemented via an X3D plugin.  Data might be passed within the page using DOM events.  This is specification-compliant and demonstrated by multiple plugins.
-* ''(X3D as XML in HTML)'' HTML page directly includes X3D source, likely with an XML namespace prefix, presumably implemented via an X3D plugin or the browser itself.  Again data might be exchanged within the page using DOM events.  Experimentally demonstrated by [http://www.x3dom.org X3D], and now being considered for further implementation and potential standardization.
+* ''X3D directly inline as XML in HTML.'' HTML page directly includes X3D source, likely with an XML namespace prefix, presumably implemented via an X3D plugin or the browser itself.  Again data might be exchanged within the page using DOM events.  Experimentally demonstrated as a new capability by [http://www.x3dom.org X3D], and now being considered for further implementation and potential standardization in a Mobile and/or Augmented Reality (AR) profile for X3D.
-* ''(API access)'' HTML page includes some form of [http://dev.w3.org/html5/spec/Overview.html#the-canvas-element canvas] (or maybe <code>Canvas3D</code>) element that allows programmatic access to the page, so that X3D Scene Access Interface (SAI) might draw a bitmap.  Deferred until HTML5 working group decides whether or not to provide such a new feature.
+* ''Canvas3D or special API access.'' HTML page includes some form of [http://dev.w3.org/html5/spec/Overview.html#the-canvas-element canvas] (or maybe <code>Canvas3D</code>) element that allows programmatic access to the page, so that X3D Scene Access Interface (SAI) might draw a bitmap.  Deferred until HTML5 working group decides whether or not to provide such a new feature.
 Variations on these approaches are considered as part of [[X3D and HTML5 examples]].

@@ Line 1: / Line 1: @@
 =Goals: X3D and HTML5=
-The [http://www.web3D.org/x3d X3D Working Group] has made multiple contributions to the [http://www.w3.org/html/wg HTML Working Group] for the purpose of fully integrating X3D with HTML.
+The [http://www.web3D.org/x3d X3D Working Group] has made multiple contributions to the [http://www.w3.org/html/wg W3C HTML Working Group] for the purpose of fully integrating X3D with HTML.
 Our long-term goal is to make the native authoring and use of declarative XML-based X3D scenes as natural and well-supported for HTML5 authors as the support provided for
@@ Line 18: / Line 18: @@
 We have pursued three basic approaches to display an X3D scene inside an HTML page.
-* (External reference) HTML page includes an [http://dev.w3.org/html5/spec/Overview.html#the-object-element object] element tag that refers to an .x3d scene, implemented via an X3D plugin.  Data might be passed within the page using DOM events.
+* ''(External reference)'' HTML page includes an [http://dev.w3.org/html5/spec/Overview.html#the-object-element object] element tag that refers to an .x3d scene, implemented via an X3D plugin.  Data might be passed within the page using DOM events.  This is specification-compliant and demonstrated by multiple plugins.
-* (X3D as XML in HTML) HTML page directly includes X3D source, likely with an XML namespace prefix, presumably implemented via an X3D plugin or the browser itself.  Again data might be exchanged within the page using DOM events.
+* ''(X3D as XML in HTML)'' HTML page directly includes X3D source, likely with an XML namespace prefix, presumably implemented via an X3D plugin or the browser itself.  Again data might be exchanged within the page using DOM events.  Experimentally demonstrated by [http://www.x3dom.org X3D], and now being considered for further implementation and potential standardization.
-* (API access) HTML page includes some form of [http://dev.w3.org/html5/spec/Overview.html#the-canvas-element canvas] (or maybe <code>Canvas3D</code>) element that allows programmatic access to the page, so that X3D Scene Access Interface (SAI) might draw a bitmap
+* ''(API access)'' HTML page includes some form of [http://dev.w3.org/html5/spec/Overview.html#the-canvas-element canvas] (or maybe <code>Canvas3D</code>) element that allows programmatic access to the page, so that X3D Scene Access Interface (SAI) might draw a bitmap.  Deferred until HTML5 working group decides whether or not to provide such a new feature.
 Variations on these approaches are considered as part of [[X3D and HTML5 examples]].