- From: Eliot Graff via cvs-syncmail <cvsmail@w3.org>
- Date: Mon, 06 Dec 2010 20:40:39 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/html-xhtml-author-guide
In directory hutz:/tmp/cvs-serv25256
Modified Files:
html-xhtml-authoring-guide.html
Log Message:
Added "Section 11. Example Document" per Bug 10961; Made language consistent, removing all unnecessary RFC 2119 keywords;
Index: html-xhtml-authoring-guide.html
===================================================================
RCS file: /sources/public/html5/html-xhtml-author-guide/html-xhtml-authoring-guide.html,v
retrieving revision 1.43
retrieving revision 1.44
diff -u -d -r1.43 -r1.44
--- html-xhtml-authoring-guide.html 29 Oct 2010 20:34:44 -0000 1.43
+++ html-xhtml-authoring-guide.html 6 Dec 2010 20:40:37 -0000 1.44
@@ -1,25 +1,9 @@
<!DOCTYPE html>
-<html dir="ltr" lang="en"><head>
-
-
-
-
- <title>Polyglot Markup: HTML-Compatible XHTML Documents</title>
-
- <!--
-
- === NOTA BENE ===
-
- For the three scripts below, if your spec resides on dev.w3 you can check them
-
- out in the same tree and use relative links so that they'll work offline,
- -->
-
-
-
+<html dir="ltr" lang="en"><head>
+<title>Polyglot Markup: HTML-Compatible XHTML Documents</title>
- <meta name="GENERATOR" content="MSHTML 8.00.7600.16588"/>
+<meta name="GENERATOR" content="MSHTML 8.00.7600.16588"/>
<style type="text/css">
/*****************************************************************
* ReSpec CSS
@@ -488,17 +472,18 @@
<link type="text/css" rel="stylesheet" href="html-xhtml-authoring-guide_files/W3C-ED.css"/>
<link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/W3C-ED"/>
-</head>
-<body style="display: inherit;">
-<div class="head">
+</head>
+ <body style="display: inherit;">
+ <div class="head">
<p>
<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-30-october-2010">W3C Editor's Draft 30 October 2010</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><dt>Latest published version:</dt><dd><a href="http://www.w3.org/TR/html-polyglot/">http://www.w3.org/TR/html-polyglot/</a></dd><dt>Latest editor's draft:</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><dt>Previous version:</dt><dd><a href="http://www.w3.org/TR/2010/WD-html-polyglot-20100624/">http://www.w3.org/TR/2010/WD-html-polyglot-20100624/</a></dd><dt>Editor:</dt><dd><span>Eliot Graff</span>, Microsoft Corporation</dd>
+
+ <h1 class="title" id="title">Polyglot Markup: HTML-Compatible XHTML Documents</h1><h2 id="w3c-editor-s-draft-06-december-2010">W3C Editor's Draft 06 December 2010</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><dt>Latest published version:</dt><dd><a href="http://www.w3.org/TR/html-polyglot/">http://www.w3.org/TR/html-polyglot/</a></dd><dt>Latest editor's draft:</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><dt>Previous version:</dt><dd><a href="http://www.w3.org/TR/2010/WD-html-polyglot-20101019/">http://www.w3.org/TR/2010/WD-html-polyglot-20101019/</a></dd><dt>Editor:</dt><dd><span>Eliot Graff</span>, Microsoft Corporation</dd>
</dl>
+
<p class="copyright">
<a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 2010
<a href="http://www.w3.org/"><abbr title="World Wide Web Consortium">W3C</abbr></a><sup>®</sup>
@@ -508,8 +493,9 @@
<a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and
<a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.
</p>
- <hr/>
+
</div>
+<hr/>
<div class="introductory section" id="abstract"><h2>Abstract</h2>
A document that uses polyglot markup is document that is a stream of
@@ -521,7 +507,7 @@
HTML or as XHTML,
per the HTML5 specification.
Polyglot markup uses a specific DOCTYPE, namespace declarations, and a
-specific case—normally lower case but occasionally camel case—for
+specific case—normally lower case but occasionally camel case—for
element and attribute names.
Polyglot markup uses lower case for certain attribute values.
Further constraints include those on empty elements, named entity
@@ -555,17 +541,22 @@
<a href="http://lists.w3.org/Archives/Public/public-html/">archives</a>) and arrangements will be made to transpose the comments to the bug database.
All feedback is welcome.</p>
<!--End of Status of This Document-->
-<p>Publication as an Editor's Draft does not imply endorsement by the W3C Membership.
+<p>Publication
+ as a Editor's Draft does not imply endorsement by the W3C Membership.
This is a draft document and may be updated, replaced or obsoleted by
other documents at any time. It is inappropriate to cite this document
as other than work in progress.</p>
-<p>This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February 2004 W3C Patent Policy</a>. W3C maintains a <a href="http://www.w3.org/2004/01/pp-impl/40318/status" rel="disclosure">public list of any patent disclosures</a>
- made in connection with the deliverables of the group; that page also
-includes instructions for disclosing a patent. An individual who has
-actual knowledge of a patent which the individual believes contains <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential Claim(s)</a> must disclose the information in accordance with <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section 6 of the W3C Patent Policy</a>.</p></div>
+<p>
+ This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February 2004 W3C Patent Policy</a>.
+ W3C maintains a <a href="http://www.w3.org/2004/01/pp-impl/40318/status" rel="disclosure">public list of any patent disclosures</a>
+ made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has
+ actual knowledge of a patent which the individual believes contains <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential Claim(s)</a>
+ must disclose the information in accordance with <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section 6 of the W3C Patent Policy</a>.
+</p>
+</div>
-<div class="section" id="toc"><h2 class="introductory">Table of Contents</h2>
+<h2 class="introductory">Table of Contents</h2>
<ul class="toc">
<li class="tocline"><a class="tocxref" href="#introduction"><span class="secno">1. </span>Introduction</a></li>
<li class="tocline"><a class="tocxref" href="#PI-and-xml"><span class="secno">2. </span>Processing Instructions and the XML Declaration</a></li>
@@ -622,6 +613,7 @@
</ul>
</li>
<li class="tocline"><a class="tocxref" href="#foreign-content"><span class="secno">10. </span>Exceptions from the Foreign Content Parsing Rules</a></li>
+ <li class="tocline"><a class="tocxref" href="#example-document"><span class="secno">11. </span>Example Document</a></li>
<li class="tocline"><a class="tocxref" href="#acknowledgements"><span class="secno">A. </span>Acknowledgements</a></li>
<li class="tocline"><a class="tocxref" href="#references"><span class="secno">B. </span>References</a>
<ul class="toc">
@@ -644,7 +636,7 @@
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>.
- Polyglot markup is the overlap language of documents which 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 which are both HTML5 documents and XML documents.
</p>
<!--End Section 1: Introduction-->
</div>
@@ -652,7 +644,7 @@
<div id="PI-and-xml" class="section">
<!--OddPage--><h2><span class="secno">2. </span>Processing Instructions and the XML Declaration</h2>
<p>
- Processing Instructions and the XML Declaration are both forbidden in polyglot markup.
+ Processing Instructions and the XML Declaration are both forbidden in <a class="internalDFN" href="#dfn-polyglot-markup">polyglot markup</a>.
</p>
<!--End section: Processing Instructions and the XML Declaration-->
</div>
@@ -661,13 +653,13 @@
<div id="character-encoding" class="section">
<!--OddPage--><h2><span class="secno">3. </span>Specifying a Document's Character Encoding</h2>
<p>
- Polyglot markup uses either UTF-8 or UTF-16. UTF-8 is preferred.
- When polyglot markup uses UTF-8, it <em title="must not" class="rfc2119">must not</em> include a BOM.
- When polyglot markup uses UTF-16, it <em title="must" class="rfc2119">must</em> include the BOM indicating
+ <a class="internalDFN" href="#dfn-polyglot-markup" title="polyglot markup">Polyglot markup</a> uses either UTF-8 or UTF-16. UTF-8 is preferred.
+ When <a class="internalDFN" href="#dfn-polyglot-markup">polyglot markup</a> uses UTF-8, it does not include a BOM.
+ When <a class="internalDFN" href="#dfn-polyglot-markup">polyglot markup</a> uses UTF-16, it includes the BOM indicating
little-endian UTF-16 or big-endian UTF-16.
</p>
<p>
- Polyglot markup declares character encoding one of two ways:
+ <a class="internalDFN" href="#dfn-polyglot-markup" title="polyglot markup">Polyglot markup</a> declares character encoding one of two ways:
</p><ul>
<li>By using the BOM.</li>
<li>In the HTTP header of the response [<cite><a href="#bib-HTTP11" rel="biblioentry" class="bibref">HTTP11</a></cite>], as in the following:
@@ -678,13 +670,14 @@
<br>
<code>Content-type: text/html; charset=utf-16</code>
</p>
- Note that polyglot markup may use either <code>text/html</code> or <code>application/xhtml+xml</code> for the value of the content type.
+ Note that <a class="internalDFN" href="#dfn-polyglot-markup">polyglot markup</a> may use either <code>text/html</code> or <code>application/xhtml+xml</code> for the value of the content type.
</li>
</ul>
<p></p>
<p>
Using <code><meta charset="*"/></code> has no effect in XML.
- Therefore, polyglot markup <em title="may" class="rfc2119">may</em> use <code><meta charset="*"/></code> provided the document is encoded as UTF-8 and the value of charset is a case-insensitive match for the string “utf-8”.
+ Therefore, <a class="internalDFN" href="#dfn-polyglot-markup">polyglot markup</a> may use <code><meta charset="*"/></code> provided the document is encoded as UTF-8
+ and the value of charset is a case-insensitive match for the string "utf-8".
</p>
<p>
Note that the <a href="http://www.w3.org/International/questions/qa-html-encoding-declarations">W3C Internationalization (i18n) Group recommends</a>
@@ -698,8 +691,8 @@
<div id="doctype" class="section">
<!--OddPage--><h2><span class="secno">4. </span>The DOCTYPE</h2>
<p>
- Polyglot markup <em title="must" class="rfc2119">must</em> have a document type declaration (DOCTYPE) specified by <a href="http://www.w3.org/TR/html5/syntax.html#the-doctype">section 8.1.1</a> of [<cite><a href="#bib-HTML5" rel="biblioentry" class="bibref">HTML5</a></cite>].
- In addition, the DOCTYPE <em title="must" class="rfc2119">must</em> conform to the following rules:
+ <a class="internalDFN" href="#dfn-polyglot-markup" title="polyglot markup">Polyglot markup</a> uses a document type declaration (DOCTYPE) specified by <a href="http://www.w3.org/TR/html5/syntax.html#the-doctype">section 8.1.1</a> of [<cite><a href="#bib-HTML5" rel="biblioentry" class="bibref">HTML5</a></cite>].
+ In addition, the DOCTYPE conforms to the following rules:
</p>
<ul>
<li>The string <code>DOCTYPE</code> is in uppercase letters.</li>
@@ -709,16 +702,14 @@
<li>A Formal Public Identifier (FPI), if present, is a case-sensitive match of the registered FPI to which it points.</li>
<li>A URI, if present in the document type declaration, is a case-sensitive match of the URI to which it points.
<ul>
- <li>If the URI is the string <code>about:legacy-compat</code>, the string <em title="must" class="rfc2119">must</em> be in lowercase, as required by HTML5.</li>
- <li>If the URI is an http URL, the URI must point to the correct resource, using case-sensitive letters.</li>
+ <li>If the URI is the string <code>about:legacy-compat</code>, <a class="internalDFN" href="#dfn-polyglot-markup">polyglot markup</a> includes the string in lowercase letters, as required by HTML5.</li>
+ <li>If the URI is an http URL, the URI points to the correct resource, using case-sensitive letters.</li>
</ul>
</li>
</ul>
<p>
- Note that polyglot markup cannot use document type declarations for
-HTML4, HTML3, or HTML2, regardless of whether they contain a URI or not
-and regardless of their effect in HTML5 parsers, as these document type
-declarations are not compatible with XHTML.
+ Note that <a class="internalDFN" href="#dfn-polyglot-markup">polyglot markup</a> does not use document type declarations for HTML4, HTML3, or HTML2, regardless of whether they contain a URI or not and
+ regardless of their effect in HTML5 parsers, as these document type declarations are not compatible with XHTML.
</p>
<!--End section: The DOCTYPE-->
</div>
@@ -727,14 +718,17 @@
<div id="namespaces" class="section">
<!--OddPage--><h2><span class="secno">5. </span>Namespaces</h2>
<p>
- The following rules apply to namespaces used in polyglot markup.
+ The following rules apply to namespaces used in <a class="internalDFN" href="#dfn-polyglot-markup">polyglot markup</a>.
</p>
<div id="element-level-namespaces" class="section">
<h3><span class="secno">5.1 </span>Element-Level Namespaces</h3>
<p>
- [<cite><a href="#bib-HTML5" rel="biblioentry" class="bibref">HTML5</a></cite>] introduces undeclared (native) default namespaces for the root HTML element <code><html></code>, the root SVG element <code><svg></code>, and the root MathML element <code><math></code>.
- The following default namespaces <em title="must" class="rfc2119">must</em> be declared in polyglot markup, to maintain XML-compatibility [<cite><a href="#bib-XML10" rel="biblioentry" class="bibref">XML10</a></cite>]:
+ [<cite><a href="#bib-HTML5" rel="biblioentry" class="bibref">HTML5</a></cite>] introduces undeclared (native) default namespaces for the root HTML element <code><html></code>, the root SVG element <code><svg></code>,
+ and the root MathML element <code><math></code>.
+ <a class="internalDFN" href="#dfn-polyglot-markup" title="polyglot markup">Polyglot markup</a>
+ declares the following default namespaces, when the markup languages
+are included in the document, to maintain XML-compatibility [<cite><a href="#bib-XML10" rel="biblioentry" class="bibref">XML10</a></cite>]:
</p><ul>
<li><code><html xmlns="http://www.w3.org/1999/xhtml"></code></li>
<li><code><math xmlns="http://www.w3.org/1998/Math/MathML"></code></li>
@@ -742,7 +736,8 @@
</ul>
<p></p>
<p>
- Polyglot markup <em title="must not" class="rfc2119">must not</em> declare any other default or prefixed element namespace, because [<cite><a href="#bib-HTML5" rel="biblioentry" class="bibref">HTML5</a></cite>] does not natively support the declaring of any other default or prefixed element namespace.
+ <a class="internalDFN" href="#dfn-polyglot-markup" title="polyglot markup">Polyglot markup</a> does not declare any other default or prefixed element namespace, because
+ [<cite><a href="#bib-HTML5" rel="biblioentry" class="bibref">HTML5</a></cite>] does not natively support the declaring of any other default or prefixed element namespace.
</p>
<!-- End section, "Element-Level Namespaces" -->
</div>
@@ -751,9 +746,10 @@
<h3><span class="secno">5.2 </span>Attribute-Level Namespaces</h3>
<p>
[<cite><a href="#bib-HTML5" rel="biblioentry" class="bibref">HTML5</a></cite>] introduces undeclared (native) support for attributes in the XLink namespace and with the prefix <code>xlink:</code>.
- Polyglot markup <em title="must" class="rfc2119">must</em> declare the XLink namespace on the HTML root element (<code><html></code>) or once on the foreign element where is used (<code><svg></code> or <code><mathml></code>), to maintain XML-compatibility [<cite><a href="#bib-XML10" rel="biblioentry" class="bibref">XML10</a></cite>].
+ <a class="internalDFN" href="#dfn-polyglot-markup" title="polyglot markup">Polyglot markup</a> declares the XLink namespace on the HTML root element (<code><html></code>) or
+ once on the foreign element where it is used (<code><svg></code> or <code><mathml></code>), to maintain XML-compatibility [<cite><a href="#bib-XML10" rel="biblioentry" class="bibref">XML10</a></cite>].
</p>
- <p>In polyglot markup, the xlink prefix uses the namespace declaration <code>xmlns:xlink="http://www.w3.org/1999/xlink"</code> before using the xlink prefix for the following attributes:
+ <p>In <a class="internalDFN" href="#dfn-polyglot-markup">polyglot markup</a>, the xlink prefix uses the namespace declaration <code>xmlns:xlink="http://www.w3.org/1999/xlink"</code> before using the xlink prefix for the following attributes:
</p><ul>
<li><code>xlink:actuate</code></li>
<li><code>xlink:arcrole</code></li>
@@ -763,11 +759,11 @@
<li><code>xlink:title</code></li>
<li><code>xlink:type</code></li>
</ul>
- Furthermore, polyglot markup defines the xlink prefix only on foreign elements (any SVG or MathML element) but not the root <code><html></code> element or any other HTML element.
+ Furthermore, <a class="internalDFN" href="#dfn-polyglot-markup">polyglot markup</a> defines the xlink prefix only on foreign elements (any SVG or MathML element) but not the root <code><html></code> element or any other HTML element.
<p></p>
<p>
Note that there are other prefixed attributes that can be used beyond <code>xlink:href</code> (such as <code>xml:base</code>).
- Polyglot markup does not declare these prefixes via xmlns. The prefixes are implicitly declared in XML and are automatically
+ <a class="internalDFN" href="#dfn-polyglot-markup" title="polyglot markup">Polyglot markup</a> does not declare these prefixes via xmlns. The prefixes are implicitly declared in XML and are automatically
applied to the appropriate attributes in HTML.
</p>
<!-- End section, "Attribute-Level Namespaces" -->
@@ -777,12 +773,12 @@
<div id="elements" class="section">
<!--OddPage--><h2><span class="secno">6. </span>Elements</h2>
-<p>Polyglot markup conforms to the following rules regarding elements.</p>
+<p><a class="internalDFN" href="#dfn-polyglot-markup" title="polyglot markup">Polyglot markup</a> conforms to the following rules regarding elements.</p>
<div id="required-elements" class="section">
<h3><span class="secno">6.1 </span>Required Elements</h3>
<p>
- Polyglot markup <em title="must" class="rfc2119">must</em> explicitly have a <code>tbody</code> element surrounding groups of <code>tr</code> elements within a <code>table</code> element.
+ <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.
</p>
<p>
@@ -795,7 +791,7 @@
<pre class="example"><table>
<tr>...</pre>
<p>
- Polyglot markup <em title="must" class="rfc2119">must</em> explicitly have a <code>colgroup</code> element surrounding groups of <code>col</code> elements within a <code>table</code> element.
+ <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.
</p>
<p>
@@ -813,8 +809,8 @@
<div id="elements-that-cannot-be-used" class="section">
<h3><span class="secno">6.2 </span>Elements that Cannot Be Used in Polyglot Markup</h3>
<p>
- Polyglot markup does not use the <code><noscript></code> element, because
- the <code><noscript></code> element must not be used in XML documents. [<cite><a href="#bib-HTML5" rel="biblioentry" class="bibref">HTML5</a></cite>]
+ <a class="internalDFN" href="#dfn-polyglot-markup" title="polyglot markup">Polyglot markup</a> does not use the <code><noscript></code> element, because
+ the <code><noscript></code> element cannot be used in XML documents. [<cite><a href="#bib-HTML5" rel="biblioentry" class="bibref">HTML5</a></cite>]
</p>
<!--End section: Elements that Cannot Be Used in Polyglot Markup-->
</div>
@@ -823,21 +819,20 @@
<div id="case-sensitivity" class="section">
<h3><span class="secno">6.3 </span>Case-Sensitivity</h3>
<p>
- The following guidelines apply to any usage of element names,
-attribute names, or attribute values in markup, script, or CSS.
- Polyglot markup uses lower case letters for all ASCII letters.
- For non-ASCII letters—such as Greek, Cyrillic, or non-ASCII Latin
-letters—polyglot markup respects case sensitivity as it is called for.
+ The following guidelines apply to any usage of element names, attribute names, or attribute values in markup, script, or CSS.
+ <a class="internalDFN" href="#dfn-polyglot-markup" title="polyglot markup">Polyglot markup</a> uses lower case letters for all ASCII letters.
+ For non-ASCII letters—such as Greek, Cyrillic, or non-ASCII Latin letters—<a class="internalDFN" href="#dfn-polyglot-markup">polyglot markup</a> respects case sensitivity as it is called for.
</p>
<div id="element-names" class="section">
<h4><span class="secno">6.3.1 </span>Element Names</h4>
- <p>Polyglot markup uses the correct case for element names.</p>
+ <p><a class="internalDFN" href="#dfn-polyglot-markup" title="polyglot markup">Polyglot markup</a> uses the correct case for element names.</p>
<ul>
- <li>Polyglot markup uses lowercase letters for all HTML element names.</li>
- <li>Polyglot markup uses lowercase letters for all MathML element names.</li>
- <li>Polyglot markup uses lowercase letters for all SVG element names except the following, which <em title="must" class="rfc2119">must</em> be in mixed case:
+ <li><a class="internalDFN" href="#dfn-polyglot-markup" title="polyglot markup">Polyglot markup</a> uses lowercase letters for all HTML element names.</li>
+ <li><a class="internalDFN" href="#dfn-polyglot-markup" title="polyglot markup">Polyglot markup</a> uses lowercase letters for all MathML element names.</li>
+ <li><a class="internalDFN" href="#dfn-polyglot-markup" title="polyglot markup">Polyglot markup</a> uses lowercase letters for all SVG element names except the following,
+ for which <a class="internalDFN" href="#dfn-polyglot-markup">polyglot markup</a> uses mixed case:
<ul>
<li><code>altGlyph</code></li>
<li><code>altGlyphDef</code></li>
@@ -884,12 +879,13 @@
<div id="attribute-names" class="section">
<h4><span class="secno">6.3.2 </span>Attribute Names</h4>
- <p>Polyglot markup uses the correct case for attribute names.</p>
+ <p><a class="internalDFN" href="#dfn-polyglot-markup" title="polyglot markup">Polyglot markup</a> uses the correct case for attribute names.</p>
<ul>
- <li>Polyglot markup uses lowercase letters in attribute names for all HTML elements.</li>
- <li>Polyglot markup uses lowercase letters in attribute names for all MathML elements except the lowercase <code>definitionurl</code>
- <em title="must" class="rfc2119">must</em> be changed to the mixed case <code>definitionURL</code>.</li>
- <li>Polyglot markup uses lowercase letters in attribute names for all SVG elements except the following, which <em title="must" class="rfc2119">must</em> be in mixed case:
+ <li><a class="internalDFN" href="#dfn-polyglot-markup" title="polyglot markup">Polyglot markup</a> uses lowercase letters in attribute names for all HTML elements.</li>
+ <li><a class="internalDFN" href="#dfn-polyglot-markup" title="polyglot markup">Polyglot markup</a> uses lowercase letters in attribute names for all MathML elements except the lowercase <code>definitionurl</code>,
+ which <a class="internalDFN" href="#dfn-polyglot-markup">polyglot markup</a> changes to the mixed case <code>definitionURL</code>.</li>
+ <li><a class="internalDFN" href="#dfn-polyglot-markup" title="polyglot markup">Polyglot markup</a> uses lowercase letters in attribute names for all SVG elements except the following,
+ for which <a class="internalDFN" href="#dfn-polyglot-markup">polyglot markup</a> uses mixed case:
<ul>
<li><code>attributeName</code></li>
<li><code>attributeType</code></li>
@@ -962,18 +958,17 @@
<div id="attribute-values" class="section">
<h4><span class="secno">6.3.3 </span>Attribute Values</h4>
<p>
- Polyglot markup requires the case used for characters in the values
-of the following attributes to be consistent between markup, DOM APIs,
-and CSS
+ <a class="internalDFN" href="#dfn-polyglot-markup" title="polyglot markup">Polyglot markup</a>
+ requires the case used for characters in the values of the following
+attributes to be consistent between markup, DOM APIs, and CSS
when these attributes are used on HTML elements.
This is because XML is case sensitive, but the values of these
attributes are treated as case insensitive in HTML when matched via CSS
selectors
- (See <a href="http://dev.w3.org/html5/spec/links.html#selectors">4.14.1 Case-sensitivity</a>, in the HTML5 specification). [<cite><a href="#bib-HTML5" rel="biblioentry" class="bibref">HTML5</a></cite>]
-
- In addition, polyglot markup respects the case sensitivity of all
-other attribute values and for non-ASCII characters in the values of the
- attributes listed.
+ (See <a href="http://dev.w3.org/html5/spec/links.html#selectors">4.14.1 Case-sensitivity</a>, in the HTML5 specification). [<cite><a href="#bib-HTML5" rel="biblioentry" class="bibref">HTML5</a></cite>]
+ In addition, <a class="internalDFN" href="#dfn-polyglot-markup">polyglot markup</a>
+ respects the case sensitivity of all other attribute values and for
+non-ASCII characters in the values of the attributes listed.
Note that other specifications, such as RDFa, may place additional
restrictions on the allowed values of certain attributes.
</p>
@@ -1032,7 +1027,7 @@
<div id="empty-elements" class="section">
<h3><span class="secno">6.4 </span>Empty Elements</h3>
- <p>Polyglot markup uses only the elements in the following list as empty elements.</p>
+ <p><a class="internalDFN" href="#dfn-polyglot-markup" title="polyglot markup">Polyglot markup</a> uses only the elements in the following list as empty elements.</p>
<ul>
<li><code>area</code></li>
<li><code>base</code></li>
@@ -1049,33 +1044,31 @@
<li><code>param</code></li>
<li><code>source</code></li>
</ul>
- <p>Polyglot markup uses the minimized tag syntax for empty elements, e.g. <code><br/></code>.
+ <p><a class="internalDFN" href="#dfn-polyglot-markup" title="polyglot markup">Polyglot markup</a> uses the minimized tag syntax for empty elements, e.g. <code><br/></code>.
The alternative syntax <code><br></br></code> allowed by XML gives uncertain results in many existing user agents.
</p>
<p>
Given an empty instance of an element whose content model is not EMPTY (for example, an empty title or paragraph)
- polyglot markup does not use the minimized form (e.g. the document uses <code><p></p></code> and not <code><p /></code>).
+ <a class="internalDFN" href="#dfn-polyglot-markup">polyglot markup</a> does not use the minimized form (e.g. the document uses <code><p></p></code> and not <code><p /></code>).
</p>
<p>Note that MathML and SVG elements may be either self-closing or contain content.</p>
<!--End section: Empty Elements-->
</div>
- <div id="elements-with-soecial-considerations" class="section">
+ <div id="elements-with-special-considerations" class="section">
<h3><span class="secno">6.5 </span>Elements with Special Considerations</h3>
- <p>The following elements or their considerations require exceptions to the general rules for polyglot markup.</p>
+ <p>The following elements or their considerations require exceptions to the general rules for <a class="internalDFN" href="#dfn-polyglot-markup">polyglot markup</a>.</p>
<div id="white-space-in-textarea-and-pre" class="section">
<h4><span class="secno">6.5.1 </span>White Space in <code><textarea></code> and <code><pre></code> Elements</h4>
- Within polyglot markup, the text within either a <code><textarea></code> or <code><pre></code> element <em title="must not" class="rfc2119">must not</em> begin with white space.
+ When <a class="internalDFN" href="#dfn-polyglot-markup">polyglot markup</a> uses either a <code><textarea></code> or <code><pre></code> element, the text within the element does not begin with white space.
<!--End section: White Space in textarea and pre Elements-->
</div>
<div id="elements-that-cannot-contain-special-characters" class="section">
<h4><span class="secno">6.5.2 </span>Elements that Cannot Contain Special Characters</h4>
<p>
- Due to the conflict between parsing rules between HTML and XML,
-polyglot markup uses the following elements only if they do not contain
-angled brackets ("<" or ">") or ampersands ("&").
+ Due to the conflict between parsing rules between HTML and XML, <a class="internalDFN" href="#dfn-polyglot-markup">polyglot markup</a> uses the following elements only if they do not contain angled brackets ("<" or ">") or ampersands ("&").
</p>
<ul>
<li><code>plaintext</code></li>
@@ -1092,15 +1085,15 @@
<div id="attributes" class="section">
<!--OddPage--><h2><span class="secno">7. </span>Attributes</h2>
-<p>Because of attribute-value normalization in XML [<cite><a href="#bib-XML10" rel="biblioentry" class="bibref">XML10</a></cite>], polyglot markup does not contain tabs, line feeds, or carriage returns within CDATA attributes.
+<p>Because of attribute-value normalization in XML [<cite><a href="#bib-XML10" rel="biblioentry" class="bibref">XML10</a></cite>], <a class="internalDFN" href="#dfn-polyglot-markup">polyglot markup</a> does not contain tabs, line feeds, or carriage returns within CDATA attributes.
</p>
-<p>Polyglot markup surrounds all attribute values with quotation marks.
- Attribute values <em title="may" class="rfc2119">may</em> be surrounded either by single quotation marks or by double quotation marks.</p>
+<p><a class="internalDFN" href="#dfn-polyglot-markup" title="polyglot markup">Polyglot markup</a> surrounds all attribute values with quotation marks.
+ <a class="internalDFN" href="#dfn-polyglot-markup" title="polyglot markup">Polyglot markup</a> surrounds attribute values by either single quotation marks or by double quotation marks.</p>
<p>See also <a href="#attribute-values">Attribute Values</a>.</p>
<div id="disallowed-attributes" class="section">
<h3><span class="secno">7.1 </span>Disallowed Attributes</h3>
- <p>The following attributes are not allowed in polyglot markup.
+ <p>The following attributes are not allowed in <a class="internalDFN" href="#dfn-polyglot-markup">polyglot markup</a>.
These attributes have effects in documents parsed as XML but do not have effects in documents parsed as text/html.
The HTML5 spec therefore defines them as invalid in text/html documents. [<cite><a href="#bib-HTML5" rel="biblioentry" class="bibref">HTML5</a></cite>]
</p>
@@ -1115,9 +1108,9 @@
<div id="language-attributes" class="section">
<h3><span class="secno">7.2 </span>Language Attributes</h3>
- <p>When using language attributes, polyglot markup <em title="must" class="rfc2119">must</em> use both the <code>lang</code> and <code>xml:lang</code> attributes.
- Neither attribute is to be used without the other, and the values for both <code>lang</code> and <code>xml:lang</code> <em title="must" class="rfc2119">must</em> be the same.</p>
- <p>Polyglot markup <em title="should" class="rfc2119">should</em> use the language attributes in the <code>html</code> element to set the default language for the document.</p>
+ <p>When using language attributes, <a class="internalDFN" href="#dfn-polyglot-markup">polyglot markup</a> uses both the <code>lang</code> and <code>xml:lang</code> attributes.
+ Neither attribute is to be used without the other, and <a class="internalDFN" href="#dfn-polyglot-markup">polyglot markup</a> maintains identical values for both <code>lang</code> and <code>xml:lang</code>.</p>
+ <p><a class="internalDFN" href="#dfn-polyglot-markup" title="polyglot markup">Polyglot markup</a> uses the language attributes in the <code>html</code> element to set the default language for the document.</p>
<!--End section: Language Attributes-->
</div>
@@ -1127,7 +1120,7 @@
<div id="named-entity-references" class="section">
<!--OddPage--><h2><span class="secno">8. </span>Named Entity References</h2>
- <p>Polyglot markup uses only the following named entity references:</p>
+ <p><a class="internalDFN" href="#dfn-polyglot-markup" title="polyglot markup">Polyglot markup</a> uses only the following named entity references:</p>
<ul>
<li><code>amp</code></li>
<li><code>lt</code></li>
@@ -1136,9 +1129,9 @@
<li><code>quot</code></li>
</ul>
<p>
- For entities beyond the previous list, a polyglot document uses character references.
- For example, polyglot markup uses <code>&#xA0;</code> instead of <code>&nbsp;</code>.
- Note that polyglot markup may use decimal values for escape characters (such as &#160; in the previous example);
+ For entities beyond the previous list, <a class="internalDFN" href="#dfn-polyglot-markup">polyglot markup</a> uses character references.
+ For example, <a class="internalDFN" href="#dfn-polyglot-markup">polyglot markup</a> uses <code>&#xA0;</code> instead of <code>&nbsp;</code>.
+ Note that <a class="internalDFN" href="#dfn-polyglot-markup">polyglot markup</a> may use decimal values for escape characters (such as &#160; in the previous example);
however, the <a href="http://www.w3.org/TR/2005/REC-charmod-20050215/#C048">Character Model for the World Wide Web</a> recommends
that content <em title="should" class="rfc2119">should</em> use the hexadecimal form of character escapes rather than the decimal form when both are available. [<cite><a href="#bib-CHARMOD" rel="biblioentry" class="bibref">CHARMOD</a></cite>]
</p>
@@ -1149,33 +1142,33 @@
<div id="script-and-style" class="section">
<!--OddPage--><h2><span class="secno">9. </span>Script and Style</h2>
- <p>Script and style commands <em title="should" class="rfc2119">should</em> be included by linking to external files rather than including them in-line.
- However, polyglot markup <em title="must not" class="rfc2119">must not</em> link to an external stylesheet by using the xml-stylesheet processing instruction.
+ <p>
+ <a class="internalDFN" href="#dfn-polyglot-markup" title="polyglot markup">Polyglot markup</a> includes script and style commands by linking to external files rather than including them in-line.
+ <a class="internalDFN" href="#dfn-polyglot-markup" title="polyglot markup">Polyglot markup</a> does not link to an external stylesheet by using the xml-stylesheet processing instruction.
See also <a href="#PI-and-xml">Processing Instructions and the XML Declaration</a>.
</p>
- <p>The following examples show the proper way to include external script and style, respectively:</p>
+ <p>The following examples show how <a class="internalDFN" href="#dfn-polyglot-markup">polyglot markup</a> includes external script and style, respectively:</p>
<pre class="example"><script src="external.js"></script></pre>
<pre class="example"><link rel="stylesheet" href="external.css"/></pre>
<p>Although <code>document.write()</code> and <code>document.writeln()</code> are valid in an HTML document, neither function may be used in XHTML.
- Therefore, neither is used in polyglot markup.
+ Therefore, neither is used in <a class="internalDFN" href="#dfn-polyglot-markup">polyglot markup</a>.
Instead, use the <code>innerHTML</code> property for both HTML and XHTML.
Note that the <code>innerHTML</code> property takes a string.
XML parsers parse the string as XML in XHTML.
HTML parsers parse the string as HTML in HTML.
- Because of the difference in parsing, if you send the parser content
-that does not follow the rules for polyglot markup the results will
-differ for a DOM create with an XML parser and one created with an HTML
-parser.
+ Because of the difference in parsing, if you send the parser content that does not follow the rules for <a class="internalDFN" href="#dfn-polyglot-markup">polyglot markup</a>
+ the results will differ for a DOM create with an XML parser and one created with an HTML parser.
</p>
<div id="external-script-and-style" class="section">
<h3><span class="secno">9.1 </span>External Script and Style</h3>
- <p>Polyglot markup uses external scripts if that document's script or style sheet uses <code><</code> or <code>&</code> or <code>]]></code> or <code>--</code>.
+ <p><a class="internalDFN" href="#dfn-polyglot-markup" title="polyglot markup">Polyglot markup</a> uses external scripts if that document's script or style sheet uses <code><</code> or <code>&</code> or <code>]]></code> or <code>--</code>.
Note that XML parsers are permitted to silently remove the
-contents of comments; therefore, the historical practice of hiding
-scripts and style sheets within comments to make the documents backward
-compatible is likely to not work as expected in XML-based user agents.
+contents of comments;
+ therefore, the historical practice of hiding scripts and style
+sheets within comments to make the documents backward compatible is
+likely to not work as expected in XML-based user agents.
</p>
<!--End section: External Script and Style-->
@@ -1183,8 +1176,8 @@
<div id="in-line-script-and-style" class="section">
<h3><span class="secno">9.2 </span>In-line Script and Style</h3>
- <p>If polyglot markup must use script or style commands within its source code, either use safe content or wrap the command in a <code>CDATA</code> section.
- However, polyglot markup does not use a <code>CDATA</code> section unless it is being used within foreign content.
+ <p>If <a class="internalDFN" href="#dfn-polyglot-markup">polyglot markup</a> must use script or style commands within its source code, either use safe content or wrap the command in a <code>CDATA</code> section.
+ However, <a class="internalDFN" href="#dfn-polyglot-markup">polyglot markup</a> does not use a <code>CDATA</code> section unless it is being used within foreign content.
</p>
<div id="safe-content" class="section">
@@ -1199,7 +1192,7 @@
<div id="wrapping-in-cdata" class="section">
<h4><span class="secno">9.2.2 </span>Wrapping a Command in a CDATA Section</h4>
- <p>Note that you cannot achieve same DOM in both XHTML and HTML by using in-line commands in a CDATA section.
+ <p>Note that you cannot achieve the same DOM in both XHTML and HTML by using in-line commands in a CDATA section.
However, this is not usally a problem unless the code has a dependency on the exact number of text nodes under a <code><script></code> or <code><style></code> element.
The following examples show in-line script and style commands wrapped in a <code>CDATA</code> section.
</p>
@@ -1213,11 +1206,11 @@
(styles go here)
/*]]>*/
</style></pre>
- <p>When using MathML or SVG, the parser follows the XML parsing
-rules.
- Polyglot markup does not rely on getting a CDATA instance from the
-DOM when using MathML or SVG, because the HTML parser does not create a
-CDATA instance in the DOM.
+ <p>When using MathML or SVG, the parser follows the XML parsing rules.
+ <a class="internalDFN" href="#dfn-polyglot-markup" title="polyglot markup">Polyglot markup</a>
+ does not rely on getting a CDATA instance from the DOM when using
+MathML or SVG, because the HTML parser does not create a CDATA instance
+in the DOM.
</p>
<!--End section: Wrapping a Command in a CDATA Section-->
@@ -1230,14 +1223,174 @@
</div>
<div id="foreign-content" class="section">
-<!--OddPage--><h2><span class="secno">10. </span>Exceptions from the Foreign Content Parsing Rules</h2>
-<p>
- <!-- TODO: Need to call out exceptions from the foreign content parsing rules (e.g. <foreignContent> -->
-</p>
+ <!--OddPage--><h2><span class="secno">10. </span>Exceptions from the Foreign Content Parsing Rules</h2>
+ <p>
+ <!-- TODO: Need to call out exceptions from the foreign content parsing rules (e.g. <foreignContent> -->
+ </p>
<!--End section: Exceptions from the Foreign Content Parsing Rules-->
</div>
+<div id="example-document" class="section">
+ <!--OddPage--><h2><span class="secno">11. </span>Example Document</h2>
+ <p>
+ The following example code acts as <a class="internalDFN" href="#dfn-polyglot-markup">polyglot markup</a> and validates as eother XHTML or as HTML. You can view the page live
+ at <a href="http://dev.w3.org/html5/html-xhtml-author-guide/SamplePage.html">http://dev.w3.org/html5/html-xhtml-author-guide/SamplePage.html</a>.
+ </p>
+ <pre class="example"><!DOCTYPE html>
+
+
+<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
+
+ <head>
+ <title>A Sample Page Using Polglot Markup</title>
+ <!-- The link element is self-closing as described in <a href="#empty-elements">Section 6.4 Empty Elements</a> -->
+ <!-- Style commands are included by linking to an external file rather than including them in-line,
+ as described in <a href="#script-and-style">Section 9. Script and Style</a> -->
+ <link type="text/css" rel="stylesheet" href="Sample.css"/>
+ </head>
+
+ <body>
+ <h1>Sample Page Using Polyglot Markup</h1>
+ <p>
+ The source code for <a href="http://dev.w3.org/html5/html-xhtml-author-guide/SamplePage.html">this document</a> uses <a class="internalDFN" href="#dfn-polyglot-markup">polyglot markup</a>,
+ a document that is a stream of bytes that parses into identical document trees
+ (with the exception of the xmlns attribute on the root element) when processed as HTML and when processed as XML.
+ The source code for <a href="http://dev.w3.org/html5/html-xhtml-author-guide/SamplePage.html">this document</a> also contains additional comments about the use of
+ <a class="internalDFN" href="#dfn-polyglot-markup">polyglot markup</a>.
+ </p>
+
+ <h2>Foreign Elements</h2>
+ <p>
+ The following shapes use SVG elements.
+ <a class="internalDFN" href="#dfn-polyglot-markup" title="polyglot markup">Polyglot markup</a> introduces undeclared (native) default namespaces
+ for the the root SVG element (<svg>) and respects the mixed-case element names and values
+ when appropriate, as described in sections <a href="#element-level-namespaces">5.1 Element-Level Namespaces</a>,
+ <a href="#element-names">6.3.1 Element Names</a>, and <a href="#attribute-values">6.3.3 Attribute Values</a>.
+ </p>
+
+ <!-- <a class="internalDFN" href="#dfn-polyglot-markup" title="polyglot markup">Polyglot markup</a> declares the xlink: namespace on the <svg> element to maintain XML-compatibility -->
+ <svg width="350" height="250" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
+ <g>
+ <title>Three SVG shapes</title>
+ <desc>
+ This SVG image contains an ellipse filled with a gradient that goes from white to blue as it moves outward from the center.
+ A yellow rectangle with a black border overlaps the ellipse in the upper-left quadrant,
+ and a red spiral on a white background overlaps the ellipse in the bottom-right quadrant.
+ The red spiral is also a link to the example code for that SVG shape.
+ </desc>
+ <defs>
+ <!-- Note that "radialGradient" and "myGradient" respect mixed-case values. -->
+ <radialGradient id="myGradient" cx="50%" cy="50%" r="50%" fx="50%" fy="50%">
+ <stop offset="0%" style="stop-color:rgb(200,200,200); stop-opacity:0"/>
+ <stop offset="100%" style="stop-color:rgb(0,0,255); stop-opacity:1"/>
+ </radialGradient>
+ </defs>
+ <ellipse cx="50%" cy="50%" rx="50%" ry="42%" style="fill:url(#myGradient)"/>
+ <rect x="0" y="0" width="100" height="100" style="fill: yellow; stroke: black;"/>
+ <a xlink:href="http://www.w3schools.com/svg/tryit.asp?filename=path2&type=svg">
+ <path transform="translate(60, -175)" d="M153 334
+ C153 334 151 334 151 334
+ C151 339 153 344 156 344
+ C164 344 171 339 171 334
+ C171 322 164 314 156 314
+ C142 314 131 322 131 334
+ C131 350 142 364 156 364
+ C175 364 191 350 191 334
+ C191 311 175 294 156 294
+ C131 294 111 311 111 334
+ C111 361 131 384 156 384
+ C186 384 211 361 211 334
+ C211 300 186 274 156 274"
+ style="fill:white;stroke:red;stroke-width:2"/>
+ </a>
+ </g>
+ </svg>
+ <h2>Empty Elements</h2>
+ <!-- Given an empty instance of an element whose content model is not EMPTY (in this case, an empty paragraph)
+ <a class="internalDFN" href="#dfn-polyglot-markup">polyglot markup</a> does not use the minimized form, as described in <a href="#empty-elements">Section 6.4 Empty Elements</a> -->
+ <p></p>
+ <p>
+ There is an empty <p> element before this paragraph.
+ <a class="internalDFN" href="#dfn-polyglot-markup" title="polyglot markup">Polyglot markup</a> uses <p></p> and not <p />.
+ </p>
+ <p>
+ <a class="internalDFN" href="#dfn-polyglot-markup" title="polyglot markup">Polyglot markup</a> treats certain elements as self-closing,
+ empty elements, such as the following <img> element.
+ </p>
+ <img height="48" width="72" alt="W3C" src="http://www.w3.org/Icons/w3c_home"/>
+ <p>
+ For more information, see <a href="#empty-elements">Section 6.4 Empty Elements</a>.
+ </p>
+
+
+ <h2>Required Elements</h2>
+ <p>
+ The following table uses the required <tbody> element, as described in
+ <a href="#required-elements">Section 6.1 Required Elements</a>.
+ </p>
+ <table>
+ <tbody>
+ <tr>
+ <th>Column One</th>
+ <th>Column Two</th>
+ </tr>
+ <tr>
+ <td>Row 1, Column 1</td>
+ <td>Row 1, Column 2</td>
+ </tr>
+ <tr>
+ <td>Row 2, Column 1</td>
+ <td>Row 2, Column 2</td>
+ </tr>
+ <tr>
+ <td>Row 3, Column 1</td>
+ <td>Row 3, Column 2</td>
+ </tr>
+ </tbody>
+ </table>
+
+ <p>
+ The following table uses the required <colgroup> element, as described in
+ <a href="#required-elements">Section 6.1 Required Elements</a>.
+ </p>
+ <table>
+ <colgroup>
+ <col style="background-color:silver"/>
+ <col style="background-color:gray"/>
+ <col style="background-color:yellow"/>
+ </colgroup>
+ <tr>
+ <th>ISBN</th>
+ <th>Title</th>
+ <th>Price</th>
+ </tr>
+ <tr>
+ <td>3476896</td>
+ <td>My first HTML</td>
+ <td>$53</td>
+ </tr>
+ <tr>
+ <td>1234567</td>
+ <td>Intermediate Polyglot</td>
+ <td>$49</td>
+ </tr>
+ </table>
+
+
+ <h2>Named Entity References</h2>
+ <p>
+ This paragraph uses the string "&amp;" for ampersands ("&") and uses the string "&#xA0;"
+ for a nonbreaking space between the words "polyglot markup," as described in
+ <a href="#named-entity-references">Section 8. Named Entity References</a>.
+ </p>
+ </body>
+</html> </pre>
+
+<!--End section: Exceptions from the Foreign Content Parsing Rules-->
+</div>
+
+
<div id="acknowledgements" class="appendix section">
<!--OddPage--><h2><span class="secno">A. </span>Acknowledgements</h2>
<p>
@@ -1287,6 +1440,5 @@
</div>
</div>
-</body>
-</html>
\ No newline at end of file
+</body></html>
\ No newline at end of file
Received on Monday, 6 December 2010 20:40:43 UTC