Updates to the Conformance section based on dbaron's feedback

git-svn-id: http://svn.whatwg.org/webapps@9 340c8d12-0b0e-0410-8428-c7bf67bfef74
whatwg · Mar 10, 2006 · 27ff18e · 27ff18e
1 parent d1f8a18
commit 27ff18e
Show file tree

Hide file tree

Showing 2 changed files with 31 additions and 24 deletions.
diff --git a/index b/index
@@ -1301,11 +1301,16 @@
   <!-- XXX but they should be marked up -->
 
   <p>This specification describes the conformance criteria for user agents
-   (relevant to implementors) and documents (relevant to authors).
+   (relevant to implementors) and documents (relevant to authors and
+   authoring tool implementors).
 
-  <p>Conformance requirements phrased as requirements on elements,
-   attributes, methods or objects are conformance requirements on user
-   agents.
+  <p class="note">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>
+  <!--XXX quite possible that
+  this is stated twice. check for whether this is a dupe. -->
 
   <p>User agents fall into several (overlapping) categories with different
    conformance requirements.
@@ -1463,6 +1468,13 @@ and suggestions on this to the list, btw).
 
   </dl>
 
+  <p>Some conformance requirements are phrased as requirements on elements,
+   attributes, methods or objects. Such requirements fall into two
+   categories; those describing content model restrictions, and those
+   describing implementatino behaviour. The former category of requirements
+   are requirements on documents and authoring tools. The second category are
+   requirements on user agents.
+
   <p>Conformance requirements phrased as algorithms or specific steps may be
    implemented in any manner, so long as the end result is equivalent. (In
    particular, the algorithms defined in this specification are intended to
@@ -1473,14 +1485,6 @@ and suggestions on this to the list, btw).
    service attacks, to guard against running out of memory, or to work around
    platform-specific limitations.
 
-  <p class="note">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>
-  <!--XXX quite possible that
-  this is stated twice. check for whether this is a dupe. -->
-
   <p>For compatibility with existing content and prior specifications, this
    specification describes two authoring formats: one based on XML (referred
    to as <dfn id="xhtml5" title="XHTML">XHTML5</dfn>), and one using a <a

diff --git a/source b/source
@@ -363,11 +363,15 @@
 
   <p>This specification describes the conformance criteria for user
   agents (relevant to implementors) and documents (relevant to
-  authors).</p>
+  authors and authoring tool implementors).</p>
 
-  <p>Conformance requirements phrased as requirements on elements,
-  attributes, methods or objects are conformance requirements on user
-  agents.</p>
+  <p class="note">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> <!--XXX quite possible that
+  this is stated twice. check for whether this is a dupe. -->
 
   <p>User agents fall into several (overlapping) categories with
   different conformance requirements.</p>
@@ -540,6 +544,13 @@ and suggestions on this to the list, btw).
 
   </dl>
 
+  <p>Some conformance requirements are phrased as requirements on
+  elements, attributes, methods or objects. Such requirements fall
+  into two categories; those describing content model restrictions,
+  and those describing implementatino behaviour. The former category
+  of requirements are requirements on documents and authoring
+  tools. The second category are requirements on user agents.</p>
+
   <p>Conformance requirements phrased as algorithms or specific steps
   may be implemented in any manner, so long as the end result is
   equivalent. (In particular, the algorithms defined in this
@@ -551,14 +562,6 @@ and suggestions on this to the list, btw).
   e.g. to prevent denial of service attacks, to guard against running
   out of memory, or to work around platform-specific limitations.</p>
 
-  <p class="note">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> <!--XXX quite possible that
-  this is stated twice. check for whether this is a dupe. -->
-
   <p>For compatibility with existing content and prior specifications,
   this specification describes two authoring formats: one based on XML
   (referred to as <dfn id="xhtml5" title="XHTML">XHTML5</dfn>), and