[e] (0) Explain some of the conformance terminology better.

Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=13536 git-svn-id: http://svn.whatwg.org/webapps@6473 340c8d12-0b0e-0410-8428-c7bf67bfef74
whatwg · Aug 16, 2011 · 12430c4 · 12430c4
1 parent 41d04d9
commit 12430c4
Show file tree

Hide file tree

Showing 3 changed files with 63 additions and 0 deletions.
diff --git a/complete.html b/complete.html
@@ -3373,6 +3373,27 @@ <h3 id=conformance-requirements><span class=secno>2.2 </span>Conformance require
   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

diff --git a/index b/index
@@ -3270,6 +3270,27 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
   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

diff --git a/source b/source
@@ -2237,6 +2237,27 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
   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