W3C home > Mailing lists > Public > public-html-commits@w3.org > August 2009

html5/spec Overview.html,1.2861,1.2862

From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
Date: Fri, 28 Aug 2009 00:31:55 +0000
To: public-html-commits@w3.org
Message-Id: <E1MgpNj-0002ed-7U@lionel-hutz.w3.org>
Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv10189

Modified Files:
	Overview.html 
Log Message:
Add UA conformance criteria for <head profile> and <meta scheme>; remove bogus conformance criteria for id=''. (whatwg r3683)

Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.2861
retrieving revision 1.2862
diff -u -d -r1.2861 -r1.2862
--- Overview.html	26 Aug 2009 22:31:45 -0000	1.2861
+++ Overview.html	28 Aug 2009 00:31:51 -0000	1.2862
@@ -174,7 +174,7 @@
    <h2 class="no-num no-toc" id="a-vocabulary-and-associated-apis-for-html-and-xhtml">A vocabulary and associated APIs for HTML and XHTML</h2>
    <!--ZZZ:-->
    <h2 class="no-num no-toc" id="w3c-working-draft-25-august-2009">W3C Working Draft 25 August 2009</h2>
-   <!--<h2 class="no-num no-toc">Editor's Draft 26 August 2009</h2>-->
+   <!--<h2 class="no-num no-toc">Editor's Draft 27 August 2009</h2>-->
    <!--:ZZZ-->
    <dl><!-- ZZZ: update the month/day (twice), (un)comment out--><dt>This Version:</dt>
     <dd><a href="http://www.w3.org/TR/2009/WD-html5-20090825/">http://www.w3.org/TR/2009/WD-html5-20090825/</a></dd>
@@ -272,7 +272,7 @@
   track.
   <!--ZZZ:-->
   This specification is the 25 August 2009 Working Draft.
-  <!--This specification is the 26 August 2009 Editor's Draft.-->
+  <!--This specification is the 27 August 2009 Editor's Draft.-->
   <!--:ZZZ-->
   </p><!-- UNDER NO CIRCUMSTANCES IS THE PRECEDING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><!-- relationship to other work (required) --><p>This specification is also being produced by the <a href="http://www.whatwg.org/">WHATWG</a>. The two specifications are
   identical from the table of contents onwards.</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 --><!-- context and rationale (required) --><p>This specification is intended to replace (be a new version of)
@@ -6933,12 +6933,12 @@
   namespace specified.<hr><p>To enable assistive technology products to expose a more
   fine-grained interface than is otherwise possible with HTML elements
   and attributes, a set of <a href="#annotations-for-assistive-technology-products">annotations for assistive technology
-  products</a> can be specified.<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 class="XXX annotation"><b>Status: </b><i>Implemented and widely deployed</i><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><!-- space characters are disallowed because space-separated lists
+  products</a> can be specified.<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 class="XXX annotation"><b>Status: </b><i>Implemented and widely deployed</i><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 --><p class="note">An element's <a href="#concept-id" title="concept-id">unique
   identifier</a> can be used for a variety of purposes, most
   notably as a way to link to specific parts of a document using
@@ -7909,7 +7909,7 @@
    <p>To avoid this confusion, explicit <code><a href="#the-p-element">p</a></code> elements can be
    used.</p>
 
-  </div><h4 id="annotations-for-assistive-technology-products"><span class="secno">3.2.6 </span><dfn>Annotations for assistive technology products</dfn></h4><p class="XXX annotation"><b>Status: </b><i>First draft. </i><span><a href="http://www.w3.org/html/wg/tracker/issues/35">ISSUE-35</a> (aria-processing) and <a href="http://www.w3.org/html/wg/tracker/issues/14">ISSUE-14</a> (aria-role) block progress to Last Call</span><p>Authors may use the ARIA <code title="attr-aria-role">role</code>
+  </div><h4 id="annotations-for-assistive-technology-products"><span class="secno">3.2.6 </span><dfn>Annotations for assistive technology products</dfn></h4><p class="XXX annotation"><b>Status: </b><i>First draft. </i><span><a href="http://www.w3.org/html/wg/tracker/issues/14">ISSUE-14</a> (aria-role) and <a href="http://www.w3.org/html/wg/tracker/issues/35">ISSUE-35</a> (aria-processing) block progress to Last Call</span><p>Authors may use the ARIA <code title="attr-aria-role">role</code>
   and <code title="attr-aria-*">aria-*</code> attributes on <a href="#html-elements">HTML
   elements</a>, in accordance with the requirements described in
   the ARIA specifications, except where these conflict with the
@@ -15330,7 +15330,7 @@
  &lt;legend&gt;The castle through the ages: 1423, 1858, and 1999 respectively.&lt;/legend&gt;
 &lt;/figure&gt;</pre>
 
-  </div><h4 id="the-img-element"><span class="secno">4.8.2 </span>The <dfn><code>img</code></dfn> element</h4><p class="XXX annotation"><b>Status: </b><i>Last call for comments. </i><span><a href="http://www.w3.org/html/wg/tracker/issues/66">ISSUE-66</a> (image-analysis) and <a href="http://www.w3.org/html/wg/tracker/issues/30">ISSUE-30</a> (longdesc) block progress to Last Call</span><dl class="element"><dt>Categories</dt>
+  </div><h4 id="the-img-element"><span class="secno">4.8.2 </span>The <dfn><code>img</code></dfn> element</h4><p class="XXX annotation"><b>Status: </b><i>Last call for comments. </i><span><a href="http://www.w3.org/html/wg/tracker/issues/30">ISSUE-30</a> (longdesc) and <a href="http://www.w3.org/html/wg/tracker/issues/66">ISSUE-66</a> (image-analysis) block progress to Last Call</span><dl class="element"><dt>Categories</dt>
    <dd><a href="#flow-content">Flow content</a>.</dd>
    <dd><a href="#phrasing-content">Phrasing content</a>.</dd>
    <dd><a href="#embedded-content">Embedded content</a>.</dd>
@@ -17584,7 +17584,7 @@
   <a href="#reflect">reflect</a> the respective content attributes of the same
   name.</p>
 
-  </div><h4 id="video"><span class="secno">4.8.7 </span>The <dfn><code>video</code></dfn> element</h4><p class="XXX annotation"><b>Status: </b><i>Last call for comments. </i><span><a href="http://www.w3.org/html/wg/tracker/issues/9">ISSUE-9</a> (video-synchronization), <a href="http://www.w3.org/html/wg/tracker/issues/10">ISSUE-10</a> (video-smil) and <a href="http://www.w3.org/html/wg/tracker/issues/7">ISSUE-7</a> (video-codecs) block progress to Last Call</span><dl class="element"><dt>Categories</dt>
+  </div><h4 id="video"><span class="secno">4.8.7 </span>The <dfn><code>video</code></dfn> element</h4><p class="XXX annotation"><b>Status: </b><i>Last call for comments. </i><span><a href="http://www.w3.org/html/wg/tracker/issues/9">ISSUE-9</a> (video-synchronization), <a href="http://www.w3.org/html/wg/tracker/issues/7">ISSUE-7</a> (video-codecs) and <a href="http://www.w3.org/html/wg/tracker/issues/10">ISSUE-10</a> (video-smil) block progress to Last Call</span><dl class="element"><dt>Categories</dt>
    <dd><a href="#flow-content">Flow content</a>.</dd>
    <dd><a href="#phrasing-content">Phrasing content</a>.</dd>
    <dd><a href="#embedded-content">Embedded content</a>.</dd>
@@ -23723,7 +23723,7 @@
   user agent must act as if it had rerun the algorithms for image
   maps.</p>
 
-  </div><h4 id="mathml"><span class="secno">4.8.15 </span>MathML</h4><p class="XXX annotation"><b>Status: </b><i>Last call for comments. </i><span><a href="http://www.w3.org/html/wg/tracker/issues/37">ISSUE-37</a> (html-svg-mathml) blocks progress to Last Call</span><p>The <dfn id="math"><code>math</code></dfn> element from the <a href="#mathml-namespace">MathML
+  </div><h4 id="mathml"><span class="secno">4.8.15 </span>MathML</h4><p class="XXX annotation"><b>Status: </b><i>Last call for comments</i><p>The <dfn id="math"><code>math</code></dfn> element from the <a href="#mathml-namespace">MathML
   namespace</a> falls into the <a href="#embedded-content">embedded content</a>
   category for the purposes of the content models in this
   specification.<div class="impl">
@@ -48386,7 +48386,7 @@
   <a href="#source-browsing-context">source browsing context</a>.</p>
 
 
-  <h5 id="hyperlink-auditing"><span class="secno">6.12.2.1 </span><dfn>Hyperlink auditing</dfn></h5><p class="XXX annotation"><b>Status: </b><i>Controversial Working Draft. </i><span><a href="http://www.w3.org/html/wg/tracker/issues/1">ISSUE-1</a> (PINGPOST), <a href="http://www.w3.org/html/wg/tracker/issues/2">ISSUE-2</a> (PINGUI) and <a href="http://www.w3.org/html/wg/tracker/issues/63">ISSUE-63</a> (origin-req-scope) block progress to Last Call</span></p>
+  <h5 id="hyperlink-auditing"><span class="secno">6.12.2.1 </span><dfn>Hyperlink auditing</dfn></h5><p class="XXX annotation"><b>Status: </b><i>Controversial Working Draft. </i><span><a href="http://www.w3.org/html/wg/tracker/issues/2">ISSUE-2</a> (PINGUI), <a href="http://www.w3.org/html/wg/tracker/issues/1">ISSUE-1</a> (PINGPOST) and <a href="http://www.w3.org/html/wg/tracker/issues/63">ISSUE-63</a> (origin-req-scope) block progress to Last Call</span></p>
 
   <p>If an <code><a href="#the-a-element">a</a></code> or <code><a href="#the-area-element">area</a></code> hyperlink element has a
   <code title="attr-hyperlink-ping"><a href="#ping">ping</a></code> attribute, and the
@@ -53439,7 +53439,7 @@
   the ranges U+0041 .. U+005A (LATIN CAPITAL LETTER A to LATIN CAPITAL
   LETTER Z) and U+0061 .. U+007A (LATIN SMALL LETTER A to LATIN SMALL
   LETTER Z). For convenience, in this section this is just referred to
-  as "case-insensitive".<h4 id="the-doctype"><span class="secno">9.1.1 </span>The DOCTYPE</h4><p class="XXX annotation"><span><a href="http://www.w3.org/html/wg/tracker/issues/4">ISSUE-4</a> (html-versioning) and <a href="http://www.w3.org/html/wg/tracker/issues/54">ISSUE-54</a> (doctype-legacy-compat) block progress to Last Call</span><p>A <dfn id="syntax-doctype" title="syntax-doctype">DOCTYPE</dfn> is a mostly useless,
+  as "case-insensitive".<h4 id="the-doctype"><span class="secno">9.1.1 </span>The DOCTYPE</h4><p class="XXX annotation"><span><a href="http://www.w3.org/html/wg/tracker/issues/4">ISSUE-4</a> (html-versioning) blocks progress to Last Call</span><p>A <dfn id="syntax-doctype" title="syntax-doctype">DOCTYPE</dfn> is a mostly useless,
   but required, header.<p class="note">DOCTYPEs are required for legacy reasons. When
   omitted, browsers tend to use a different rendering mode that is
   incompatible with some specifications. Including the DOCTYPE in a
@@ -54064,7 +54064,7 @@
   specification. This section does not apply to XML documents. <a href="#refsXML">[XML]</a></p>
 
 
-  <h5 id="determining-the-character-encoding"><span class="secno">9.2.2.1 </span>Determining the character encoding</h5><p class="XXX annotation"><b>Status: </b><i>Working draft. </i><span><a href="http://www.w3.org/html/wg/tracker/issues/11">ISSUE-11</a> (default-encoding) blocks progress to Last Call</span></p>
+  <h5 id="determining-the-character-encoding"><span class="secno">9.2.2.1 </span>Determining the character encoding</h5><p class="XXX annotation"><b>Status: </b><i>Working draft</i></p>
 
   <p>In some cases, it might be impractical to unambiguously determine
   the encoding before parsing the document. Because of this, this
@@ -59467,7 +59467,7 @@
     mode</a>.</p>
    </dd>
 
-  </dl><h5 id="parsing-main-inforeign"><span class="secno">9.2.5.21 </span>The "<dfn title="insertion mode: in foreign content">in foreign content</dfn>" insertion mode</h5><p class="XXX annotation"><span><a href="http://www.w3.org/html/wg/tracker/issues/37">ISSUE-37</a> (html-svg-mathml) blocks progress to Last Call</span></p>
+  </dl><h5 id="parsing-main-inforeign"><span class="secno">9.2.5.21 </span>The "<dfn title="insertion mode: in foreign content">in foreign content</dfn>" insertion mode</h5>
 
   <p>When the <a href="#insertion-mode">insertion mode</a> is "<a href="#parsing-main-inforeign" title="insertion
   mode: in foreign content">in foreign content</a>", tokens must be
@@ -66227,6 +66227,20 @@
            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>
@@ -66372,6 +66386,40 @@
            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>
Received on Friday, 28 August 2009 00:32:05 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 28 August 2009 00:32:09 GMT