W3C home > Mailing lists > Public > public-html-commits@w3.org > March 2011

html5/html-xhtml-author-guide html-xhtml-authoring-guide.html,1.60,1.61

From: Eliot Graff via cvs-syncmail <cvsmail@w3.org>
Date: Thu, 03 Mar 2011 21:24:07 +0000
To: public-html-commits@w3.org
Message-Id: <E1PvG0F-0000Te-Bo@lionel-hutz.w3.org>
Update of /sources/public/html5/html-xhtml-author-guide
In directory hutz:/tmp/cvs-serv1465

Modified Files:
	html-xhtml-authoring-guide.html 
Log Message:
Edited the Introduction to account for requests contained in bug 11909, further clarifying the definition of polyglot markup.

Index: html-xhtml-authoring-guide.html
===================================================================
RCS file: /sources/public/html5/html-xhtml-author-guide/html-xhtml-authoring-guide.html,v
retrieving revision 1.60
retrieving revision 1.61
diff -u -d -r1.60 -r1.61
--- html-xhtml-authoring-guide.html	3 Mar 2011 18:34:05 -0000	1.60
+++ html-xhtml-authoring-guide.html	3 Mar 2011 21:24:05 -0000	1.61
@@ -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-05-january-2011">W3C Editor's Draft 3 March 2011</h2>
+		<h2 id="w3c-editor-s-draft-05-january-2011">W3C Editor's Draft 2 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>
@@ -163,74 +163,68 @@
 
 
 <div id="introduction" class="section informative">
-<h2><span class="secno">1. </span>Introduction</h2>
-	<p>
-		<em>This section is non-normative.</em>
-	</p>
+<!--OddPage--><h2><span class="secno">1. </span>Introduction</h2><p><em>This section is non-normative.</em></p>
 	<p>
 		It is often valuable to be able to serve HTML5 documents that are also well formed XML documents. 
 		An author may, for example, use XML tools to generate a document, and they and others may process the document using XML tools. 
 		The language used to create documents that can be parsed by both HTML and XML parsers is called <dfn id="dfn-polyglot-markup">polyglot markup</dfn>.
-		<a class="internalDFN" href="#dfn-polyglot-markup" title="polyglot markup">Polyglot markup</a> is the overlap language of documents that are both HTML5 documents and XML documents. 
+		<a class="internalDFN" href="#dfn-polyglot-markup" title="polyglot markup">Polyglot markup</a> is 
+		the overlap language of documents that are both HTML5 documents and XML documents. 
 		It is recommended that these documents be served as either <code>text/html</code> (if the content is transmitted to an HTML-aware user agent) 
 		or <code>application/xhtml+xml</code> (if the content is transmitted to an XHTML-aware user agent).
 		Other permissible MIME types are <code>text/xml</code>, <code>application/xml</code>, 
 		and any MIME type whose subtype ends with the four characters "<code>+xml</code>". [<cite><a href="#bib-XML-MT" rel="biblioentry" class="bibref">XML-MT</a></cite>]
 	</p>
 	<p>
-		<a class="internalDFN" href="#dfn-polyglot-markup" title="polyglot markup">Polyglot markup</a>:
+		<a class="internalDFN" href="#dfn-polyglot-markup" title="polyglot markup">Polyglot markup</a> results in:
 	</p>
 	<ul>
-		<li>is valid HTML5. [<cite><a href="#bib-HTML5" rel="biblioentry" class="bibref">HTML5</a></cite>]</li>
-		<li>is <a href="http://www.w3.org/TR/2008/PER-xml-20080205/#sec-well-formed">well-formed XML</a>. [<cite><a href="#bib-XML10" rel="biblioentry" class="bibref">XML10</a></cite>]</li>
-		<li>results in identical DOMs (with the exception of the <code>xmlns</code> attribute on the root element) when processed as HTML and when processed as XML.</li>			
+		<li>a valid HTML document. [<cite><a href="#bib-HTML5" rel="biblioentry" class="bibref">HTML5</a></cite>]</li>
+		<li>
+			a <a href="http://www.w3.org/TR/2008/PER-xml-20080205/#sec-well-formed">well-formed XML</a> document. 
+			[<cite><a href="#bib-XML10" rel="biblioentry" class="bibref">XML10</a></cite>]
+		</li>
+		<li>
+			identical DOMs when processed as HTML and when processed as XML. 
+			A noteable exception to this is that HTML and XML parsers generate different DOMs for 
+			some <code>xml</code> (<code>xml:lang</code>, <code>xml:space</code>, and <code>xml:base</code>), 
+			<code>xmlns</code> (<code>xmlns=""</code> and <code>xmlns:xlink=""</code>), and <code>xlink</code> (such as <code>xlink:href</code>) attributes. 
+			XML requires and HTML5 permits these attributes in certain locations and the attributes are preserved by HTML parsers.
+		</li>			
 	</ul>
 	<p>
 		<a class="internalDFN" href="#dfn-polyglot-markup" title="polyglot markup">Polyglot markup</a> is not constrained: 
 	</p>
 	<ul>
-		<li>to be <a href="http://www.w3.org/TR/2008/PER-xml-20080205/#dt-valid">valid XML</a>. [<cite><a href="#bib-XML10" rel="biblioentry" class="bibref">XML10</a></cite>]</li>
+		<li>
+			to be <a href="http://www.w3.org/TR/2008/PER-xml-20080205/#dt-valid">valid XML</a>. 
+			[<cite><a href="#bib-XML10" rel="biblioentry" class="bibref">XML10</a></cite>]
+		</li>
 		<li>by conformance to any XML DTD.</li>
 	</ul>
 	<p>
+		<a class="internalDFN" href="#dfn-polyglot-markup" title="polyglot markup">Polyglot markup</a> is 
+		scripted according to the rules of XML (does not use <code>document.write</code>, for example) 
+		and excludes HTML elements that are impossible to replicate in an XML parser (does not use the <code>&lt;noscript&gt;</code> element, for example).
+		<a class="internalDFN" href="#dfn-polyglot-markup" title="polyglot markup">Polyglot markup</a> triggers non-quirks mode in HTML parsers, 
+		as non-quirks mode is closest to XML-mode rendering, in regard to both DOM and CSS.
+		<a class="internalDFN" href="#dfn-polyglot-markup" title="polyglot markup">Polyglot markup</a> results in 
+		the same encoding and the same language in both HTML-mode and XML-mode.
+	</p>
+	<p>
 		All web content need not be authored in <a class="internalDFN" href="#dfn-polyglot-markup">polyglot markup</a>.
-		<a class="internalDFN" href="#dfn-polyglot-markup" title="polyglot markup">Polyglot markup</a> is ideal for publishing when there's a strong desire to serve both HMTL and XML tool chains 
+		<a class="internalDFN" href="#dfn-polyglot-markup" title="polyglot markup">Polyglot markup</a> is ideal for publishing when 
+		there's a strong desire to serve both HTML and XML tool chains 
 		without simultaneously having to maintain dual copies of the content: one in HTML and a second in XHTML. 
-		In addition, a single <a class="internalDFN" href="#dfn-polyglot-markup">polyglot markup</a> output requires less infrastructure to produce than to produce both HTML and XHTML output for the same content. 
-		<a class="internalDFN" href="#dfn-polyglot-markup" title="polyglot markup">Polyglot markup</a> is also be beneficial when lightweight processes—such as 
-		quick testing or even hand-authoring—are applied to content intended to be published both as HTML and XHTML, 
+		In addition, a single <a class="internalDFN" href="#dfn-polyglot-markup">polyglot markup</a> output requires 
+		less infrastructure to produce than to produce both HTML and XHTML output for the same content. 
+		<a class="internalDFN" href="#dfn-polyglot-markup" title="polyglot markup">Polyglot markup</a> is also be beneficial when lightweight processes&#x2014;such as 
+		quick testing or even hand-authoring&#x2014;are applied to content intended to be published both as HTML and XHTML, 
 		especially if that content is not sent through a tool chain. 
 	</p>
 <!--End section: Introduction-->
 </div>
 
-
-
-	<div id="introduction" class="section informative">
-		<h2><span class="secno">1. </span>Introduction</h2>
-		<p>
-			<em>This section is non-normative.</em>
-		</p>
-		<p>
-			It is often valuable to be able to serve HTML5 documents that are also well formed XML documents. 
-			An author may, for example, use XML tools to generate a document, and they and others may process the document using XML tools. 
-			These documents are served as text/html. 
-			The language used to create documents that can be parsed by both HTML and XML parsers is called <dfn id="dfn-polyglot-markup">polyglot markup</dfn>. 
-			<a class="internalDFN" href="#dfn-polyglot-markup" title="polyglot markup">Polyglot markup</a> is the overlap language of documents which are both HTML5 documents and XML documents. 
-		</p>
-		<p>
-			All web content need not be authored in <a>polyglot markup</a>.
-			<a title="polyglot markup">Polyglot markup</a> is ideal for publishing when there's a strong desire to serve both HMTL and XML tool chains 
-			without simultaneously having to maintain dual copies of the content: one in HTML and a second in XHTML. 
-			In addition, a single <a>polyglot markup</a> output requires less infrastructure to produce than to produce both HTML and XHTML output for the same content. 
-			<a title="polyglot markup">Polyglot markup</a> is also be beneficial when lightweight processes&#x2014;such as 
-			quick testing or even hand-authoring&#x2014;are applied to content intended to be published both as HTML and XHTML, 
-			especially if that content is not sent through a tool chain. 
-		</p>
-<!--End Section 1: Introduction-->
-	</div>
-
-
 <div id="PI-and-xml" class="section">
 <!--OddPage--><h2><span class="secno">2. </span>Processing Instructions and the XML Declaration</h2>
 <p>
@@ -1004,6 +998,7 @@
 
 
 
+
 <!-- Appendix -->
 <div id="acknowledgements" class="appendix section">
 <h2><span class="secno">A. </span>Acknowledgements</h2>
Received on Thursday, 3 March 2011 21:24:09 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 3 March 2011 21:24:10 GMT