microdata; hixie: Tweak the conformance section a bit so we can have a 'conformance classes' subsection. (whatwg r5922)

microdata; hixie: Tweak the conformance section a bit so we can have a
'conformance classes' subsection. (whatwg r5922)

http://dev.w3.org/cvsweb/html5/md/Overview.html?r1=1.114&r2=1.115&f=h
http://html5.org/tools/web-apps-tracker?from=5921&to=5922

===================================================================
RCS file: /sources/public/html5/md/Overview.html,v
retrieving revision 1.114
retrieving revision 1.115
diff -u -d -r1.114 -r1.115
--- Overview.html 28 Feb 2011 22:16:36 -0000 1.114
+++ Overview.html 1 Mar 2011 22:57:38 -0000 1.115
@@ -344,7 +344,7 @@
 
    <h1>HTML Microdata</h1>
    <h2 class="no-num no-toc" id="generatedID"></h2>
-   <h2 class="no-num no-toc" id="editor-s-draft-28-february-2011">Editor's Draft 28 February 2011</h2>
+   <h2 class="no-num no-toc" id="editor-s-draft-1-march-2011">Editor's Draft 1 March 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>
@@ -474,7 +474,7 @@
   Group</a> is the W3C working group responsible for this
   specification's progress along the W3C Recommendation
   track.
-  This specification is the 28 February 2011 Editor's Draft.
+  This specification is the 1 March 2011 Editor's Draft.
   </p><!-- UNDER NO CIRCUMSTANCES IS THE PRECEDING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><!-- relationship to other work (required) --><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 --><!--YYY BOILERPLATE middle-w3c-html-module-status--><!-- required patent boilerplate --><p>This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5
@@ -618,36 +618,13 @@
   NOT",--> "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and
   "OPTIONAL" in the normative parts of this document are to be
   interpreted as described in RFC2119. For readability, these words do
-  not appear in all uppercase letters in this specification. <a href="#refsRFC2119">[RFC2119]</a><p class="impl">Requirements phrased in the imperative as part of
-  algorithms (such as "strip any leading space characters" or "return
-  false and abort these steps") are to be interpreted with the meaning
-  of the key word ("must", "should", "may", etc) used in introducing
-  the algorithm.<p>This specification describes the conformance criteria for <span class="impl">user agents (relevant to implementors) and</span>
-  documents<span class="impl"> (relevant to authors and authoring tool
-  implementors)</span>.<p><dfn id="conforming-documents">Conforming documents</dfn> are those that comply with all
-  the conformance criteria for documents. For readability, some of
-  these conformance requirements are phrased as conformance
-  requirements on authors; such requirements are implicitly
-  requirements on documents: by definition, all documents are assumed
-  to have had an author. (In some cases, that author may itself be a
-  user agent &mdash; such user agents are subject to additional rules,
-  as explained below.)<p class="example">For example, if a requirement states that
-  "authors must not use the <code title="">foobar</code> element", it
-  would imply that documents are not allowed to contain elements named
-  <code title="">foobar</code>.<div class="impl">
-
+  not appear in all uppercase letters in this specification. <a href="#refsRFC2119">[RFC2119]</a><div class="impl">
 
-  <p>Some conformance requirements are phrased as requirements on
-  elements, attributes, methods or objects. Such requirements fall
-  into two categories: those describing content model restrictions,
-  and those describing implementation behavior. Those in the former
-  category are requirements on documents and authoring tools. Those in
-  the second category are requirements on user agents. Similarly, some
-  conformance requirements are phrased as requirements on authors;
-  such requirements are to be interpreted as conformance requirements
-  on the documents that authors produce. (In other words, this
-  specification does not distinguish between conformance criteria on
-  authors and conformance criteria on documents.)</p>
+  <p>Requirements phrased in the imperative as part of algorithms
+  (such as "strip any leading space characters" or "return false and
+  abort these steps") are to be interpreted with the meaning of the
+  key word ("must", "should", "may", etc) used in introducing the
+  algorithm.</p>
 
   <p>Conformance requirements phrased as algorithms or specific steps
   may be implemented in any manner, so long as the end result is
@@ -655,11 +632,6 @@
   specification are intended to be easy to follow, and not intended to
   be performant.)</p>
 
-  <p id="hardwareLimitations">User agents may impose
-  implementation-specific limits on otherwise unconstrained inputs,
-  e.g. to prevent denial of service attacks, to guard against running
-  out of memory, or to work around platform-specific limitations.</p>
-
   </div><h3 id="htmlpropertiescollection-0"><span class="secno">1.2 </span>HTMLPropertiesCollection</h3><p>The <code><a href="#htmlpropertiescollection">HTMLPropertiesCollection</a></code> interface represents a
   <a href="#collections" title="collections">collection</a> of elements that add
   name-value pairs to a particular <a href="#concept-item" title="concept-item">item</a> in the <span>microdata</span>

Received on Tuesday, 1 March 2011 22:59:44 UTC