microdata; hixie: Drop <time> and replace it with <data>. Drop the Atom conversion section entirely. Convert a bunch of examples that used to use <time pubdate> to using schema.org, to show how to annotate publication dates and the like in a machine-processable way. (whatwg r6783)

microdata; hixie: Drop <time> and replace it with <data>. Drop the Atom
conversion section entirely. Convert a bunch of examples that used to
use <time pubdate> to using schema.org, to show how to annotate
publication dates and the like in a machine-processable way. (whatwg
r6783)

http://dev.w3.org/cvsweb/html5/md/Overview.html?r1=1.172&r2=1.173&f=h
http://html5.org/tools/web-apps-tracker?from=6782&to=6783

===================================================================
RCS file: /sources/public/html5/md/Overview.html,v
retrieving revision 1.172
retrieving revision 1.173
diff -u -d -r1.172 -r1.173
--- Overview.html 25 Oct 2011 19:23:17 -0000 1.172
+++ Overview.html 29 Oct 2011 05:43:25 -0000 1.173
@@ -320,7 +320,7 @@
 
    <h1>HTML Microdata</h1>
    <h2 class="no-num no-toc" id="generatedID"></h2>
-   <h2 class="no-num no-toc" id="editor-s-draft-25-october-2011">Editor's Draft 25 October 2011</h2>
+   <h2 class="no-num no-toc" id="editor-s-draft-29-october-2011">Editor's Draft 29 October 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>
@@ -454,7 +454,7 @@
   Group</a> is the W3C working group responsible for this
   specification's progress along the W3C Recommendation
   track.
-  This specification is the 25 October 2011 Editor's Draft.
+  This specification is the 29 October 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
@@ -698,14 +698,16 @@
  &lt;img itemprop="image" src="google-logo.png" alt="Google"&gt;
 &lt;/div&gt;</pre>
 
-  </div><p>When a string value is a date, time, or both a date and a time,
-  it is expressed using the <code>time</code> element and its <code title="attr-time-datetime">datetime</code> attribute.<div class="example">
+  </div><p>When a string value is in some machine-readable format unsuitable
+  for human consumption, it is expressed using the <code title="attr-data-value">value</code> attribute of the
+  <code>data</code> element, with the human-readable version given in
+  the element's contents.<div class="example">
 
-   <p>In this example, the item has one property,
-   "birthday", whose value is a date:</p>
+   <p>In this example, the item has one property, "birthday", whose
+   value is a date:</p>
 
    <pre>&lt;div itemscope&gt;
- I was born on &lt;time itemprop="birthday" datetime="2009-05-10"&gt;May 10th 2009&lt;/time&gt;.
+ I was born on &lt;data itemprop="birthday" value="2009-05-10"&gt;May 10th 2009&lt;/data&gt;.
 &lt;/div&gt;</pre>
 
   </div><p>Properties can also themselves be groups of name-value pairs, by
@@ -863,7 +865,7 @@
  &lt;dt&gt;Author
  &lt;dd itemprop="author"&gt;Peter F. Hamilton
  &lt;dt&gt;Publication date
- &lt;dd&gt;&lt;time itemprop="pubdate" datetime="1996-01-26"&gt;26 January 1996&lt;/time&gt;
+ &lt;dd&gt;&lt;data itemprop="pubdate" value="1996-01-26"&gt;26 January 1996&lt;/data&gt;
 &lt;/dl&gt;</pre>
 
    <p>The "<code title="">http://vocab.example.net/book</code>"
@@ -1323,9 +1325,10 @@
    url">resolving</a> it results in an error.</dd>
 
 
-   <dt>If the element is a <code>time</code> element with a <code title="attr-time-datetime">datetime</code> attribute</dt>
+   <dt>If the element is a <code>data</code> element</dt>
 
-   <dd><p>The value is the value of the element's <code title="attr-time-datetime">datetime</code> attribute.</dd>
+   <dd><p>The value is the value of the element's <code title="attr-data-value">value</code> attribute, if it has one, or
+   the empty string otherwise.</dd>
 
 
    <dt>Otherwise</dt>
@@ -1340,22 +1343,19 @@
   <code>video</code> elements.<p>If a property's <a href="#concept-property-value" title="concept-property-value">value</a>, as defined by the
   property's definition, is an <a href="#absolute-url">absolute URL</a>, the property
   must be specified using a <a href="#url-property-elements" title="URL property elements">URL
-  property 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>, as defined by
-  the property's definition, the property must be specified using the
-  <code title="attr-time-datetime">datetime</code> attribute of a
-  <code>time</code> element.<p class="note">These requirements do not apply just because a
-  property value happens to match the syntax for a URL or date/time
-  construct. They only apply if the property is explicitly defined as
-  taking such a value.<p class="example">For example, a book about the first moon landing
-  could be called "1969-07-20". A "title" property from a vocabulary
-  that defines a title as being a string would not expect the title to
-  be given in a <code>time</code> element, even though it looks like a
-  date. On the other hand, if there was a (rather narrowly scoped!)
-  vocaburaly for "books whose titles imply dates" which had a "title"
-  property defined to take a date, then the property <em>would</em>
-  expect the title to be given in a <code>time</code> element, because
-  of the requirement above.<div class="impl"> 
+  property element</a>.<p class="note">These requirements do not apply just because a
+  property value happens to match the syntax for a URL. They only
+  apply if the property is explicitly defined as taking such a
+  value.<p class="example">For example, a book about the first moon landing
+   could be called "mission:moon". A "title"
+  property from a vocabulary that defines a title as being a string
+  would not expect the title to be given in an <code>a</code> element,
+  even though it looks like a <a href="#url">URL</a>. On the other hand, if
+  there was a (rather narrowly scoped!) vocabulary for "books whose
+  titles look like URLs" which had a "title" property defined to take
+  a URL, then the property <em>would</em> expect the title to be given
+  in an <code>a</code> element (or one of the other <a href="#url-property-elements">URL property
+  elements</a>), because of the requirement above.<div class="impl"> 
 
 
   <h3 id="associating-names-with-items"><span class="secno">2.5 </span>Associating names with items</h3>
@@ -1617,10 +1617,9 @@
    <dd><p>The attribute must act as it would if it was <a href="#reflect" title="reflect">reflecting</a> the element's <code title="">data</code> content attribute.</dd>
 
 
-   <dt>If the element is a <code>time</code> element with a <code title="attr-time-datetime">datetime</code> attribute</dt>
+   <dt>If the element is a <code>data</code> element</dt>
 
-   <dd><p>The attribute must act as it would if it was <a href="#reflect" title="reflect">reflecting</a> the element's <code title="attr-time-datetime">datetime</code> content
-   attribute.</dd>
+   <dd><p>The attribute must act as it would if it was <a href="#reflect" title="reflect">reflecting</a> the element's <code title="attr-data-value">value</code> content attribute.</dd>
 
 
    <dt>Otherwise</dt>

Received on Saturday, 29 October 2011 05:43:52 UTC