[html5] r6419 - [e] (0) This seems to be a common mistake, so let's call it out. Fixing http://w [...]

[whatwg at whatwg.org]

Author: ianh
Date: 2011-08-11 13:40:29 -0700 (Thu, 11 Aug 2011)
New Revision: 6419

Modified:
   complete.html
   index
   source
Log:
[e] (0) This seems to be a common mistake, so let's call it out.
Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=12141

Modified: complete.html
===================================================================
--- complete.html	2011-08-11 20:22:42 UTC (rev 6418)
+++ complete.html	2011-08-11 20:40:29 UTC (rev 6419)
@@ -1952,8 +1952,48 @@
   picking random sections from the contents list and following all the
   cross-references.</p>
 
+  <p>As described in the conformance requirements section below, this
+  specification describes conformance criteria for a variety of
+  conformance classes. In particular, there are conformance
+  requirements that apply to <em>producers</em>, for example authors
+  and the documents they create, and there are conformance
+  requirements that apply to <em>consumers</em>, for example Web
+  browsers. They can be distinguished by what they are requiring: a
+  requirement on a producer states what is allowed, while a
+  requirement on a consumer states how software is to act.</p>
 
+  <div class=example>
 
+   <p>For example, "the <code title="">foo</code> attribute's value
+   must be a <a href=#valid-integer>valid integer</a>" is a requirement on
+   producers, as it lays out the allowed values; in contrast, the
+   requirement "the <code title="">foo</code> attribute's value must
+   be parsed using the <a href=#rules-for-parsing-integers>rules for parsing integers</a>" is a
+   requirement on consumers, as it describes how to process the
+   content.</p>
+
+  </div>
+
+  <p><strong>Requirements on producers have no bearing whatsoever on
+  consumers.</strong></p>
+
+  <div class=example>
+
+   <p>Continuing the above example, a requirement stating that a
+   particular attribute's value is constrained to being a <a href=#valid-integer>valid
+   integer</a> emphatically does <em>not</em> imply anything about
+   the requirements on consumers. It might be that the consumers are
+   in fact required to treat the attribute as an opaque string,
+   completely unaffected by whether the value conforms to the
+   requirements or not. It might be (as in the previous example) that
+   the consumers are required to parse the value using specific rules
+   that define how invalid (non-numeric in this case) values are to be
+   processed.</p>
+
+  </div>
+
+
+
   <h4 id=typographic-conventions><span class=secno>1.8.2 </span>Typographic conventions</h4>
 
   <p>This is a definition, requirement, or explanation.</p>

Modified: index
===================================================================
--- index	2011-08-11 20:22:42 UTC (rev 6418)
+++ index	2011-08-11 20:40:29 UTC (rev 6419)
@@ -1849,8 +1849,48 @@
   picking random sections from the contents list and following all the
   cross-references.</p>
 
+  <p>As described in the conformance requirements section below, this
+  specification describes conformance criteria for a variety of
+  conformance classes. In particular, there are conformance
+  requirements that apply to <em>producers</em>, for example authors
+  and the documents they create, and there are conformance
+  requirements that apply to <em>consumers</em>, for example Web
+  browsers. They can be distinguished by what they are requiring: a
+  requirement on a producer states what is allowed, while a
+  requirement on a consumer states how software is to act.</p>
 
+  <div class=example>
 
+   <p>For example, "the <code title="">foo</code> attribute's value
+   must be a <a href=#valid-integer>valid integer</a>" is a requirement on
+   producers, as it lays out the allowed values; in contrast, the
+   requirement "the <code title="">foo</code> attribute's value must
+   be parsed using the <a href=#rules-for-parsing-integers>rules for parsing integers</a>" is a
+   requirement on consumers, as it describes how to process the
+   content.</p>
+
+  </div>
+
+  <p><strong>Requirements on producers have no bearing whatsoever on
+  consumers.</strong></p>
+
+  <div class=example>
+
+   <p>Continuing the above example, a requirement stating that a
+   particular attribute's value is constrained to being a <a href=#valid-integer>valid
+   integer</a> emphatically does <em>not</em> imply anything about
+   the requirements on consumers. It might be that the consumers are
+   in fact required to treat the attribute as an opaque string,
+   completely unaffected by whether the value conforms to the
+   requirements or not. It might be (as in the previous example) that
+   the consumers are required to parse the value using specific rules
+   that define how invalid (non-numeric in this case) values are to be
+   processed.</p>
+
+  </div>
+
+
+
   <h4 id=typographic-conventions><span class=secno>1.8.2 </span>Typographic conventions</h4>
 
   <p>This is a definition, requirement, or explanation.</p>

Modified: source
===================================================================
--- source	2011-08-11 20:22:42 UTC (rev 6418)
+++ source	2011-08-11 20:40:29 UTC (rev 6419)
@@ -713,8 +713,48 @@
   picking random sections from the contents list and following all the
   cross-references.</p>
 
+  <p>As described in the conformance requirements section below, this
+  specification describes conformance criteria for a variety of
+  conformance classes. In particular, there are conformance
+  requirements that apply to <em>producers</em>, for example authors
+  and the documents they create, and there are conformance
+  requirements that apply to <em>consumers</em>, for example Web
+  browsers. They can be distinguished by what they are requiring: a
+  requirement on a producer states what is allowed, while a
+  requirement on a consumer states how software is to act.</p>
 
+  <div class="example">
 
+   <p>For example, "the <code title="">foo</code> attribute's value
+   must be a <span>valid integer</span>" is a requirement on
+   producers, as it lays out the allowed values; in contrast, the
+   requirement "the <code title="">foo</code> attribute's value must
+   be parsed using the <span>rules for parsing integers</span>" is a
+   requirement on consumers, as it describes how to process the
+   content.</p>
+
+  </div>
+
+  <p><strong>Requirements on producers have no bearing whatsoever on
+  consumers.</strong></p>
+
+  <div class="example">
+
+   <p>Continuing the above example, a requirement stating that a
+   particular attribute's value is constrained to being a <span>valid
+   integer</span> emphatically does <em>not</em> imply anything about
+   the requirements on consumers. It might be that the consumers are
+   in fact required to treat the attribute as an opaque string,
+   completely unaffected by whether the value conforms to the
+   requirements or not. It might be (as in the previous example) that
+   the consumers are required to parse the value using specific rules
+   that define how invalid (non-numeric in this case) values are to be
+   processed.</p>
+
+  </div>
+
+
+
   <h4>Typographic conventions</h4>
 
   <p>This is a definition, requirement, or explanation.</p>