- From: poot <cvsmail@w3.org>
- Date: Tue, 16 Aug 2011 00:41:13 -0400
- To: public-html-diffs@w3.org
microdata; hixie: Explain some of the conformance terminology better.
(whatwg r6473)
http://dev.w3.org/cvsweb/html5/md/Overview.html?r1=1.157&r2=1.158&f=h
http://html5.org/tools/web-apps-tracker?from=6472&to=6473
===================================================================
RCS file: /sources/public/html5/md/Overview.html,v
retrieving revision 1.157
retrieving revision 1.158
diff -u -d -r1.157 -r1.158
--- Overview.html 15 Aug 2011 20:30:47 -0000 1.157
+++ Overview.html 16 Aug 2011 04:40:52 -0000 1.158
@@ -321,7 +321,7 @@
<h1>HTML Microdata</h1>
<h2 class="no-num no-toc" id="generatedID"></h2>
- <h2 class="no-num no-toc" id="editor-s-draft-15-august-2011">Editor's Draft 15 August 2011</h2>
+ <h2 class="no-num no-toc" id="editor-s-draft-16-august-2011">Editor's Draft 16 August 2011</h2>
<dl><dt>Latest Published Version:</dt>
<dd><a href="http://www.w3.org/TR/microdata/">http://www.w3.org/TR/microdata/</a></dd>
<dt>Latest Editor's Draft:</dt>
@@ -455,7 +455,7 @@
Group</a> is the W3C working group responsible for this
specification's progress along the W3C Recommendation
track.
- This specification is the 15 August 2011 Editor's Draft.
+ This specification is the 16 August 2011 Editor's Draft.
</p><!-- UNDER NO CIRCUMSTANCES IS THE PRECEDING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><p>Work on this specification is also done at the <a href="http://www.whatwg.org/">WHATWG</a>. The W3C HTML working group
actively pursues convergence with the WHATWG, as required by the <a href="http://www.w3.org/2007/03/HTML-WG-charter">W3C HTML working
group charter</a>.</p><!-- UNDER NO CIRCUMSTANCES IS THE FOLLOWING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><!-- UNDER NO CIRCUMSTANCES IS THE PRECEDING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><p>This specification is an extension to the HTML5 language. All
@@ -544,6 +544,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
Received on Tuesday, 16 August 2011 04:41:18 UTC