microdata; hixie: Let W3C deal with the registries. (whatwg r5470)

microdata; hixie: Let W3C deal with the registries. (whatwg r5470)

http://dev.w3.org/cvsweb/html5/md/Overview.html?r1=1.87&r2=1.88&f=h
http://html5.org/tools/web-apps-tracker?from=5469&to=5470

===================================================================
RCS file: /sources/public/html5/md/Overview.html,v
retrieving revision 1.87
retrieving revision 1.88
diff -u -d -r1.87 -r1.88
--- Overview.html 11 Aug 2010 03:50:03 -0000 1.87
+++ Overview.html 23 Sep 2010 17:45:07 -0000 1.88
@@ -311,7 +311,7 @@
 
    <h1>HTML Microdata</h1>
    <h2 class="no-num no-toc" id="generatedID"></h2>
-   <h2 class="no-num no-toc" id="editor-s-draft-11-august-2010">Editor's Draft 11 August 2010</h2>
+   <h2 class="no-num no-toc" id="editor-s-draft-23-september-2010">Editor's Draft 23 September 2010</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>
@@ -405,7 +405,7 @@
   Group</a> is the W3C working group responsible for this
   specification's progress along the W3C Recommendation
   track.
-  This specification is the 11 August 2010 Editor's Draft.
+  This specification is the 23 September 2010 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
@@ -543,7 +543,7 @@
   nodes</dfn>, which come up in the context of drag-and-drop
   interfaces.</p>
 
---><h3 id="conformance-requirements"><span class="secno">1.1 </span>Conformance requirements</h3><p class="XXX annotation"><b>Status: </b><i>Last call for comments</i><p>All diagrams, examples, and notes in this specification are
+--><h3 id="conformance-requirements"><span class="secno">1.1 </span>Conformance requirements</h3><p>All diagrams, examples, and notes in this specification are
   non-normative, as are all sections explicitly marked non-normative.
   Everything else in this specification is normative.<p>The key words "MUST", "MUST NOT", "REQUIRED", <!--"SHALL", "SHALL
   NOT",--> "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and
@@ -670,14 +670,14 @@
   values obtained from the <code title="dom-itemValue"><a href="#dom-itemvalue">itemValue</a></code> DOM property of each of the
   elements represented by the object, in <a href="#tree-order">tree order</a>.</p>
 
-  </div><h2 id="introduction"><span class="secno">2 </span>Introduction</h2><p class="XXX annotation"><b>Status: </b><i>Last call for comments</i><h3 id="overview"><span class="secno">2.1 </span>Overview</h3><p class="XXX annotation"><b>Status: </b><i>Last call for comments</i><p><i>This section is non-normative.</i><p>Sometimes, it is desirable to annotate content with specific
+  </div><h2 id="introduction"><span class="secno">2 </span>Introduction</h2><h3 id="overview"><span class="secno">2.1 </span>Overview</h3><p><i>This section is non-normative.</i><p>Sometimes, it is desirable to annotate content with specific
   machine-readable labels, e.g. to allow generic scripts to provide
   services that are customised to the page, or to enable content from
   a variety of cooperating authors to be processed by a single script
   in a consistent manner.<p>For this purpose, authors can use the microdata features
   described in this section. Microdata allows nested groups of
   name-value pairs to be added to documents, in parallel with the
-  existing content.<h3 id="the-basic-syntax"><span class="secno">2.2 </span>The basic syntax</h3><p class="XXX annotation"><b>Status: </b><i>Last call for comments</i><p><i>This section is non-normative.</i><p>At a high level, microdata consists of a group of name-value
+  existing content.<h3 id="the-basic-syntax"><span class="secno">2.2 </span>The basic syntax</h3><p><i>This section is non-normative.</i><p>At a high level, microdata consists of a group of name-value
   pairs. The groups are called <a href="#concept-item" title="concept-item">items</a>, and each name-value pair is a
   property. Items and properties are represented by regular
   elements.<p>To create an item, the <code title="attr-itemscope"><a href="#attr-itemscope">itemscope</a></code> attribute is used.<p>To add a property to an item, the <code title="attr-itemprop"><a href="#names:-the-itemprop-attribute">itemprop</a></code> attribute is used on one of
@@ -825,7 +825,7 @@
    drag-and-drop data. In neither case is the image in any way
    associated with the item.</p>
 
-  </div><h3 id="typed-items"><span class="secno">2.3 </span>Typed items</h3><p class="XXX annotation"><b>Status: </b><i>Last call for comments</i><p><i>This section is non-normative.</i><p>The examples in the previous section show how information could
+  </div><h3 id="typed-items"><span class="secno">2.3 </span>Typed items</h3><p><i>This section is non-normative.</i><p>The examples in the previous section show how information could
   be marked up on a page that doesn't expect its microdata to be
   re-used. Microdata is most useful, though, when it is used in
   contexts where other authors and readers are able to cooperate to
@@ -853,7 +853,7 @@
   given for an item with the type "http://census.example/person" might
   refer to the economic class of an individual, while a property named
   "class" given for an item with the type "http://example.com/school/teacher"
-  might refer to the classroom a teacher has been assigned.<h3 id="global-identifiers-for-items"><span class="secno">2.4 </span>Global identifiers for items</h3><p class="XXX annotation"><b>Status: </b><i>Last call for comments</i><p><i>This section is non-normative.</i><p>Sometimes, an <a href="#concept-item" title="concept-item">item</a> gives
+  might refer to the classroom a teacher has been assigned.<h3 id="global-identifiers-for-items"><span class="secno">2.4 </span>Global identifiers for items</h3><p><i>This section is non-normative.</i><p>Sometimes, an <a href="#concept-item" title="concept-item">item</a> gives
   information about a topic that has a global identifier. For example,
   books can be identified by their ISBN number.<p>Vocabularies (as identified by the <code title="attr-itemtype"><a href="#attr-itemtype">itemtype</a></code> attribute) can be designed
   such that <a href="#concept-item" title="concept-item">items</a> get associated
@@ -892,7 +892,7 @@
   leads to a situation where it is ambiguous whether the identifier,
   and thus the set of properties specified in the microdata,
   references the page or something else.</p>
-  --><h3 id="selecting-names-when-defining-vocabularies"><span class="secno">2.5 </span>Selecting names when defining vocabularies</h3><p class="XXX annotation"><b>Status: </b><i>Last call for comments</i><p><i>This section is non-normative.</i><p>Using microdata means using a vocabulary. For some purposes, an
+  --><h3 id="selecting-names-when-defining-vocabularies"><span class="secno">2.5 </span>Selecting names when defining vocabularies</h3><p><i>This section is non-normative.</i><p>Using microdata means using a vocabulary. For some purposes, an
   ad-hoc vocabulary is adequate. For others, a vocabulary will need to
   be designed. Where possible, authors are encouraged to re-use
   existing vocabularies, as this makes content re-use easier.<p>When designing new vocabularies, identifiers can be created
@@ -947,7 +947,7 @@
       <td>white
      <tr><td>img
       <td>.../hedral.jpeg
-   </table></div><h3 id="using-the-microdata-dom-api"><span class="secno">2.6 </span>Using the microdata DOM API</h3><p class="XXX annotation"><b>Status: </b><i>Last call for comments</i><p><i>This section is non-normative.</i><p>The microdata becomes even more useful when scripts can use it to
+   </table></div><h3 id="using-the-microdata-dom-api"><span class="secno">2.6 </span>Using the microdata DOM API</h3><p><i>This section is non-normative.</i><p>The microdata becomes even more useful when scripts can use it to
   expose information to the user, for example offering it in a form
   that can be used by other applications.<p>The <code title="dom-document-getItems"><a href="#dom-document-getitems">document.getItems(<var title="">typeNames</var>)</a></code> method provides access to the
   <a href="#top-level-microdata-items">top-level microdata items</a>. It returns a
@@ -1052,13 +1052,13 @@
    </ul><p>(The duplicate occurrence of "http://example.com/color" is not included
    in the list.)</p>
 
-  </div><h2 id="encoding-microdata"><span class="secno">3 </span>Encoding microdata</h2><p class="XXX annotation"><b>Status: </b><i>Last call for comments</i><p>The following attributes are added as <a href="#global-attributes">global
+  </div><h2 id="encoding-microdata"><span class="secno">3 </span>Encoding microdata</h2><p>The following attributes are added as <a href="#global-attributes">global
   attributes</a> to <a href="#html-elements">HTML elements</a>:<ul class="brief"><li><code title="attr-itemid"><a href="#attr-itemid">itemid</a></code></li>
    <li><code title="attr-itemprop"><a href="#names:-the-itemprop-attribute">itemprop</a></code></li>
    <li><code title="attr-itemref"><a href="#attr-itemref">itemref</a></code></li>
    <li><code title="attr-itemscope"><a href="#attr-itemscope">itemscope</a></code></li>
    <li><code title="attr-itemtype"><a href="#attr-itemtype">itemtype</a></code></li>
-  </ul><h3 id="the-microdata-model"><span class="secno">3.1 </span>The microdata model</h3><p class="XXX annotation"><b>Status: </b><i>Last call for comments</i><p>The microdata model consists of groups of name-value pairs known
+  </ul><h3 id="the-microdata-model"><span class="secno">3.1 </span>The microdata model</h3><p>The microdata model consists of groups of name-value pairs known
   as <a href="#concept-item" title="concept-item">items</a>.<p>Each group is known as an <a href="#concept-item" title="concept-item">item</a>. Each <a href="#concept-item" title="concept-item">item</a> can have an <a href="#item-type">item type</a>,
   a <a href="#global-identifier">global identifier</a> (if the <a href="#item-type">item type</a>
   <a href="#support-global-identifiers-for-items" title="support global identifiers for items">supports global
@@ -1071,7 +1071,7 @@
   item">property</a> of a <a href="#typed-item">typed item</a>. The
   <dfn id="relevant-type">relevant type</dfn> for a <a href="#typed-item">typed item</a> is the <a href="#concept-item" title="concept-item">item</a>'s <a href="#item-type">item type</a>, if it has
   one, or else is the <a href="#relevant-type">relevant type</a> of the <a href="#concept-item" title="concept-item">item</a> for which it is a <a href="#the-properties-of-an-item" title="the
-  properties of an item">property</a>'s <a href="#concept-property-value" title="concept-property-value">value</a>.<h3 id="items"><span class="secno">3.2 </span>Items</h3><p class="XXX annotation"><b>Status: </b><i>Last call for comments</i><p>Every <a href="#html-elements" title="HTML elements">HTML element</a> may have an
+  properties of an item">property</a>'s <a href="#concept-property-value" title="concept-property-value">value</a>.<h3 id="items"><span class="secno">3.2 </span>Items</h3><p>Every <a href="#html-elements" title="HTML elements">HTML element</a> may have an
   <dfn id="attr-itemscope" title="attr-itemscope"><code>itemscope</code></dfn> attribute
   specified. The <code title="attr-itemscope"><a href="#attr-itemscope">itemscope</a></code>
   attribute is a <a href="#boolean-attribute">boolean attribute</a>.<p>An element with the <code title="attr-itemscope"><a href="#attr-itemscope">itemscope</a></code>
@@ -1126,7 +1126,7 @@
   specified, must have a value that is an <a href="#unordered-set-of-unique-space-separated-tokens">unordered set of
   unique space-separated tokens</a> consisting of <a href="#concept-id" title="concept-ID">IDs</a> of elements in the same <a href="#home-subtree">home
   subtree</a>.<p>The <code title="attr-itemref"><a href="#attr-itemref">itemref</a></code> attribute must not
-  be specified on elements that do not have an <code title="attr-itemscope"><a href="#attr-itemscope">itemscope</a></code> attribute specified.<h3 id="names:-the-itemprop-attribute"><span class="secno">3.3 </span>Names: the <dfn title="attr-itemprop"><code>itemprop</code></dfn> attribute</h3><p class="XXX annotation"><b>Status: </b><i>Last call for comments</i><p>Every <a href="#html-elements" title="HTML elements">HTML element</a> may have an
+  be specified on elements that do not have an <code title="attr-itemscope"><a href="#attr-itemscope">itemscope</a></code> attribute specified.<h3 id="names:-the-itemprop-attribute"><span class="secno">3.3 </span>Names: the <dfn title="attr-itemprop"><code>itemprop</code></dfn> attribute</h3><p>Every <a href="#html-elements" title="HTML elements">HTML element</a> may have an
   <code title="attr-itemprop"><a href="#names:-the-itemprop-attribute">itemprop</a></code> attribute specified, if
   doing so <a href="#the-properties-of-an-item" title="the properties of an item">adds a
   property</a> to one or more <a href="#concept-item" title="concept-item">items</a> (as defined below).<p>The <code title="attr-itemprop"><a href="#names:-the-itemprop-attribute">itemprop</a></code> attribute, if
@@ -1206,7 +1206,7 @@
 &lt;/div&gt;
 </pre>
 
-  </div><h3 id="values"><span class="secno">3.4 </span>Values</h3><p class="XXX annotation"><b>Status: </b><i>Last call for comments</i><p>The <dfn id="concept-property-value" title="concept-property-value">property value</dfn> of a
+  </div><h3 id="values"><span class="secno">3.4 </span>Values</h3><p>The <dfn id="concept-property-value" title="concept-property-value">property value</dfn> of a
   name-value pair added by an element with an <code title="attr-itemprop"><a href="#names:-the-itemprop-attribute">itemprop</a></code> attribute depends on the
   element, as follows:<dl><dt>If the element also has an <code title="attr-itemscope"><a href="#attr-itemscope">itemscope</a></code> attribute</dt>
 
@@ -1273,7 +1273,7 @@
   element</a>.<p>If a property's <a href="#concept-property-value" title="concept-property-value">value</a>
   represents a <a href="#concept-date" title="concept-date">date</a>, <a href="#concept-time" title="concept-time">time</a>, or <a href="#concept-datetime" title="concept-datetime">global date and time</a>, the property
   must be specified using the <code title="attr-time-datetime">datetime</code> attribute of a
-  <code>time</code> element.<h3 id="associating-names-with-items"><span class="secno">3.5 </span>Associating names with items</h3><p class="XXX annotation"><b>Status: </b><i>Last call for comments</i><p>To find <dfn id="the-properties-of-an-item">the properties of an item</dfn> defined by the
+  <code>time</code> element.<h3 id="associating-names-with-items"><span class="secno">3.5 </span>Associating names with items</h3><p>To find <dfn id="the-properties-of-an-item">the properties of an item</dfn> defined by the
   element <var title="">root</var>, the user agent must try to
   <a href="#crawl-the-properties">crawl the properties</a> of the element <var title="">root</var>, with an empty list as the value of <var title="">memory</var>: if this fails, then <a href="#the-properties-of-an-item" title="the
   properties of an item">the properties of the item</a> defined by
@@ -1400,7 +1400,7 @@
     <dd>The mailbox.
     <dt>license
     <dd><code title="">http://www.opensource.org/licenses/mit-license.php</code>
-   </dl></div><h2 id="microdata-dom-api"><span class="secno">4 </span>Microdata DOM API</h2><p class="XXX annotation"><b>Status: </b><i>Last call for comments</i><pre class="idl">[Supplemental] interface <a href="#htmldocument">HTMLDocument</a> { <!--WARNING: ALSO DUPLICATED IN HTMLDocument SECTION-->
+   </dl></div><h2 id="microdata-dom-api"><span class="secno">4 </span>Microdata DOM API</h2><pre class="idl">[Supplemental] interface <a href="#htmldocument">HTMLDocument</a> { <!--WARNING: ALSO DUPLICATED IN HTMLDocument SECTION-->
   NodeList <a href="#dom-document-getitems" title="dom-document-getItems">getItems</a>(in optional DOMString typeNames); // <span>microdata</span>
 };
 
@@ -1601,9 +1601,9 @@
    </li>
   </ol></div><div class="impl">
 
-  <h2 id="converting-html-to-other-formats"><span class="secno">5 </span>Converting HTML to other formats</h2><p class="XXX annotation"><b>Status: </b><i>Last call for comments</i></p>
+  <h2 id="converting-html-to-other-formats"><span class="secno">5 </span>Converting HTML to other formats</h2>
 
-  <h3 id="json"><span class="secno">5.1 </span>JSON</h3><p class="XXX annotation"><b>Status: </b><i>Last call for comments</i></p>
+  <h3 id="json"><span class="secno">5.1 </span>JSON</h3>
 
   <p>Given a list of nodes <var title="">nodes</var> in a
   <code>Document</code>, a user agent must run the following algorithm
@@ -1675,7 +1675,7 @@
 
    <li><p>Return <var title="">result</var>.</li>
 
-  </ol><h3 id="rdf"><span class="secno">5.2 </span>RDF</h3><p class="XXX annotation"><b>Status: </b><i>Last call for comments</i></p>
+  </ol><h3 id="rdf"><span class="secno">5.2 </span>RDF</h3>
 
   <p>To <dfn id="extracting-rdf" title="extracting rdf">convert a <code>Document</code> to
   RDF</dfn>, a user agent must run the following algorithm:</p>
@@ -1984,7 +1984,7 @@
 
    <li><p>Return <var title="">subject</var>.</li>
 
-  </ol><h4 id="examples"><span class="secno">5.2.1 </span>Examples</h4><p class="XXX annotation"><b>Status: </b><i>Last call for comments</i></p>
+  </ol><h4 id="examples"><span class="secno">5.2.1 </span>Examples</h4>
 
   <p><i>This section is non-normative.</i></p>
 
@@ -2132,10 +2132,10 @@
    <dt>Author:</dt>
    <dd>Ian Hickson &lt;ian@hixie.ch&gt;</dd>
    <dt>Change controller:</dt>
-   <dd>WHATWG</dd>
+   <dd>W3C</dd>
   </dl><p>Fragment identifiers used with
   <code><a href="#application-microdata-json">application/microdata+json</a></code> resources have the same
-  semantics as when used with <code>application/json</code>. <a href="#refsJSON">[JSON]</a><h2 class="no-num" id="references">References</h2><p class="XXX annotation"><b>Status: </b><i>Implemented and widely deployed</i></p><!--REFS--><p>All references are normative unless marked "Non-normative".</p><!-- Dates are only included for standards older than the Web, because the newer ones keep changing. --><dl><dt id="refsHTML5">[HTML5]</dt>
+  semantics as when used with <code>application/json</code>. <a href="#refsJSON">[JSON]</a><h2 class="no-num" id="references">References</h2><!--REFS--><p>All references are normative unless marked "Non-normative".</p><!-- Dates are only included for standards older than the Web, because the newer ones keep changing. --><dl><dt id="refsHTML5">[HTML5]</dt>
    <dd>
 <!--YYYEND microdata-->
    (Non-normative)
@@ -2164,5 +2164,5 @@
    <dd><cite><a href="http://dev.w3.org/2006/webapi/WebIDL/">Web
    IDL</a></cite>, C. McCormack. W3C.</dd>
 
-  </dl><h2 class="no-num" id="acknowledgements">Acknowledgements</h2><p class="XXX annotation"><b>Status: </b><i>Last call for comments</i><p>For a full list of acknowledgements, please see the HTML5
+  </dl><h2 class="no-num" id="acknowledgements">Acknowledgements</h2><p>For a full list of acknowledgements, please see the HTML5
   specification. <a href="#refsHTML5">[HTML5]</a>

Received on Thursday, 23 September 2010 17:46:17 UTC