hixie: This seems to be a common mistake, so let's call it out. (whatwg r6419)

hixie: This seems to be a common mistake, so let's call it out. (whatwg
r6419)

http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.5123&r2=1.5124&f=h
http://html5.org/tools/web-apps-tracker?from=6418&to=6419

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.5123
retrieving revision 1.5124
diff -u -d -r1.5123 -r1.5124
--- Overview.html 11 Aug 2011 20:22:56 -0000 1.5123
+++ Overview.html 11 Aug 2011 20:40:43 -0000 1.5124
@@ -1584,7 +1584,39 @@
   First, it should be read cover-to-cover, multiple times. Then, it
   should be read backwards at least once. Then it should be read by
   picking random sections from the contents list and following all the
-  cross-references.<h4 id="typographic-conventions"><span class="secno">1.7.2 </span>Typographic conventions</h4><p>This is a definition, requirement, or explanation.<p class="note">This is a note.<p class="example">This is an example.<p class="XXX">This is an open issue.<p class="warning">This is a warning.<pre class="idl extract">interface <dfn title="">Example</dfn> {
+  cross-references.<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.<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><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.7.2 </span>Typographic conventions</h4><p>This is a definition, requirement, or explanation.<p class="note">This is a note.<p class="example">This is an example.<p class="XXX">This is an open issue.<p class="warning">This is a warning.<pre class="idl extract">interface <dfn title="">Example</dfn> {
   // this is an IDL definition
 };</pre><dl class="domintro"><dt><var title="">variable</var> = <var title="">object</var> . <code title="">method</code>( [ <var title="">optionalArgument</var> ] )</dt>

Received on Thursday, 11 August 2011 20:40:55 UTC