[e] (0) Now both pedancy and simplicity are losing in the race for cl…

…arity. Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=13370 git-svn-id: http://svn.whatwg.org/webapps@6343 340c8d12-0b0e-0410-8428-c7bf67bfef74
whatwg · Aug 2, 2011 · 75d313c · 75d313c
1 parent 6460b63
commit 75d313c
Show file tree

Hide file tree

Showing 3 changed files with 67 additions and 19 deletions.
diff --git a/complete.html b/complete.html
@@ -56835,16 +56835,32 @@ <h4 id=values><span class=secno>5.2.4 </span>Values</h4>
   <code><a href=#the-object-element>object</a></code>, <code><a href=#the-source-element>source</a></code>, <code><a href=#the-track-element>track</a></code>, and
   <code><a href=#the-video-element>video</a></code> elements.</p>
 
-  <p>If a property's <a href=#concept-property-value title=concept-property-value>value</a>
-  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>
+  <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>
 
   <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><a href=#attr-time-datetime>datetime</a></code> attribute of 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><a href=#attr-time-datetime>datetime</a></code> attribute of a
   <code><a href=#the-time-element>time</a></code> element.</p>
 
+  <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>
+
+  <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><a href=#the-time-element>time</a></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>
+  except the title to be given in a <code><a href=#the-time-element>time</a></code> element, because
+  of the requirement above.</p>
+
 
 
   <div class=impl> <!-- this is unfortunate, as it is hiding authoring conformance criteria (so we leave it in for the w3c copy) -->

diff --git a/index b/index
@@ -56707,16 +56707,32 @@ document.body.appendChild(outer);</pre>
   <code><a href=#the-object-element>object</a></code>, <code><a href=#the-source-element>source</a></code>, <code><a href=#the-track-element>track</a></code>, and
   <code><a href=#the-video-element>video</a></code> elements.</p>
 
-  <p>If a property's <a href=#concept-property-value title=concept-property-value>value</a>
-  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>
+  <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>
 
   <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><a href=#attr-time-datetime>datetime</a></code> attribute of 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><a href=#attr-time-datetime>datetime</a></code> attribute of a
   <code><a href=#the-time-element>time</a></code> element.</p>
 
+  <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>
+
+  <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><a href=#the-time-element>time</a></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>
+  except the title to be given in a <code><a href=#the-time-element>time</a></code> element, because
+  of the requirement above.</p>
+
 
 
   <div class=impl> <!-- this is unfortunate, as it is hiding authoring conformance criteria (so we leave it in for the w3c copy) -->

diff --git a/source b/source
@@ -64083,19 +64083,35 @@ document.body.appendChild(outer);</pre>
   <code>object</code>, <code>source</code>, <code>track</code>, and
   <code>video</code> elements.</p>
 
-  <p>If a property's <span title="concept-property-value">value</span>
-  is an <span>absolute URL</span>, the property must be specified
-  using a <span title="URL property elements">URL property
-  element</span>.</p>
+  <p>If a property's <span
+  title="concept-property-value">value</span>, as defined by the
+  property's definition, is an <span>absolute URL</span>, the property
+  must be specified using a <span title="URL property elements">URL
+  property element</span>.</p>
 
   <p>If a property's <span title="concept-property-value">value</span>
   represents a <span title="concept-date">date</span>, <span
   title="concept-time">time</span>, or <span
-  title="concept-datetime">global date and time</span>, the property
-  must be specified using the <code
-  title="attr-time-datetime">datetime</code> attribute of a
+  title="concept-datetime">global date and time</span>, 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>
 
+  <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>
+
+  <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>
+  except the title to be given in a <code>time</code> element, because
+  of the requirement above.</p>
+
 
 <!--END w3c-html-->
   <div class="impl"> <!-- this is unfortunate, as it is hiding authoring conformance criteria (so we leave it in for the w3c copy) -->