eliot: Edited Section 6.1, Required Elements, per bug 12322

eliot: Edited Section 6.1, Required Elements, per bug 12322

http://dev.w3.org/cvsweb/html5/html-xhtml-author-guide/html-xhtml-authoring-guide.html?r1=1.71&r2=1.72&f=h

===================================================================
RCS file: /sources/public/html5/html-xhtml-author-guide/html-xhtml-authoring-guide.html,v
retrieving revision 1.71
retrieving revision 1.72
diff -u -d -r1.71 -r1.72
--- html-xhtml-authoring-guide.html 18 Mar 2011 22:05:01 -0000 1.71
+++ html-xhtml-authoring-guide.html 18 Mar 2011 22:55:26 -0000 1.72
@@ -14,7 +14,7 @@
    <a href="http://www.w3.org/"><img height="48" width="72" alt="W3C" src="http://www.w3.org/Icons/w3c_home"/></a>
   </p>
   <h1 class="title" id="title">Polyglot Markup: HTML-Compatible XHTML Documents</h1>
-  <h2 id="w3c-editor-s-draft-18-march-2011">W3C Editor's Draft 17 March 2011</h2>
+  <h2 id="w3c-editor-s-draft-18-march-2011">W3C Editor's Draft 18 March 2011</h2>
   <dl>
    <dt>This version:</dt>
    <dd><a href="http://dev.w3.org/html5/html-xhtml-author-guide/html-xhtml-authoring-guide.html">http://dev.w3.org/html5/html-xhtml-author-guide/html-xhtml-authoring-guide.html</a></dd>
@@ -385,7 +385,7 @@
    Therefore, the following source code would be the most basic <a class="internalDFN" href="#dfn-polyglot-markup">polyglot markup</a> document.
   </p>
   <pre class="example">&lt;!DOCTYPE html&gt;
-&lt;html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"&gt;
+&lt;html xmlns="http://www.w3.org/1999/xhtml" lang="" xml:lang=""&gt;
   &lt;head&gt;
     &lt;title&gt;&lt;/title&gt;
   &lt;/head&gt;
@@ -393,8 +393,11 @@
   &lt;/body&gt;
 &lt;/html&gt;</pre>
   <p>
-   <a class="internalDFN" href="#dfn-polyglot-markup" title="polyglot markup">Polyglot markup</a> explicitly uses a <code>tbody</code> element surrounding groups of <code>tr</code> elements within a <code>table</code> element.
-   HTML parsers insert the <code>tbody</code> element, but XML parsers do not, thus creating different DOMs.
+   Whenever it uses a <code>tr</code> element, <a class="internalDFN" href="#dfn-polyglot-markup">polyglot markup</a> always wraps the <code>tr</code> element inside a 
+   <code>tbody</code>, <code>thead</code>, or <code>tfoot</code> element. 
+   In HTML, if a group of one or more adjacent <code>tr</code> elements are not explictly wrapped inside a <code>tbody</code>, <code>thead</code>, or <code>tfoot</code> element, 
+   the HTML parser creates and wraps a new <code>tbody</code> element around the <code>tr</code> elements. 
+   XML parsers do not crete the <code>tbody</code> element, thus offering the potential for creating different DOMs.
   </p>
   <p>
    Correct:
@@ -406,8 +409,10 @@
   <pre class="example">&lt;table&gt;
 &lt;tr&gt;...</pre>
   <p>
-   <a class="internalDFN" href="#dfn-polyglot-markup" title="polyglot markup">Polyglot markup</a> explicitly uses a <code>colgroup</code> element surrounding groups of <code>col</code> elements within a <code>table</code> element. 
-      HTML parsers insert the <code>colgroup</code> element, but XML parsers do not, thus creating different DOMs.
+   Whenever it uses <code>col</code> elements within a <code>table</code> element, <a class="internalDFN" href="#dfn-polyglot-markup">polyglot markup</a> explicitly uses a <code>colgroup</code> element surrounding groups of the <code>col</code> elements. 
+      In HTML, if a group of one or more adjacent <code>col</code> elements are not explicitly wrapped inside a <code>colgroup</code> element, 
+      the HTML parser creates and wraps a new <code>colgroup</code> element around the <code>col</code> elements. 
+      XML parsers do not create the <code>colgroup</code> element, thus offering the potential for creating different DOMs.
   </p>
   <p>
    Correct:
@@ -773,8 +778,11 @@
    then <a class="internalDFN" href="#dfn-polyglot-markup">polyglot markup</a> is required to specify the language mapping of the root element.
    According to <a href="http://dev.w3.org/html5/spec/semantics.html#attr-meta-http-equiv-content-language">Content language state</a> in [<cite><a href="#bib-HTML5" rel="biblioentry" class="bibref">HTML5</a></cite>], 
    the <code>http-equiv="content-language"</code> attribute on the <code>&lt;meta&gt;</code> element specifices the language of the root element 
-   whenever its <code>content</code> attribute contains no more and no less than exactly one language tag.
-   Therefore, not specifying the language mapping of the root element would mean that HTML5 would interpret this as setting the default language for the root element, while XML did not.
+   whenever its <code>content</code> attribute contains no more and no 
+less than exactly one language tag. 
+   Therefore, not specifying the language mapping of the root element 
+would mean that HTML5 would interpret this as setting the default 
+language for the root element, while XML did not.
   </p>
 
 <!--End section: Language Attributes-->

Received on Friday, 18 March 2011 22:56:44 UTC