Skip to content
Permalink
Browse files

[] (0) Add UA conformance criteria for <head profile> and <meta schem…

…e>; remove bogus conformance criteria for id=''.

git-svn-id: http://svn.whatwg.org/webapps@3683 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information...
Hixie committed Aug 28, 2009
1 parent 4da1e2e commit 38996e686ac2de48b0df2d8bbc58e996878350eb
Showing with 119 additions and 13 deletions.
  1. +55 −7 index
  2. +64 −6 source
62 index
@@ -71,7 +71,7 @@
<div class=head>
<p><a class=logo href=http://www.whatwg.org/ rel=home><img alt=WHATWG src=/images/logo></a></p>
<h1>HTML 5</h1>
<h2 class="no-num no-toc" id=draft-standard-&mdash;-26-august-2009>Draft Standard &mdash; 26 August 2009</h2>
<h2 class="no-num no-toc" id=draft-standard-&mdash;-27-august-2009>Draft Standard &mdash; 27 August 2009</h2>
<p>You can take part in this work. <a href=http://www.whatwg.org/mailing-list>Join the working group's discussion list.</a></p>
<p><strong>Web designers!</strong> We have a <a href=http://blog.whatwg.org/faq/>FAQ</a>, a <a href=http://forums.whatwg.org/>forum</a>, and a <a href=http://www.whatwg.org/mailing-list#help>help mailing list</a> for you!</p>
<!--<p class="impl"><strong>Implementors!</strong> We have a <a href="http://www.whatwg.org/mailing-list#implementors">mailing list</a> for you too!</p>-->
@@ -7686,12 +7686,12 @@ interface <dfn id=htmlunknownelement>HTMLUnknownElement</dfn> : <a href=#htmlele

<h5 id=the-id-attribute><span class=secno>3.2.3.1 </span>The <dfn title=attr-id><code>id</code></dfn> attribute</h5>

<p>The <code title=attr-id><a href=#the-id-attribute>id</a></code> attribute
<a href=#represents>represents</a> its element's <dfn id=concept-id title=concept-id>unique
identifier (ID)</dfn>. The value must be unique amongst all the IDs
in the element's <a href=#home-subtree>home subtree</a> and must contain at least
one character. The value must not contain any <a href=#space-character title="space
character">space characters</a>.</p>
<p>The <code title=attr-id><a href=#the-id-attribute>id</a></code> attribute specifies its
element's <dfn id=concept-id title=concept-id>unique identifier (ID)</dfn>. The
value must be unique amongst all the IDs in the element's <a href=#home-subtree>home
subtree</a> and must contain at least one character. The value
must not contain any <a href=#space-character title="space character">space
characters</a>.</p>

<!-- space characters are disallowed because space-separated lists
of IDs otherwise would not be able to reach all valid IDs -->
attribute DOMString <a href=#dom-head-profile title=dom-head-profile>profile</a>;
};</pre>

<p>User agents should ignore the <code title=attr-head-profile><a href=#attr-head-profile>profile</a></code> content attribute on
<code><a href=#the-head-element-0>head</a></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 <a href=#url>URL</a>
and dereferenced, the user agent may <a href=#resolve-a-url title="resolve a
url">resolve</a> the attribute's value, and if that is
successful, may then <a href=#fetch>fetch</a> the resulting <a href=#absolute-url>absolute
URL</a> and apply the appropriate processing.</p>

<p>The <dfn id=dom-head-profile title=dom-head-profile><code>profile</code></dfn> DOM
attribute of the <code><a href=#the-head-element-0>head</a></code> element must <a href=#reflect>reflect</a>
the content attribute of the same name.</p>
attribute DOMString <a href=#dom-meta-scheme title=dom-meta-scheme>scheme</a>;
};</pre>

<p>User agents may treat the <code title=attr-meta-scheme><a href=#attr-meta-scheme>scheme</a></code> content attribute on the
<code><a href=#meta>meta</a></code> element as an extension of the element's <code title=attr-meta-name><a href=#attr-meta-name>name</a></code> content attribute when processing
a <code><a href=#meta>meta</a></code> element with a <code title=attr-meta-name><a href=#attr-meta-name>name</a></code> attribute whose value is one that
the user agent recognises as supporting the <code title=attr-meta-scheme><a href=#attr-meta-scheme>scheme</a></code> attribute.</p>

<p>User agents are encouraged to ignore the <code title=attr-meta-scheme><a href=#attr-meta-scheme>scheme</a></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><a href=#attr-meta-scheme>scheme</a></code> attribute.</p>

<div class=example>

<p>For example, if the user agent acts on <code><a href=#meta>meta</a></code>
elements with <code title=attr-meta-name><a href=#attr-meta-name>name</a></code> attributes
having the value "eGMS.subject.keyword", and knows that the <code title=attr-meta-scheme><a href=#attr-meta-scheme>scheme</a></code> attribute is used with this
metadata name, then it could take the <code title=attr-meta-scheme><a href=#attr-meta-scheme>scheme</a></code> attribute into account,
acting as if it was an extension of the <code title=attr-meta-name><a href=#attr-meta-name>name</a></code> attribute. Thus the following
two <code><a href=#meta>meta</a></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 --&gt;
&lt;meta name="eGMS.subject.keyword" scheme="LGCL" content="Abandoned vehicles"&gt;
&lt;meta name="eGMS.subject.keyword" scheme="ORLY" content="Mah car: kthxbye"&gt;</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"&gt;
&lt;meta name="eGMS.subject.keyword" content="Mah car: kthxbye"&gt;</pre>

</div>

<p>The <dfn id=dom-meta-scheme title=dom-meta-scheme><code>scheme</code></dfn> DOM
attribute of the <code><a href=#meta>meta</a></code> element must <a href=#reflect>reflect</a>
the content attribute of the same name.</p>
70 source
@@ -7806,12 +7806,12 @@ interface <dfn>HTMLUnknownElement</dfn> : <span>HTMLElement</span> { };</pre>

<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 -->
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>
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>

0 comments on commit 38996e6

Please sign in to comment.
You can’t perform that action at this time.