HTML Standard Tracker

Diff (omit for latest revision)
Filter

Short URL: http://html5.org/r/3683

File a bug

SVNBugCommentTime (UTC)
3683Add UA conformance criteria for <head profile> and <meta scheme>; remove bogus conformance criteria for id=''.2009-08-28 00:33
Index: source
===================================================================
--- source	(revision 3682)
+++ source	(revision 3683)
@@ -7806,12 +7806,12 @@
 
   <h5>The <dfn title="attr-id"><code>id</code></dfn> attribute</h5>
 
-  <p>The <code title="attr-id">id</code> attribute
-  <span>represents</span> its element's <dfn title="concept-id">unique
-  identifier (ID)</dfn>. The value must be unique amongst all the IDs
-  in the element's <span>home subtree</span> and must contain at least
-  one character. The value must not contain any <span title="space
-  character">space characters</span>.</p>
+  <p>The <code title="attr-id">id</code> attribute specifies its
+  element's <dfn title="concept-id">unique identifier (ID)</dfn>. The
+  value must be unique amongst all the IDs in the element's <span>home
+  subtree</span> and must contain at least one character. The value
+  must not contain any <span title="space character">space
+  characters</span>.</p>
 
   <!-- space characters are disallowed because space-separated lists
   of IDs otherwise would not be able to reach all valid IDs -->
@@ -85991,6 +85991,21 @@
            attribute DOMString <span title="dom-head-profile">profile</span>;
 };</pre>
 
+  <p>User agents should ignore the <code
+  title="attr-head-profile">profile</code> content attribute on
+  <code>head</code> elements.</p>
+
+  <p>When the attribute would be used as a globally unique name, the
+  user agent should instead always assume that all known profiles
+  apply to all pages, and should therefore apply the conventions of
+  all known metadata profiles to the document.</p>
+
+  <p>When the attribute's value would be handled as a <span>URL</span>
+  and dereferenced, the user agent may <span title="resolve a
+  url">resolve</span> the attribute's value, and if that is
+  successful, may then <span>fetch</span> the resulting <span>absolute
+  URL</span> and apply the appropriate processing.</p>
+
   <p>The <dfn title="dom-head-profile"><code>profile</code></dfn> DOM
   attribute of the <code>head</code> element must <span>reflect</span>
   the content attribute of the same name.</p>
@@ -86173,6 +86188,49 @@
            attribute DOMString <span title="dom-meta-scheme">scheme</span>;
 };</pre>
 
+  <p>User agents may treat the <code
+  title="attr-meta-scheme">scheme</code> content attribute on the
+  <code>meta</code> element as an extension of the element's <code
+  title="attr-meta-name">name</code> content attribute when processing
+  a <code>meta</code> element with a <code
+  title="attr-meta-name">name</code> attribute whose value is one that
+  the user agent recognises as supporting the <code
+  title="attr-meta-scheme">scheme</code> attribute.</p>
+
+  <p>User agents are encouraged to ignore the <code
+  title="attr-meta-scheme">scheme</code> attribute and instead process
+  the value given to the metadata name as if it had been specified for
+  each expected value of the <code
+  title="attr-meta-scheme">scheme</code> attribute.</p>
+
+  <div class="example">
+
+   <p>For example, if the user agent acts on <code>meta</code>
+   elements with <code title="attr-meta-name">name</code> attributes
+   having the value "eGMS.subject.keyword", and knows that the <code
+   title="attr-meta-scheme">scheme</code> attribute is used with this
+   metadata name, then it could take the <code
+   title="attr-meta-scheme">scheme</code> attribute into account,
+   acting as if it was an extension of the <code
+   title="attr-meta-name">name</code> attribute. Thus the following
+   two <code>meta</code> elements could be treated as two elements
+   giving values for two different metadata names, one consisting of a
+   combination of "eGMS.subject.keyword" and "LGCL", and the other
+   consisting of a combination of "eGMS.subject.keyword" and
+   "ORLY":</p>
+
+   <pre class="bad">&lt;!-- this markup is invalid -->
+&lt;meta name="eGMS.subject.keyword" scheme="LGCL" content="Abandoned vehicles">
+&lt;meta name="eGMS.subject.keyword" scheme="ORLY" content="Mah car: kthxbye"></pre>
+
+   <p>The recommended processing of this markup, however, would be
+   equivalent to the following:</p>
+
+   <pre>&lt;meta name="eGMS.subject.keyword" content="Abandoned vehicles">
+&lt;meta name="eGMS.subject.keyword" content="Mah car: kthxbye"></pre>
+
+  </div>
+
   <p>The <dfn title="dom-meta-scheme"><code>scheme</code></dfn> DOM
   attribute of the <code>meta</code> element must <span>reflect</span>
   the content attribute of the same name.</p>

|