[html5] r4932 - [e] (0) explain what a conforming document is Fixing http://www.w3.org/Bugs/Publ [...]

[whatwg at whatwg.org]

Author: ianh
Date: 2010-03-31 18:00:38 -0700 (Wed, 31 Mar 2010)
New Revision: 4932

Modified:
   complete.html
   index
   source
Log:
[e] (0) explain what a conforming document is
Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=9178

Modified: complete.html
===================================================================
--- complete.html	2010-04-01 00:51:48 UTC (rev 4931)
+++ complete.html	2010-04-01 01:00:38 UTC (rev 4932)
@@ -2767,13 +2767,20 @@
   documents<span class=impl> (relevant to authors and authoring tool
   implementors)</span>.</p>
 
-  <p class="note impl">There is no implied relationship between
-  document conformance requirements and implementation conformance
-  requirements. User agents are not free to handle non-conformant
-  documents as they please; the processing model described in this
-  specification applies to implementations regardless of the
-  conformity of the input documents.</p>
+  <p><dfn id=conforming-documents>Conforming documents</dfn> are those that comply with all
+  the conformance criteria for documents. For readability, some of
+  these conformance requirements are phrased as conformance
+  requirements on authors; such requirements are implicitly
+  requirements on documents: by definition, all documents are assumed
+  to have had an author. (In some cases, that author may itself be a
+  user agent — such user agents are subject to additional rules,
+  as explained below.)</p>
 
+  <p class=example>For example, if a requirement states that
+  "authors must not use the <code title="">foobar</code> element", it
+  would imply that documents are not allowed to contain elements named
+  <code title="">foobar</code>.</p>
+
   <div class=impl>
 
 
@@ -2934,9 +2941,9 @@
 
    <dd>
 
-    <p>Authoring tools and markup generators must generate conforming
-    documents. Conformance criteria that apply to authors also apply
-    to authoring tools, where appropriate.</p>
+    <p>Authoring tools and markup generators must generate
+    <a href=#conforming-documents>conforming documents</a>. Conformance criteria that apply
+    to authors also apply to authoring tools, where appropriate.</p>
 
     <p>Authoring tools are exempt from the strict requirements of
     using elements only for their specified purpose, but only to the
@@ -3018,6 +3025,13 @@
 
 
 
+  <p class="note impl">There is no implied relationship between
+  document conformance requirements and implementation conformance
+  requirements. User agents are not free to handle non-conformant
+  documents as they please; the processing model described in this
+  specification applies to implementations regardless of the
+  conformity of the input documents.</p>
+
   <p>For compatibility with existing content and prior specifications,
   this specification describes two authoring formats: one based on XML
   (referred to as <a href=#the-xhtml-syntax>the XHTML syntax</a>), and one using a <a href=#writing>custom format</a> inspired by SGML (referred to as

Modified: index
===================================================================
--- index	2010-04-01 00:51:48 UTC (rev 4931)
+++ index	2010-04-01 01:00:38 UTC (rev 4932)
@@ -2665,13 +2665,20 @@
   documents<span class=impl> (relevant to authors and authoring tool
   implementors)</span>.</p>
 
-  <p class="note impl">There is no implied relationship between
-  document conformance requirements and implementation conformance
-  requirements. User agents are not free to handle non-conformant
-  documents as they please; the processing model described in this
-  specification applies to implementations regardless of the
-  conformity of the input documents.</p>
+  <p><dfn id=conforming-documents>Conforming documents</dfn> are those that comply with all
+  the conformance criteria for documents. For readability, some of
+  these conformance requirements are phrased as conformance
+  requirements on authors; such requirements are implicitly
+  requirements on documents: by definition, all documents are assumed
+  to have had an author. (In some cases, that author may itself be a
+  user agent — such user agents are subject to additional rules,
+  as explained below.)</p>
 
+  <p class=example>For example, if a requirement states that
+  "authors must not use the <code title="">foobar</code> element", it
+  would imply that documents are not allowed to contain elements named
+  <code title="">foobar</code>.</p>
+
   <div class=impl>
 
 
@@ -2832,9 +2839,9 @@
 
    <dd>
 
-    <p>Authoring tools and markup generators must generate conforming
-    documents. Conformance criteria that apply to authors also apply
-    to authoring tools, where appropriate.</p>
+    <p>Authoring tools and markup generators must generate
+    <a href=#conforming-documents>conforming documents</a>. Conformance criteria that apply
+    to authors also apply to authoring tools, where appropriate.</p>
 
     <p>Authoring tools are exempt from the strict requirements of
     using elements only for their specified purpose, but only to the
@@ -2916,6 +2923,13 @@
 
 
 
+  <p class="note impl">There is no implied relationship between
+  document conformance requirements and implementation conformance
+  requirements. User agents are not free to handle non-conformant
+  documents as they please; the processing model described in this
+  specification applies to implementations regardless of the
+  conformity of the input documents.</p>
+
   <p>For compatibility with existing content and prior specifications,
   this specification describes two authoring formats: one based on XML
   (referred to as <a href=#the-xhtml-syntax>the XHTML syntax</a>), and one using a <a href=#writing>custom format</a> inspired by SGML (referred to as

Modified: source
===================================================================
--- source	2010-04-01 00:51:48 UTC (rev 4931)
+++ source	2010-04-01 01:00:38 UTC (rev 4932)
@@ -1643,13 +1643,20 @@
   documents<span class="impl"> (relevant to authors and authoring tool
   implementors)</span>.</p>
 
-  <p class="note impl">There is no implied relationship between
-  document conformance requirements and implementation conformance
-  requirements. User agents are not free to handle non-conformant
-  documents as they please; the processing model described in this
-  specification applies to implementations regardless of the
-  conformity of the input documents.</p>
+  <p><dfn>Conforming documents</dfn> are those that comply with all
+  the conformance criteria for documents. For readability, some of
+  these conformance requirements are phrased as conformance
+  requirements on authors; such requirements are implicitly
+  requirements on documents: by definition, all documents are assumed
+  to have had an author. (In some cases, that author may itself be a
+  user agent — such user agents are subject to additional rules,
+  as explained below.)</p>
 
+  <p class="example">For example, if a requirement states that
+  "authors must not use the <code title="">foobar</code> element", it
+  would imply that documents are not allowed to contain elements named
+  <code title="">foobar</code>.</p>
+
   <div class="impl">
 
 <!--END microdata-->
@@ -1825,9 +1832,9 @@
 
    <dd>
 
-    <p>Authoring tools and markup generators must generate conforming
-    documents. Conformance criteria that apply to authors also apply
-    to authoring tools, where appropriate.</p>
+    <p>Authoring tools and markup generators must generate
+    <span>conforming documents</span>. Conformance criteria that apply
+    to authors also apply to authoring tools, where appropriate.</p>
 
     <p>Authoring tools are exempt from the strict requirements of
     using elements only for their specified purpose, but only to the
@@ -1914,6 +1921,13 @@
 
 <!--END microdata-->
 
+  <p class="note impl">There is no implied relationship between
+  document conformance requirements and implementation conformance
+  requirements. User agents are not free to handle non-conformant
+  documents as they please; the processing model described in this
+  specification applies to implementations regardless of the
+  conformity of the input documents.</p>
+
   <p>For compatibility with existing content and prior specifications,
   this specification describes two authoring formats: one based on XML
   (referred to as <span>the XHTML syntax</span>), and one using a <a