html5/spec Overview.html,1.2882,1.2883

Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv15522

Modified Files:
	Overview.html 
Log Message:
Revamp how we refer to XHTML, the HTML syntax, and DOM5 HTML in the intro, hopefully to confuse readers less. (whatwg r3704)

Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.2882
retrieving revision 1.2883
diff -u -d -r1.2882 -r1.2883
--- Overview.html	30 Aug 2009 00:01:50 -0000	1.2882
+++ Overview.html	30 Aug 2009 00:29:10 -0000	1.2883
@@ -301,7 +301,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>
@@ -1261,40 +1261,39 @@
   implementations to continue supporting legacy content.  <a href="#refsHTML4">[HTML4]</a> <a href="#refsDOM2HTML">[DOM2HTML]</a><p>A separate document has been published by the W3C HTML working
   group to provide a more detailed reference of the differences
   between this specification and the language described in the HTML4
-  specification. <a href="#refsHTMLDIFF">[HTMLDIFF]</a><h4 id="relationship-to-xhtml-1.x"><span class="secno">1.6.2 </span>Relationship to XHTML 1.x</h4><p class="XXX annotation"><b>Status: </b><i>Working draft</i><p><i>This section is non-normative.</i><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>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>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.<h3 id="html-vs-xhtml"><span class="secno">1.7 </span>HTML vs XHTML</h3><p class="XXX annotation"><b>Status: </b><i>Controversial Working Draft</i><p><i>This section is non-normative.</i><p>This specification defines an abstract language for describing
+  specification. <a href="#refsHTMLDIFF">[HTMLDIFF]</a><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>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>While this specification updates the semantics and requirements
+  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>Thus, authors and implementors who need such a modularization
+  scheme are encouraged to continue using the XHTML Modularization
+  line of specifications.<h3 id="html-vs-xhtml"><span class="secno">1.7 </span>HTML vs XHTML</h3><p class="XXX annotation"><b>Status: </b><i>Controversial Working Draft</i><p><i>This section is non-normative.</i><p>This specification defines an abstract language for describing
   documents and applications, and some APIs for interacting with
-  in-memory representations of resources that use this language.<p>The in-memory representation is known as "DOM5 HTML", or "the
-  DOM" for short.<p>There are various concrete syntaxes that can be used to transmit
+  in-memory representations of resources that use this language.<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>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>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>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>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="">--&gt;</code>" can be represented in "DOM5 HTML" but
-  not in "HTML5" and "XHTML5". And so forth.<h3 id="structure-of-this-specification"><span class="secno">1.8 </span>Structure of this specification</h3><p><i>This section is non-normative.</i><p>This specification is divided into the following major
+  in this specification.<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>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>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="">--&gt;</code>" can be represented in the DOM but not in the
+  HTML syntax or in XML.<h3 id="structure-of-this-specification"><span class="secno">1.8 </span>Structure of this specification</h3><p><i>This section is non-normative.</i><p>This specification is divided into the following major
   sections:<dl><dt><a href="#infrastructure">Common Infrastructure</a></dt>
 
    <dd>The conformance classes, algorithms, definitions, and the
@@ -7915,7 +7914,7 @@
    <p>To avoid this confusion, explicit <code><a href="#the-p-element">p</a></code> elements can be
    used.</p>
 
-  </div><h4 id="annotations-for-assistive-technology-products"><span class="secno">3.2.6 </span><dfn>Annotations for assistive technology products</dfn></h4><p class="XXX annotation"><b>Status: </b><i>First draft. </i><span><a href="http://www.w3.org/html/wg/tracker/issues/14">ISSUE-14</a> (aria-role) and <a href="http://www.w3.org/html/wg/tracker/issues/35">ISSUE-35</a> (aria-processing) block progress to Last Call</span><p>Authors may use the ARIA <code title="attr-aria-role">role</code>
+  </div><h4 id="annotations-for-assistive-technology-products"><span class="secno">3.2.6 </span><dfn>Annotations for assistive technology products</dfn></h4><p class="XXX annotation"><b>Status: </b><i>First draft. </i><span><a href="http://www.w3.org/html/wg/tracker/issues/35">ISSUE-35</a> (aria-processing) and <a href="http://www.w3.org/html/wg/tracker/issues/14">ISSUE-14</a> (aria-role) block progress to Last Call</span><p>Authors may use the ARIA <code title="attr-aria-role">role</code>
   and <code title="attr-aria-*">aria-*</code> attributes on <a href="#html-elements">HTML
   elements</a>, in accordance with the requirements described in
   the ARIA specifications, except where these conflict with the
@@ -17603,7 +17602,7 @@
   <a href="#reflect">reflect</a> the respective content attributes of the same
   name.</p>
 
-  </div><h4 id="video"><span class="secno">4.8.7 </span>The <dfn><code>video</code></dfn> element</h4><p class="XXX annotation"><b>Status: </b><i>Last call for comments. </i><span><a href="http://www.w3.org/html/wg/tracker/issues/7">ISSUE-7</a> (video-codecs), <a href="http://www.w3.org/html/wg/tracker/issues/9">ISSUE-9</a> (video-synchronization) and <a href="http://www.w3.org/html/wg/tracker/issues/10">ISSUE-10</a> (video-smil) block progress to Last Call</span><dl class="element"><dt>Categories</dt>
+  </div><h4 id="video"><span class="secno">4.8.7 </span>The <dfn><code>video</code></dfn> element</h4><p class="XXX annotation"><b>Status: </b><i>Last call for comments. </i><span><a href="http://www.w3.org/html/wg/tracker/issues/9">ISSUE-9</a> (video-synchronization), <a href="http://www.w3.org/html/wg/tracker/issues/7">ISSUE-7</a> (video-codecs) and <a href="http://www.w3.org/html/wg/tracker/issues/10">ISSUE-10</a> (video-smil) block progress to Last Call</span><dl class="element"><dt>Categories</dt>
    <dd><a href="#flow-content">Flow content</a>.</dd>
    <dd><a href="#phrasing-content">Phrasing content</a>.</dd>
    <dd><a href="#embedded-content">Embedded content</a>.</dd>
@@ -67711,16 +67710,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.

Received on Sunday, 30 August 2009 00:29:22 UTC