HTML Standard Tracker

Filter

File a bug

SVNBugCommentTime (UTC)
2725[Authors] [Conformance Checkers] Make the legacy DOCTYPE string be compatible with more tools. Clarify some XML DOCTYPE comments.2009-01-30 08:33
@@ -857,31 +857,20 @@
   encouraged.</p>
 
   <p id="authors-using-xhtml"><span>XHTML</span> documents (<span>XML
   documents</span> using elements from the <span>HTML
   namespace</span>) that use the new features described in this
   specification and that are served over the wire (e.g. by HTTP) must
   be sent using an XML MIME type such as <code>application/xml</code>
   or <code>application/xhtml+xml</code> and must not be served as
   <code>text/html</code>. <a href="#refsRFC3023">[RFC3023]</a></p>
 
-  <p>Such XML documents may contain a <code>DOCTYPE</code> if desired,
-  but this is not required to conform to this specification.</p>
-
-  <p class="note">According to the XML specification, XML processors
-  are not guaranteed to process the external DTD subset referenced in
-  the DOCTYPE. This means, for example, that using entity references
-  for characters in XHTML documents is unsafe (except for <code
-  title="">&amp;lt;</code>, <code title="">&amp;gt;</code>, <code
-  title="">&amp;amp;</code>, <code title="">&amp;quot;</code> and
-  <code title="">&amp;apos;</code>).</p>
-
   <p id="authors-using-html"><span title="HTML5">HTML
   documents</span>, if they are served over the wire (e.g. by HTTP)
   must be labeled with the <code>text/html</code> MIME type.</p> <!--
   XXX update RFC 2854 -->
 
   <p id="entity-references">The language in this specification assumes
   that the user agent expands all entity references, and therefore
   does not include entity reference nodes in the DOM. If user agents
   do include entity reference nodes in the DOM, then user agents must
   handle them as if they were fully expanded when implementing this
@@ -52807,41 +52796,43 @@ interface <dfn>MessageChannel</dfn> {
    <li>One or more <span title="space character">space characters</span>.</li>
    <li>A string that is an <span>ASCII case-insensitive</span> match for the string "<code title="">HTML</code>".</li>
    <li>Optionally, a <span>DOCTYPE legacy string</span> (defined below).</li>
    <li>Zero or more <span title="space character">space characters</span>.</li>
    <li>A U+003E GREATER-THAN SIGN (<code>&gt;</code>) character.</li>
   </ol>
 
   <p class="note">In other words, <code>&lt;!DOCTYPE HTML></code>,
   case-insensitively.</p>
 
-  <p>For the purposes of XSLT generators that cannot output HTML
-  markup without a DOCTYPE, a <dfn>DOCTYPE legacy string</dfn> may be
-  inserted into the DOCTYPE (in the position defined above). This
-  string must consist of:</p>
+  <p>For the purposes of HTML generators that cannot output HTML
+  markup with the short DOCTYPE "<code title="">&lt;!DOCTYPE
+  HTML></code>", a <dfn>DOCTYPE legacy string</dfn> may be inserted
+  into the DOCTYPE (in the position defined above). This string must
+  consist of:</p>
 
   <ol class="brief">
    <li>One or more <span title="space character">space characters</span>.</li>
-   <li>A string that is an <span>ASCII case-insensitive</span> match for the string "<code title="">PUBLIC</code>".</li>
+   <li>A string that is an <span>ASCII case-insensitive</span> match for the string "<code title="">SYSTEM</code>".</li>
    <li>One or more <span title="space character">space characters</span>.</li>
    <li>A U+0022 QUOTATION MARK or U+0027 APOSTROPHE character (the <i>quote mark</i>).</li>
-   <li>The literal string "<code title="">XSLT-compat</code>".</li>
+   <li>The literal string "<code title="">about:legacy-compat</code>".</li>
    <li>A matching U+0022 QUOTATION MARK or U+0027 APOSTROPHE character (i.e. the same character as in the earlier step marked <i>quote mark</i>).</li>
   </ol>
 
-  <p class="note">In other words, <code>&lt;!DOCTYPE HTML PUBLIC
-  "XSLT-compat"></code> or <code>&lt;!DOCTYPE HTML PUBLIC
-  'XSLT-compat'></code>, case-insensitively except for the bit in
-  quotes.</p>
+  <p class="note">In other words, <code>&lt;!DOCTYPE HTML SYSTEM
+  "about:legacy-compat"></code> or <code>&lt;!DOCTYPE HTML PUBLIC
+  'about:legacy-compat'></code>, case-insensitively except for the bit
+  in quotes.</p>
 
   <p>The <span>DOCTYPE legacy string</span> should not be used unless
-  the document is generated from XSLT.</p>
+  the document is generated from a system that cannot output the
+  shorter string.</p>
 
 
 
   <h4>Elements</h4>
 
   <p>There are five different kinds of <dfn
   title="syntax-elements">elements</dfn>: void elements, CDATA
   elements, RCDATA elements, foreign elements, and normal
   elements.</p>
 
@@ -56656,24 +56647,24 @@ interface <dfn>MessageChannel</dfn> {
     <p>Append a <code>Comment</code> node to the <code>Document</code>
     object with the <code title="">data</code> attribute set to the
     data given in the comment token.</p>
    </dd>
 
    <dt>A DOCTYPE token</dt>
    <dd>
 
     <p>If the DOCTYPE token's <code title="">name</code> is not a
     <span>case-sensitive</span> match for the string "<code
-    title="">html</code>", or if the token's public identifier is
-    neither missing nor a <span>case-sensitive</span> match for the
-    string "<code>XSLT-compat</code>", or if the token's system
-    identifier is not missing, then there is a <span>parse
+    title="">html</code>", or if the token's public identifier is not
+    missing, or if the token's system identifier is neither missing
+    nor a <span>case-sensitive</span> match for the string
+    "<code>about:legacy-compat</code>", then there is a <span>parse
     error</span> (this is the <dfn>DOCTYPE parse
     error</dfn>). Conformance checkers may, instead of reporting this
     error, switch to a conformance checking mode for another language
     (e.g. based on the DOCTYPE token a conformance checker could
     recognize that the document is an HTML4-era document, and defer to
     an HTML4 conformance checker.)</p>
 
     <p>Append a <code>DocumentType</code> node to the
     <code>Document</code> node, with the <code title="">name</code>
     attribute set to the name given in the DOCTYPE token, or the empty
@@ -60737,20 +60728,34 @@ http://lxr.mozilla.org/seamonkey/search?string=nested
   <h3>Writing XHTML documents</h3>
 
   <p>The syntax for using HTML with XML, whether in XHTML documents or
   embedded in other XML documents, is defined in the XML and
   Namespaces in XML specifications. <a href="#refsXML">[XML]</a> <a
   href="#refsXMLNS">[XMLNS]</a></p>
 
   <p>This specification does not define any syntax-level requirements
   beyond those defined for XML proper.</p>
 
+  <p>XML documents may contain a <code>DOCTYPE</code> if desired, but
+  this is not required to conform to this specification. This
+  specification does not define a public or system identifier, nor
+  provide a format DTD.</p>
+
+  <p class="note">According to the XML specification, XML processors
+  are not guaranteed to process the external DTD subset referenced in
+  the DOCTYPE. This means, for example, that using entity references
+  for characters in XHTML documents is unsafe if they are defined in
+  an external file (except for <code title="">&amp;lt;</code>, <code
+  title="">&amp;gt;</code>, <code title="">&amp;amp;</code>, <code
+  title="">&amp;quot;</code> and <code
+  title="">&amp;apos;</code>).</p>
+
 
   <h3>Parsing XHTML documents</h3>
 
   <p>This section describes the relationship between XML and the DOM,
   with a particular emphasis on how this interacts with HTML.</p>
 
   <p>An <dfn>XML parser</dfn>, for the purposes of this specification,
   is a construct that follows the rules given in the XML specification
   to map a string of bytes or characters into a <code>Document</code>
   object.</p>

|