HTML Standard Tracker

Filter

File a bug

SVNBugCommentTime (UTC)
49329178explain what a conforming document is2010-04-01 01:00
@@ -1636,26 +1636,33 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
   algorithms (such as "strip any leading space characters" or "return
   false and abort these steps") are to be interpreted with the meaning
   of the key word ("must", "should", "may", etc) used in introducing
   the algorithm.</p>
 
   <p>This specification describes the conformance criteria for <span
   class="impl">user agents (relevant to implementors) and</span>
   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 &mdash; 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-->
 
   <p>User agents fall into several (overlapping) categories with
   different conformance requirements.</p>
 
   <dl>
 
@@ -1818,23 +1825,23 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
     title="outline">document outlines</span> but increases the nesting
     level for each paragraph and does not increase the nesting level
     for each section would not be conforming.</p>
 
    </dd>
 
    <dt id="editors">Authoring tools and markup generators</dt>
 
    <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
     extent that authoring tools are not yet able to determine author
     intent. However, authoring tools must not automatically misuse
     elements or encourage their users to do so.</p>
 
     <p class="example">For example, it is not conforming to use an
     <code>address</code> element for arbitrary contact information;
     that element can only be used for marking up contact information
@@ -1907,20 +1914,27 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
 
   <p id="hardwareLimitations">User agents may impose
   implementation-specific limits on otherwise unconstrained inputs,
   e.g. to prevent denial of service attacks, to guard against running
   out of memory, or to work around platform-specific limitations.</p>
 
   </div>
 
 <!--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
   href="#writing">custom format</a> inspired by SGML (referred to as
   <span>the HTML syntax</span>). <span class="impl">Implementations
   may support only one of these two formats, although supporting both
   is encouraged.</span></p>
 
   <p id="entity-references" class="impl">The language in this
   specification assumes that the user agent expands all entity

|