- From: Eliot Graff via cvs-syncmail <cvsmail@w3.org>
- Date: Sat, 12 Feb 2011 00:32:23 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/html-xhtml-author-guide
In directory hutz:/tmp/cvs-serv23748
Modified Files:
html-xhtml-authoring-guide.html
Log Message:
Rewrote Introduction to include correct MIME types and use cases (per bugs 11754 & 11755) as well as principles of polyglot (11909); added @srcdoc example to "Attributes" (per bug 10788); added note to "Language Attributes" (per bug 10152); removed 9.2.2 "Wrapping a Command in a CDATA Section" and consolidated 9.2, "In-line Script and Style," and 9.2.1, "Safe Content" (as a result of actions for bug 11909); added sentence to "Named Entity References" disallowing "&" and "<" as characters (bug 11905); Deleted section 6.5.2 Elements that Cannot Contain Special Characters, as these elements are deprecated in HTML5 (bug 11904); Added section for attributes with special considerations and populated it with note to not use spaces within @id, per bug 11910;
Index: html-xhtml-authoring-guide.html
===================================================================
RCS file: /sources/public/html5/html-xhtml-author-guide/html-xhtml-authoring-guide.html,v
retrieving revision 1.54
retrieving revision 1.55
diff -u -d -r1.54 -r1.55
--- html-xhtml-authoring-guide.html 26 Jan 2011 23:48:32 -0000 1.54
+++ html-xhtml-authoring-guide.html 12 Feb 2011 00:32:21 -0000 1.55
@@ -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 26 January 2011</h2>
+ <h2 id="w3c-editor-s-draft-05-january-2011">W3C Editor's Draft 11 February 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>
@@ -96,8 +96,9 @@
<!--End of Status of This Document-->
</div>
- <div>
-<h2 class="introductory" id="toc">Table of Contents</h2>
+<!-- TOC -->
+<div class="section" id="toc">
+<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>
@@ -112,8 +113,7 @@
<li class="tocline"><a class="tocxref" href="#elements"><span class="secno">6. </span>Elements</a>
<ul class="toc">
<li class="tocline"><a class="tocxref" href="#required-elements"><span class="secno">6.1 </span>Required Elements</a></li>
- <li class="tocline"><a class="tocxref" href="#elements-that-cannot-be-used"><span class="secno">6.2 </span>
- Elements that Cannot Be Used in Polyglot Markup</a></li>
+ <li class="tocline"><a class="tocxref" href="#elements-that-cannot-be-used"><span class="secno">6.2 </span>Elements that Cannot Be Used in Polyglot Markup</a></li>
<li class="tocline"><a class="tocxref" href="#case-sensitivity"><span class="secno">6.3 </span>Case-Sensitivity</a>
<ul class="toc">
<li class="tocline"><a class="tocxref" href="#element-names"><span class="secno">6.3.1 </span>Element Names</a></li>
@@ -122,14 +122,9 @@
</ul>
</li>
<li class="tocline"><a class="tocxref" href="#empty-elements"><span class="secno">6.4 </span>Void Elements</a></li>
- <li class="tocline"><a class="tocxref" href="#elements-with-soecial-considerations"><span class="secno">6.5 </span>
- Elements with Special Considerations</a>
+ <li class="tocline"><a class="tocxref" href="#elements-with-special-considerations"><span class="secno">6.5 </span>Elements with Special Considerations</a>
<ul class="toc">
- <li class="tocline"><a class="tocxref" href="#newlines-in-textarea-and-pre"><span class="secno">6.5.1 </span>
- Newlines in <code><textarea></code> and <code><pre></code> Elements</a></li>
- <li class="tocline"><a class="tocxref" href="#elements-that-cannot-contain-special-characters"><span class="secno">6.5.2 </span>
- Elements that Cannot Contain Special Characters</a></li>
-
+ <li class="tocline"><a class="tocxref" href="#newlines-in-textarea-and-pre"><span class="secno">6.5.1 </span>Newlines in <code><textarea></code> and <code><pre></code> Elements</a></li>
</ul>
</li>
</ul>
@@ -138,19 +133,18 @@
<ul class="toc">
<li class="tocline"><a class="tocxref" href="#disallowed-attributes"><span class="secno">7.1 </span>Disallowed Attributes</a></li>
<li class="tocline"><a class="tocxref" href="#language-attributes"><span class="secno">7.2 </span>Language Attributes</a></li>
+ <li class="tocline"><a class="tocxref" href="#attributes-with-special-considerations"><span class="secno">7.3 </span>Attributes with Special Considerations</a>
+ <ul class="toc">
+ <li class="tocline"><a class="tocxref" href="#id-attribute"><span class="secno">7.3.1 </span>The <code>id</code> Attribute</a></li>
+ </ul>
+ </li>
</ul>
</li>
<li class="tocline"><a class="tocxref" href="#named-entity-references"><span class="secno">8. </span>Named Entity References</a></li>
<li class="tocline"><a class="tocxref" href="#script-and-style"><span class="secno">9. </span>Script and Style</a>
<ul class="toc">
<li class="tocline"><a class="tocxref" href="#external-script-and-style"><span class="secno">9.1 </span>External Script and Style</a></li>
- <li class="tocline"><a class="tocxref" href="#in-line-script-and-style"><span class="secno">9.2 </span>In-line Script and Style</a>
- <ul class="toc">
- <li class="tocline"><a class="tocxref" href="#safe-content"><span class="secno">9.2.1 </span>Safe Content</a></li>
- <li class="tocline"><a class="tocxref" href="#wrapping-in-cdata"><span class="secno">9.2.2 </span>
- Wrapping a Command in a CDATA Section</a></li>
- </ul>
- </li>
+ <li class="tocline"><a class="tocxref" href="#in-line-script-and-style"><span class="secno">9.2 </span>In-line Script and Style</a></li>
</ul>
</li>
<li class="tocline"><a class="tocxref" href="#comments"><span class="secno">10. </span>Comments in Polyglot Markup</a></li>
@@ -165,6 +159,50 @@
</li>
</ul>
</div>
+<!-- End TOC -->
+
+
+<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.
+ 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.
+ 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>:
+ </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>
+ </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>by conformance to any XML DTD.</li>
+ </ul>
+ <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
+ 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,
+ especially if that content is not sent through a tool chain.
+ </p>
+<!--End section: Introduction-->
+</div>
@@ -180,6 +218,15 @@
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—such as
+ quick testing or even hand-authoring—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>
@@ -611,18 +658,6 @@
<!--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, <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>
- <li><code>xmp</code></li>
- </ul>
-<!--End section: Elements that Cannot Contain Special Characters-->
- </div>
-
<!--End section: Elements with Special Considerations-->
</div>
@@ -637,7 +672,10 @@
For example, within an attribute's value, <a class="internalDFN" href="#dfn-polyglot-markup">polyglot markup</a> uses <code>&#x9;</code> for a tab
rather than the literal character <code>'\t'</code>.
This is because of attribute-value normalization in XML [<cite><a href="#bib-XML10" rel="biblioentry" class="bibref">XML10</a></cite>].
+ The following example uses numeric character references (escaped characters) for the line feed and tab within a <code>srcdoc</code> attribute.
</p>
+<pre class="example"><iframe srcdoc="<p>Hello &#x0A; &#x09; world!</p>" src="demo_iframe_srcdoc.htm"></iframe></pre>
+
<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.
@@ -665,11 +703,35 @@
<h3><span class="secno">7.2 </span>Language Attributes</h3>
<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>
+ <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>
+ <p class="note">
+ If <a class="internalDFN" href="#dfn-polyglot-markup">polyglot markup</a> uses the <code>http-equiv</code> attribute on the <code><meta></code> element, <a class="internalDFN" href="#dfn-polyglot-markup">polyglot markup</a> <em title="must" class="rfc2119">must</em> use both the <code>lang</code> and <code>xml:lang</code> attributes.
+ </p>
<!--End section: Language Attributes-->
</div>
+ <div id="attributes-with-special-considerations" class="section">
+ <h3><span class="secno">7.3 </span>Attributes with Special Considerations</h3>
+ <p>
+ The following attributes or their considerations require exceptions to the general rules for <a class="internalDFN" href="#dfn-polyglot-markup">polyglot markup</a>.
+ </p>
+
+ <div id="id-attribute" class="section">
+ <h4><span class="secno">7.3.1 </span>The <code>id</code> Attribute</h4>
+ <p>
+ <a class="internalDFN" href="#dfn-polyglot-markup" title="polyglot markup">Polyglot markup</a> does not contain any space characters within the value of an <code>id</code> attribute.
+ This is because values for the <code>id</code> attribute <a href="http://dev.w3.org/html5/spec/elements.html#the-id-attribute">may not contain space characters</a> in HTML5. [<cite><a href="#bib-HTML5" rel="biblioentry" class="bibref">HTML5</a></cite>]
+ </p>
+ <!-- End section: The id Attribute -->
+ </div>
+
+
+<!-- End section: Attributes with Special Considerations -->
+ </div>
+
<!--End section: Attributes-->
</div>
@@ -691,6 +753,10 @@
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>
+ <p>
+ <a class="internalDFN" href="#dfn-polyglot-markup" title="polyglot markup">Polyglot markup</a> always uses character references for the less than sign (<code><</code>) and ampersand (<code>&</code>) when they are used as characters,
+ except when those characters appear inside a CDATA section.
+ </p>
<!--End section: Named Entity References-->
</div>
@@ -716,63 +782,32 @@
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><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>.
+ <div id="external-script-and-style" class="section">
+ <h3><span class="secno">9.1 </span>External Script and Style</h3>
+ <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
+ Note that XML parsers are permitted to silently remove the
contents of comments;
- therefore, the historical practice of hiding scripts and style
+ 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>
-
+ </p>
+
<!--End section: External Script and Style-->
- </div>
-
- <div id="in-line-script-and-style" class="section">
- <h3><span class="secno">9.2 </span>In-line Script and Style</h3>
- <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">
- <h4><span class="secno">9.2.1 </span>Safe Content</h4>
- <p>Safe content is content that does not contain a <code><</code> or <code>&</code> character.
- The following example is safe because it does not contain problematic characters within the <code><script></code> tag.
- </p>
- <pre class="example"><script>document.body.appendChild(document.createElement("div"));</script></pre>
+ </div>
- <!--End section: Safe Content-->
- </div>
-
- <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 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>
- <pre class="example"><script>
- //<![CDATA[
- (script goes here)
- //]]>
- </script></pre>
- <pre class="example"><style>
- /*<![CDATA[*/
- (styles go here)
- /*]]>*/
- </style></pre>
- <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-->
- </div>
+ <div id="in-line-script-and-style" class="section">
+ <h3><span class="secno">9.2 </span>In-line Script and Style</h3>
+ <p>
+ When <a class="internalDFN" href="#dfn-polyglot-markup">polyglot markup</a> must use script or style commands within its source code, it uses safe content.
+ </p>
+ <p>
+ Safe content is content that does not contain a <code><</code> or <code>&</code> character.
+ The following example is safe because it does not contain problematic characters within the <code><script></code> tag.
+ </p>
+ <pre class="example"><script>document.body.appendChild(document.createElement("div"));</script></pre>
-<!--End section: In-line Script and Style-->
+ <!--End section: In-line Script and Style-->
</div>
<!--End section: Script and Style-->
@@ -957,15 +992,15 @@
<!--End section: Example Document-->
</div>
+
+<!-- Appendix -->
<div id="acknowledgements" class="appendix section">
-<!--OddPage--><h2><span class="secno">A. </span>Acknowledgements</h2>
-<p>
- Many thanks to Daniel Glazman, Richard Ishida, Tony Ross, Sam Ruby,
-Jonas Sicking, Leif Halvard Silli, Henri Sivonen, Manu Sporny, and
-Philip Taylor.
- Special thanks to the W3C TAG and the W3C Internationalization (i18n)
-Core Working Group.
-</p>
+<h2><span class="secno">A. </span>Acknowledgements</h2>
+ <p>
+ Many thanks to Robin Berjon, David Carlisle, Daniel Glazman, Richard Ishida, Tony Ross,
+ Sam Ruby, Jonas Sicking, Leif Halvard Silli, Henri Sivonen, Manu Sporny, and Philip Taylor.
+ Special thanks to the W3C TAG and the W3C Internationalization (i18n) Core Working Group.
+ </p>
</div>
<div class="appendix section" id="references">
@@ -973,38 +1008,42 @@
<div class="section" id="normative-references">
<h3><span class="secno">B.1 </span>Normative references</h3>
+
<dl class="bibliography">
<dt id="bib-CHARMOD">[CHARMOD]</dt>
- <dd>Martin J. Dürst; et al. <a href="http://www.w3.org/TR/2005/REC-charmod-20050215">
- <cite>Character Model for the World Wide Web 1.0: Fundamentals.</cite></a> 15 February 2005. W3C Recommendation.
- URL: <a href="http://www.w3.org/TR/2005/REC-charmod-20050215">http://www.w3.org/TR/2005/REC-charmod-20050215</a>
+ <dd>Martin J. Dürst; et al. <a href="http://www.w3.org/TR/2005/REC-charmod-20050215"><cite>Character Model for the World Wide Web 1.0: Fundamentals.</cite></a>
+ 15 February 2005. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2005/REC-charmod-20050215">http://www.w3.org/TR/2005/REC-charmod-20050215</a>
</dd>
<dt id="bib-HTML5">[HTML5]</dt>
- <dd>Ian Hickson; David Hyatt. <a href="http://www.w3.org/TR/2010/WD-html5-20100304/"><cite>HTML 5.</cite></a>
- 4 March 2010. W3C Working Draft. (Work in progress.) URL: <a href="http://www.w3.org/TR/2010/WD-html5-20100304/">
- http://www.w3.org/TR/2010/WD-html5-20100304/</a>
+ <dd>Ian Hickson; David Hyatt. <a href="http://www.w3.org/TR/2010/WD-html5-20100304/"><cite>HTML 5.</cite></a> 4 March 2010. W3C Working Draft. (Work in progress.)
+ URL: <a href="http://www.w3.org/TR/2010/WD-html5-20100304/">http://www.w3.org/TR/2010/WD-html5-20100304/</a>
</dd>
<dt id="bib-HTTP11">[HTTP11]</dt>
- <dd>R. Fielding; et al. <a href="http://www.ietf.org/rfc/rfc2616.txt"><cite>Hypertext Transfer Protocol - HTTP/1.1.</cite></a>
- June 1999. Internet RFC 2616. URL: <a href="http://www.ietf.org/rfc/rfc2616.txt">http://www.ietf.org/rfc/rfc2616.txt</a>
+ <dd>R. Fielding; et al. <a href="http://www.ietf.org/rfc/rfc2616.txt"><cite>Hypertext Transfer Protocol - HTTP/1.1.</cite></a> June 1999. Internet RFC 2616. URL:
+ <a href="http://www.ietf.org/rfc/rfc2616.txt">http://www.ietf.org/rfc/rfc2616.txt</a>
</dd>
- <dt id="bib-RFC2854">[RFC2854]</dt><dd>D. Connolly; L. Masinter. <a href="http://www.rfc-editor.org/rfc/rfc2854.txt"><cite>
- The 'text/html' Media Type.</cite></a> June 2000. Internet RFC 2854. URL: <a href="http://www.rfc-editor.org/rfc/rfc2854.txt">
- http://www.rfc-editor.org/rfc/rfc2854.txt</a>
+ <dt id="bib-RFC2854">[RFC2854]</dt>
+ <dd>D. Connolly; L. Masinter. <a href="http://www.rfc-editor.org/rfc/rfc2854.txt"><cite>The 'text/html' Media Type.</cite></a> June 2000. Internet RFC 2854. URL:
+ <a href="http://www.rfc-editor.org/rfc/rfc2854.txt">http://www.rfc-editor.org/rfc/rfc2854.txt</a>
</dd>
- <dt id="bib-XML10">[XML10]</dt>
- <dd>C. M. Sperberg-McQueen; et al. <a href="http://www.w3.org/TR/2008/REC-xml-20081126/"><cite>Extensible Markup Language (XML) 1.0 (Fifth Edition).
- </cite></a> 26 November 2008. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2008/REC-xml-20081126/">
- http://www.w3.org/TR/2008/REC-xml-20081126/</a>
+ <dt id="bib-XML-MT">[XML-MT]</dt>
+ <dd>M. Murata, S. St.Laurent, D. Kohn. <a href="http://www.ietf.org/rfc/rfc3023.txt"><cite>XML Media Types</cite></a>. IETF RFC 3023. URI:
+ <a href="http://www.ietf.org/rfc/rfc3023.txt"> http://www.ietf.org/rfc/rfc3023.txt</a>.
+ </dd>
+ <dt id="bib-XML10">[XML10]</dt><dd>C. M. Sperberg-McQueen; et al. <a href="http://www.w3.org/TR/2008/REC-xml-20081126/"><cite>Extensible Markup Language (XML) 1.0 (Fifth Edition).</cite></a>
+ 26 November 2008. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2008/REC-xml-20081126/">http://www.w3.org/TR/2008/REC-xml-20081126/</a>
</dd>
</dl>
</div>
<div class="section" id="informative-references">
<h3><span class="secno">B.2 </span>Informative references</h3>
- <p>No informative references.</p>
+ <p>
+ No informative references.
+ </p>
</div>
</div>
+<!-- End Appendix -->
-
-</body></html>
\ No newline at end of file
+</body>
+</html>
Received on Saturday, 12 February 2011 00:32:25 UTC