hixie: Mention that microdata does not imply a relationship with the document's contents. (whatwg r3663)

hixie: Mention that microdata does not imply a relationship with the
document's contents. (whatwg r3663)

http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.2842&r2=1.2843&f=h
http://html5.org/tools/web-apps-tracker?from=3662&to=3663

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.2842
retrieving revision 1.2843
diff -u -d -r1.2842 -r1.2843
--- Overview.html 23 Aug 2009 08:42:42 -0000 1.2842
+++ Overview.html 23 Aug 2009 09:01:30 -0000 1.2843
@@ -716,11 +716,12 @@
   <ol>
    <li><a href="#introduction-1"><span class="secno">5.1 </span>Introduction</a>
     <ol>
-     <li><a href="#the-basic-syntax"><span class="secno">5.1.1 </span>The basic syntax</a></li>
-     <li><a href="#typed-items"><span class="secno">5.1.2 </span>Typed items</a></li>
-     <li><a href="#selecting-names-when-defining-vocabularies"><span class="secno">5.1.3 </span>Selecting names when defining vocabularies</a></li>
-     <li><a href="#predefined-vocabularies"><span class="secno">5.1.4 </span>Predefined vocabularies</a></li>
-     <li><a href="#using-the-microdata-dom-api"><span class="secno">5.1.5 </span>Using the microdata DOM API</a></ol></li>
+     <li><a href="#overview"><span class="secno">5.1.1 </span>Overview</a></li>
+     <li><a href="#the-basic-syntax"><span class="secno">5.1.2 </span>The basic syntax</a></li>
+     <li><a href="#typed-items"><span class="secno">5.1.3 </span>Typed items</a></li>
+     <li><a href="#selecting-names-when-defining-vocabularies"><span class="secno">5.1.4 </span>Selecting names when defining vocabularies</a></li>
+     <li><a href="#predefined-vocabularies"><span class="secno">5.1.5 </span>Predefined vocabularies</a></li>
+     <li><a href="#using-the-microdata-dom-api"><span class="secno">5.1.6 </span>Using the microdata DOM API</a></ol></li>
    <li><a href="#encoding-microdata"><span class="secno">5.2 </span>Encoding microdata</a>
     <ol>
      <li><a href="#the-microdata-model"><span class="secno">5.2.1 </span>The microdata model</a></li>
@@ -37565,12 +37566,14 @@
        <span property=bit>+44</span> (0) <span property=bit>1223 123 123</span>
      </span>
 
---><h3 id="introduction-1"><span class="secno">5.1 </span>Introduction</h3><h4 id="the-basic-syntax"><span class="secno">5.1.1 </span>The basic syntax</h4><p><i>This section is non-normative.</i><p>Sometimes, it is desirable to annotate content with specific
+--><h3 id="introduction-1"><span class="secno">5.1 </span>Introduction</h3><h4 id="overview"><span class="secno">5.1.1 </span>Overview</h4><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.<p>At a high level, microdata consists of a group of name-value
+  described in this section. Microdata allows nested groups of
+  name-value pairs to be added to documents, in parallel with the
+  existing content.<h4 id="the-basic-syntax"><span class="secno">5.1.2 </span>The basic syntax</h4><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-item"><a href="#items:-the-item-attribute">item</a></code>
@@ -37692,7 +37695,33 @@
  &lt;span itemprop="com.example.favorite-color com.example.favorite-fruit"&gt;orange&lt;/span&gt;
 &lt;/div&gt;</pre>
 
-  </div><h4 id="typed-items"><span class="secno">5.1.2 </span>Typed items</h4><p><i>This section is non-normative.</i><p>The examples in the previous section show how information could
+  </div><p>It's important to note that there is no relationship between the
+  microdata and the content of the document where the microdata is
+  marked up.<div class="example">
+
+   <p>There is no semantic difference, for instance, between the
+   following two examples:</p>
+
+   <pre>&lt;figure&gt;
+ &lt;img src="castle.jpeg"&gt;
+ &lt;legend&gt;&lt;span item&gt;&lt;span itemprop="net.example.name"&gt;The Castle&lt;/span&gt;&lt;/span&gt; (1986)&lt;/legend&gt;
+&lt;/figure&gt;</pre>
+
+   <pre>&lt;span item&gt;&lt;meta itemprop="net.example.name" content="The Castle"&gt;&lt;/span&gt;
+&lt;figure&gt;
+ &lt;img src="castle.jpeg"&gt;
+ &lt;legend&gt;The Castle (1986)&lt;/legend&gt;
+&lt;/figure&gt;</pre>
+
+   <p>Both have a figure with a caption, and both, completely
+   unrelated to the figure, have an item with a name-value pair with
+   the name "net.example.name" and the value "The Castle". The only
+   difference is that if the user drags the caption out of the
+   document, in the former case, the item will be included in the
+   drag-and-drop data. In neither case is the image in any way
+   associated with the item.</p>
+
+  </div><h4 id="typed-items"><span class="secno">5.1.3 </span>Typed items</h4><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
@@ -37757,7 +37786,7 @@
       <td>white
      <tr><td>org.example.img
       <td>.../hedral.jpeg
-   </table></div><h4 id="selecting-names-when-defining-vocabularies"><span class="secno">5.1.3 </span>Selecting names when defining vocabularies</h4><p><i>This section is non-normative.</i><p>Using microdata means using a vocabulary. For some purposes, an
+   </table></div><h4 id="selecting-names-when-defining-vocabularies"><span class="secno">5.1.4 </span>Selecting names when defining vocabularies</h4><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
@@ -37774,7 +37803,7 @@
    could select identifiers of the form "com.example.jon.name" and
    "com.example.adam.name" respectively.</p>
 
-  </div><h4 id="predefined-vocabularies"><span class="secno">5.1.4 </span>Predefined vocabularies</h4><p><i>This section is non-normative.</i><p>To make the most common tasks simpler, certain vocabularies have
+  </div><h4 id="predefined-vocabularies"><span class="secno">5.1.5 </span>Predefined vocabularies</h4><p><i>This section is non-normative.</i><p>To make the most common tasks simpler, certain vocabularies have
   been predefined. These use short names for types and properties.<div class="example">
 
    <p>For example, the <a href="#md-vcard" title="md-vcard">vCard</a> vocabulary
@@ -37794,7 +37823,7 @@
 N:Washington;George;;;
 END:VCARD</pre>
 
-  </div><h4 id="using-the-microdata-dom-api"><span class="secno">5.1.5 </span>Using the microdata DOM API</h4><p><i>This section is non-normative.</i><p>The microdata becomes even more useful when scripts can use it to
+  </div><h4 id="using-the-microdata-dom-api"><span class="secno">5.1.6 </span>Using the microdata DOM API</h4><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

Received on Sunday, 23 August 2009 09:02:29 UTC