[html5] r6473 - [e] (0) Explain some of the conformance terminology better. Fixing http://www.w3 [...]

[whatwg at whatwg.org]

Author: ianh
Date: 2011-08-15 21:40:15 -0700 (Mon, 15 Aug 2011)
New Revision: 6473

Modified:
   complete.html
   index
   source
Log:
[e] (0) Explain some of the conformance terminology better.
Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=13536

Modified: complete.html
===================================================================
--- complete.html	2011-08-16 04:32:54 UTC (rev 6472)
+++ complete.html	2011-08-16 04:40:15 UTC (rev 6473)
@@ -3373,6 +3373,27 @@
   key word ("must", "should", "may", etc) used in introducing the
   algorithm.</p>
 
+  <div class=example>
+
+   <p>For example, were the spec to say:</p>
+
+   <pre>To eat a kiwi, the user must:
+1. Peel the kiwi.
+2. Eat the kiwi flesh.</pre>
+
+   <p>...it would be equivalent to the following:</p>
+
+   <pre>To eat a kiwi:
+1. The user must peel the kiwi.
+2. The user must eat the kiwi flesh.</pre>
+
+   <p>Here the key word is "must".</p>
+
+   <p>The former (imperative) style is generally preferred in this
+   specification for stylistic reasons.</p>
+
+  </div>
+
   <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

Modified: index
===================================================================
--- index	2011-08-16 04:32:54 UTC (rev 6472)
+++ index	2011-08-16 04:40:15 UTC (rev 6473)
@@ -3270,6 +3270,27 @@
   key word ("must", "should", "may", etc) used in introducing the
   algorithm.</p>
 
+  <div class=example>
+
+   <p>For example, were the spec to say:</p>
+
+   <pre>To eat a kiwi, the user must:
+1. Peel the kiwi.
+2. Eat the kiwi flesh.</pre>
+
+   <p>...it would be equivalent to the following:</p>
+
+   <pre>To eat a kiwi:
+1. The user must peel the kiwi.
+2. The user must eat the kiwi flesh.</pre>
+
+   <p>Here the key word is "must".</p>
+
+   <p>The former (imperative) style is generally preferred in this
+   specification for stylistic reasons.</p>
+
+  </div>
+
   <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

Modified: source
===================================================================
--- source	2011-08-16 04:32:54 UTC (rev 6472)
+++ source	2011-08-16 04:40:15 UTC (rev 6473)
@@ -2237,6 +2237,27 @@
   key word ("must", "should", "may", etc) used in introducing the
   algorithm.</p>
 
+  <div class="example">
+
+   <p>For example, were the spec to say:</p>
+
+   <pre>To eat a kiwi, the user must:
+1. Peel the kiwi.
+2. Eat the kiwi flesh.</pre>
+
+   <p>...it would be equivalent to the following:</p>
+
+   <pre>To eat a kiwi:
+1. The user must peel the kiwi.
+2. The user must eat the kiwi flesh.</pre>
+
+   <p>Here the key word is "must".</p>
+
+   <p>The former (imperative) style is generally preferred in this
+   specification for stylistic reasons.</p>
+
+  </div>
+
   <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