[html5] r3704 - [e] (0) Revamp how we refer to XHTML, the HTML syntax, and DOM5 HTML in the intr [...]
whatwg at whatwg.org
whatwg at whatwg.org
Sat Aug 29 17:31:20 PDT 2009
Author: ianh
Date: 2009-08-29 17:31:19 -0700 (Sat, 29 Aug 2009)
New Revision: 3704
Modified:
index
source
Log:
[e] (0) Revamp how we refer to XHTML, the HTML syntax, and DOM5 HTML in the intro, hopefully to confuse readers less.
Modified: index
===================================================================
--- index 2009-08-30 00:03:59 UTC (rev 3703)
+++ index 2009-08-30 00:31:19 UTC (rev 3704)
@@ -162,7 +162,7 @@
<li><a href=#relationships-to-other-specifications><span class=secno>1.6 </span>Relationships to other specifications</a>
<ol>
<li><a href=#relationship-to-html4-and-dom2-html><span class=secno>1.6.1 </span>Relationship to HTML4 and DOM2 HTML</a></li>
- <li><a href=#relationship-to-xhtml-1.x><span class=secno>1.6.2 </span>Relationship to XHTML 1.x</a></ol></li>
+ <li><a href=#relationship-to-xhtml1><span class=secno>1.6.2 </span>Relationship to XHTML1</a></ol></li>
<li><a href=#html-vs-xhtml><span class=secno>1.7 </span>HTML vs XHTML</a></li>
<li><a href=#structure-of-this-specification><span class=secno>1.8 </span>Structure of this specification</a>
<ol>
@@ -1219,25 +1219,22 @@
- <h4 id=relationship-to-xhtml-1.x><span class=secno>1.6.2 </span>Relationship to XHTML 1.x</h4>
+ <h4 id=relationship-to-xhtml1><span class=secno>1.6.2 </span>Relationship to XHTML1</h4>
<p><i>This section is non-normative.</i></p>
- <p>This specification is intended to replace XHTML 1.0 as the
- normative definition of the XML serialization of the HTML
- vocabulary. <a href=#refsXHTML10>[XHTML10]</a></p>
+ <p>This specification is intended to replace XHTML1 as the normative
+ definition of the XML serialization of the HTML vocabulary. <a href=#refsXHTML1>[XHTML1]</a></p>
<p>While this specification updates the semantics and requirements
- of the vocabulary defined by XHTML Modularization 1.1 and used by
- XHTML 1.1, it does not attempt to provide a replacement for the
- modularization scheme defined and used by those (and other)
- specifications, and therefore cannot be considered a complete
- replacement for them. <a href=#refsXHTMLMOD>[XHTMLMOD]</a> <a href=#refsXHTML11>[XHTML11]</a></p>
+ of the vocabulary defined by XHTML Modularization 1.1, it does not
+ attempt to provide a replacement for the modularization scheme
+ defined and used by that specification and its companion
+ specifications. <a href=#refsXHTMLMOD>[XHTMLMOD]</a></p>
- <p>Thus, authors and implementors who do not need such a
- modularization scheme can consider this specification a replacement
- for XHTML 1.x, but those who do need such a mechanism are encouraged
- to continue using the XHTML 1.1 line of specifications.</p>
+ <p>Thus, authors and implementors who need such a modularization
+ scheme are encouraged to continue using the XHTML Modularization
+ line of specifications.</p>
@@ -1249,36 +1246,38 @@
documents and applications, and some APIs for interacting with
in-memory representations of resources that use this language.</p>
- <p>The in-memory representation is known as "DOM5 HTML", or "the
- DOM" for short.</p>
+ <p>The in-memory representation is known as "DOM HTML", or "the DOM"
+ for short. This specification defines version 5 of DOM HTML, known
+ as "DOM5 HTML".</p>
<p>There are various concrete syntaxes that can be used to transmit
resources that use this abstract language, two of which are defined
in this specification.</p>
- <p>The first such concrete syntax is "HTML5". This is the format
- recommended for most authors. It is compatible with most legacy Web
- browsers. If a document is transmitted with the <a href=#mime-type>MIME
- type</a> <code><a href=#text/html>text/html</a></code>, then it will be processed as an
- "HTML5" document by Web browsers.</p>
+ <p>The first such concrete syntax is the HTML syntax. This is the
+ format recommended for most authors. It is compatible with most
+ legacy Web browsers. If a document is transmitted with the
+ <a href=#mime-type>MIME type</a> <code><a href=#text/html>text/html</a></code>, then it will be
+ processed as an HTML document by Web browsers. This specification
+ defines version 5 of the HTML syntax, known as "HTML5".</p>
- <p>The second concrete syntax uses XML, and is known as
- "XHTML5". When a document is transmitted with an <a href=#xml-mime-type>XML MIME
- type</a>, such as <code><a href=#application/xhtml+xml>application/xhtml+xml</a></code>, then it is
- treated as an "XHTML5" document by Web browsers, which means that it
- will be handled by an XML processor. Authors are reminded that the
- processing for XML and HTML differs; in particular, even minor
- syntax errors will prevent an XML document from being rendered
- fully, whereas they would be ignored in the "HTML5" syntax.</p>
+ <p>The second concrete syntax is the XHTML syntax, which is an
+ application of XML. When a document is transmitted with an <a href=#xml-mime-type>XML
+ MIME type</a>, such as <code><a href=#application/xhtml+xml>application/xhtml+xml</a></code>, then
+ it is treated as an XML document by Web browsers, to be parsed by an
+ XML processor. Authors are reminded that the processing for XML and
+ HTML differs; in particular, even minor syntax errors will prevent
+ an XML document from being rendered fully, whereas they would be
+ ignored in the HTML syntax. This specification defines version 5 of
+ the XHTML syntax, known as "XHTML5".</p>
- <p>The "DOM5 HTML", "HTML5", and "XHTML5" representations cannot all
- represent the same content. For example, namespaces cannot be
- represented using "HTML5", but they are supported in "DOM5 HTML" and
- "XHTML5". Similarly, documents that use the <code><a href=#the-noscript-element>noscript</a></code>
- feature can be represented using "HTML5", but cannot be represented
- with "XHTML5" and "DOM5 HTML". Comments that contain the string
- "<code title="">--></code>" can be represented in "DOM5 HTML" but
- not in "HTML5" and "XHTML5". And so forth.</p>
+ <p>The DOM, the HTML syntax, and XML cannot all represent the same
+ content. For example, namespaces cannot be represented using the
+ HTML syntax, but they are supported in the DOM and in XML.
+ Similarly, documents that use the <code><a href=#the-noscript-element>noscript</a></code> feature can
+ be represented using the HTML syntax, but cannot be represented with
+ the DOM or in XML. Comments that contain the string "<code title="">--></code>" can be represented in the DOM but not in the
+ HTML syntax or in XML.</p>
<h3 id=structure-of-this-specification><span class=secno>1.8 </span>Structure of this specification</h3>
@@ -73973,16 +73972,11 @@
<dd><cite><a href=http://dev.w3.org/2006/webapi/XMLHttpRequest-2/><code>XMLHttpRequest</code></a></cite>,
A. van Kesteren. W3C, June 2009.</dd>
- <dt id=refsXHTML10>[XHTML10]</dt>
+ <dt id=refsXHTML1>[XHTML1]</dt>
<dd><cite><a href=http://www.w3.org/TR/xhtml1/>XHTML(TM) 1.0 The
Extensible HyperText Markup Language (Second Edition)</a></cite>. W3C,
August 2002.</dd>
- <dt id=refsXHTML11>[XHTML11]</dt>
- <dd><cite><a href=http://www.w3.org/TR/xhtml11/>XHTML(TM) 1.1 -
- Module-based XHTML</a></cite>, M. Altheim, S. McCarron. W3C,
- May 2001.</dd>
-
<dt id=refsXHTMLMOD>[XHTMLMOD]</dt>
<dd><cite><a href=http://www.w3.org/TR/xhtml-modularization>Modularization of
XHTML(TM)</a></cite>, M. Altheim, F. Boumphrey, S. Dooley, S.
Modified: source
===================================================================
--- source 2009-08-30 00:03:59 UTC (rev 3703)
+++ source 2009-08-30 00:31:19 UTC (rev 3704)
@@ -211,26 +211,23 @@
- <h4>Relationship to XHTML 1.x</h4>
+ <h4>Relationship to XHTML1</h4>
<p><i>This section is non-normative.</i></p>
- <p>This specification is intended to replace XHTML 1.0 as the
- normative definition of the XML serialization of the HTML
- vocabulary. <a href="#refsXHTML10">[XHTML10]</a></p>
+ <p>This specification is intended to replace XHTML1 as the normative
+ definition of the XML serialization of the HTML vocabulary. <a
+ href="#refsXHTML1">[XHTML1]</a></p>
<p>While this specification updates the semantics and requirements
- of the vocabulary defined by XHTML Modularization 1.1 and used by
- XHTML 1.1, it does not attempt to provide a replacement for the
- modularization scheme defined and used by those (and other)
- specifications, and therefore cannot be considered a complete
- replacement for them. <a href="#refsXHTMLMOD">[XHTMLMOD]</a> <a
- href="#refsXHTML11">[XHTML11]</a></p>
+ of the vocabulary defined by XHTML Modularization 1.1, it does not
+ attempt to provide a replacement for the modularization scheme
+ defined and used by that specification and its companion
+ specifications. <a href="#refsXHTMLMOD">[XHTMLMOD]</a></p>
- <p>Thus, authors and implementors who do not need such a
- modularization scheme can consider this specification a replacement
- for XHTML 1.x, but those who do need such a mechanism are encouraged
- to continue using the XHTML 1.1 line of specifications.</p>
+ <p>Thus, authors and implementors who need such a modularization
+ scheme are encouraged to continue using the XHTML Modularization
+ line of specifications.</p>
@@ -242,36 +239,39 @@
documents and applications, and some APIs for interacting with
in-memory representations of resources that use this language.</p>
- <p>The in-memory representation is known as "DOM5 HTML", or "the
- DOM" for short.</p>
+ <p>The in-memory representation is known as "DOM HTML", or "the DOM"
+ for short. This specification defines version 5 of DOM HTML, known
+ as "DOM5 HTML".</p>
<p>There are various concrete syntaxes that can be used to transmit
resources that use this abstract language, two of which are defined
in this specification.</p>
- <p>The first such concrete syntax is "HTML5". This is the format
- recommended for most authors. It is compatible with most legacy Web
- browsers. If a document is transmitted with the <span>MIME
- type</span> <code>text/html</code>, then it will be processed as an
- "HTML5" document by Web browsers.</p>
+ <p>The first such concrete syntax is the HTML syntax. This is the
+ format recommended for most authors. It is compatible with most
+ legacy Web browsers. If a document is transmitted with the
+ <span>MIME type</span> <code>text/html</code>, then it will be
+ processed as an HTML document by Web browsers. This specification
+ defines version 5 of the HTML syntax, known as "HTML5".</p>
- <p>The second concrete syntax uses XML, and is known as
- "XHTML5". When a document is transmitted with an <span>XML MIME
- type</span>, such as <code>application/xhtml+xml</code>, then it is
- treated as an "XHTML5" document by Web browsers, which means that it
- will be handled by an XML processor. Authors are reminded that the
- processing for XML and HTML differs; in particular, even minor
- syntax errors will prevent an XML document from being rendered
- fully, whereas they would be ignored in the "HTML5" syntax.</p>
+ <p>The second concrete syntax is the XHTML syntax, which is an
+ application of XML. When a document is transmitted with an <span>XML
+ MIME type</span>, such as <code>application/xhtml+xml</code>, then
+ it is treated as an XML document by Web browsers, to be parsed by an
+ XML processor. Authors are reminded that the processing for XML and
+ HTML differs; in particular, even minor syntax errors will prevent
+ an XML document from being rendered fully, whereas they would be
+ ignored in the HTML syntax. This specification defines version 5 of
+ the XHTML syntax, known as "XHTML5".</p>
- <p>The "DOM5 HTML", "HTML5", and "XHTML5" representations cannot all
- represent the same content. For example, namespaces cannot be
- represented using "HTML5", but they are supported in "DOM5 HTML" and
- "XHTML5". Similarly, documents that use the <code>noscript</code>
- feature can be represented using "HTML5", but cannot be represented
- with "XHTML5" and "DOM5 HTML". Comments that contain the string
- "<code title="">--></code>" can be represented in "DOM5 HTML" but
- not in "HTML5" and "XHTML5". And so forth.</p>
+ <p>The DOM, the HTML syntax, and XML cannot all represent the same
+ content. For example, namespaces cannot be represented using the
+ HTML syntax, but they are supported in the DOM and in XML.
+ Similarly, documents that use the <code>noscript</code> feature can
+ be represented using the HTML syntax, but cannot be represented with
+ the DOM or in XML. Comments that contain the string "<code
+ title="">--></code>" can be represented in the DOM but not in the
+ HTML syntax or in XML.</p>
<h3>Structure of this specification</h3>
@@ -87882,16 +87882,11 @@
href="http://dev.w3.org/2006/webapi/XMLHttpRequest-2/"><code>XMLHttpRequest</code></a></cite>,
A. van Kesteren. W3C, June 2009.</dd>
- <dt id="refsXHTML10">[XHTML10]</dt>
+ <dt id="refsXHTML1">[XHTML1]</dt>
<dd><cite><a href="http://www.w3.org/TR/xhtml1/">XHTML(TM) 1.0 The
Extensible HyperText Markup Language (Second Edition)</a></cite>. W3C,
August 2002.</dd>
- <dt id="refsXHTML11">[XHTML11]</dt>
- <dd><cite><a href="http://www.w3.org/TR/xhtml11/">XHTML(TM) 1.1 -
- Module-based XHTML</a></cite>, M. Altheim, S. McCarron. W3C,
- May 2001.</dd>
-
<dt id="refsXHTMLMOD">[XHTMLMOD]</dt>
<dd><cite><a
href="http://www.w3.org/TR/xhtml-modularization">Modularization of
More information about the Commit-Watchers
mailing list