W3C home > Mailing lists > Public > public-html-diffs@w3.org > April 2010

hixie: explain what a conforming document is (whatwg r4932)

From: poot <cvsmail@w3.org>
Date: Thu, 1 Apr 2010 14:34:38 +0900 (JST)
To: public-html-diffs@w3.org
Message-Id: <20100401053438.A10152BC3D@toro.w3.mag.keio.ac.jp>
hixie: explain what a conforming document is (whatwg r4932)

http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.3952&r2=1.3953&f=h
http://html5.org/tools/web-apps-tracker?from=4931&to=4932

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.3952
retrieving revision 1.3953
diff -u -d -r1.3952 -r1.3953
--- Overview.html	1 Apr 2010 00:51:56 -0000	1.3952
+++ Overview.html	1 Apr 2010 01:00:43 -0000	1.3953
@@ -2280,12 +2280,17 @@
   of the key word ("must", "should", "may", etc) used in introducing
   the algorithm.<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 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.<div class="impl">
+  implementors)</span>.<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 &mdash; such user agents are subject to additional rules,
+  as explained below.)<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>.<div class="impl">
 
 
 
@@ -2445,9 +2450,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
@@ -2525,7 +2530,12 @@
   e.g. to prevent denial of service attacks, to guard against running
   out of memory, or to work around platform-specific limitations.</p>
 
-  </div><p>For compatibility with existing content and prior specifications,
+  </div><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>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
   <a href="#syntax">the HTML syntax</a>). <span class="impl">Implementations
Received on Thursday, 1 April 2010 05:35:26 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 18 December 2010 06:14:18 GMT