html5/spec elements.html,1.13,1.14 iana.html,1.331,1.332 links.html,1.25,1.26 spec.html,1.1206,1.1207

Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv21585

Modified Files:
	elements.html iana.html links.html spec.html 
Log Message:
Let W3C deal with the registries. (whatwg r5470)

[updated by splitter]


Index: elements.html
===================================================================
RCS file: /sources/public/html5/spec/elements.html,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -d -r1.13 -r1.14
--- elements.html	10 Sep 2010 01:47:06 -0000	1.13
+++ elements.html	23 Sep 2010 17:46:44 -0000	1.14
@@ -1070,11 +1070,19 @@
   attribute">custom data attributes</a>, as they are considered to
   be part of the page on which they are used. Authors of libraries
   that are reused by many authors are encouraged to include their name
-  in the attribute names, to reduce the risk of clashes.</p><div class="example">
+  in the attribute names, to reduce the risk of clashes. Where it
+  makes sense, library authors are also encouraged to make the exact
+  name used in the attribute names customizable, so that libraries
+  whose authors unknowingly picked the same name can be used on the
+  same page, and so that multiple versions of a particular library can
+  be used on the same page even when those versions are not mutually
+  compatible.</p><div class="example">
 
    <p>For example, a library called "DoQuery" could use attribute
    names like <code title="">data-doquery-range</code>, and a library
-   called "jJo" could use attributes names like <code title="">data-jjo-range</code>.</p>
+   called "jJo" could use attributes names like <code title="">data-jjo-range</code>. The jJo library could also provide
+   an API to set which prefix to use (e.g. <code title="">J.setDataPrefix('j2')</code>, making the attributes have
+   names like <code title="">data-j2-range</code>).</p>
 
   </div><h4 id="element-definitions"><span class="secno">3.2.4 </span>Element definitions</h4><p>Each element in this specification has a definition that includes
   the following information:</p><dl><dt>Categories</dt>

Index: iana.html
===================================================================
RCS file: /sources/public/html5/spec/iana.html,v
retrieving revision 1.331
retrieving revision 1.332
diff -u -d -r1.331 -r1.332
--- iana.html	8 Sep 2010 09:25:45 -0000	1.331
+++ iana.html	23 Sep 2010 17:46:44 -0000	1.332
@@ -501,7 +501,7 @@
    <dt>Author:</dt>
    <dd>Ian Hickson &lt;ian@hixie.ch&gt;</dd>
    <dt>Change controller:</dt>
-   <dd>WHATWG</dd>
+   <dd>W3C</dd>
   </dl><p>Fragment identifiers used with <code><a href="#text-html-sandboxed">text/html-sandboxed</a></code>
   resources refer to <a href="history.html#the-indicated-part-of-the-document">the indicated part of the
   document</a>.</p><h3 id="application-xhtml-xml"><span class="secno">12.3 </span><dfn><code>application/xhtml+xml</code></dfn></h3><p>This registration is for community review and will be submitted
@@ -617,6 +617,6 @@
    <dt>Author:</dt>
    <dd>Ian Hickson &lt;ian@hixie.ch&gt;</dd>
    <dt>Change controller:</dt>
-   <dd>WHATWG</dd>
+   <dd>W3C</dd>
   </dl><p>Fragment identifiers have no meaning with
   <code><a href="#text-cache-manifest">text/cache-manifest</a></code> resources.</p></body></html>
\ No newline at end of file

Index: links.html
===================================================================
RCS file: /sources/public/html5/spec/links.html,v
retrieving revision 1.25
retrieving revision 1.26
diff -u -d -r1.25 -r1.26
--- links.html	10 Sep 2010 01:47:09 -0000	1.25
+++ links.html	23 Sep 2010 17:46:44 -0000	1.26
@@ -938,7 +938,7 @@
   must also treat the keyword "<code title="">copyright</code>" like
   the <code title="rel-license"><a href="#link-type-license">license</a></code> keyword.</p>
 
-  </div><h5 id="link-type-nofollow"><span class="secno">4.12.4.9 </span>Link type "<dfn title="rel-nofollow"><code>nofollow</code></dfn>"</h5><p>The <code title="rel-nofollow"><a href="#link-type-nofollow">nofollow</a></code> keyword may be
+  </div><h5 id="link-type-nofollow"><span class="secno">4.12.4.9 </span>Link type "<dfn title="rel-nofollow"><code>nofollow</code></dfn>"</h5><p class="XXX annotation"><span><a href="http://www.w3.org/html/wg/tracker/issues/124">ISSUE-124</a> (rel-limits) blocks progress to Last Call</span></p><p>The <code title="rel-nofollow"><a href="#link-type-nofollow">nofollow</a></code> keyword may be
   used with <code><a href="text-level-semantics.html#the-a-element">a</a></code> and <code><a href="the-map-element.html#the-area-element">area</a></code> elements. This
   keyword does not create a <a href="#hyperlink">hyperlink</a>, but <a href="#hyperlink-annotation" title="hyperlink annotation">annotates</a> any other hyperlinks
   created by the element (the implied hyperlink, if no other keywords
@@ -946,7 +946,7 @@
   that the link is not endorsed by the original author or publisher of
   the page, or that the link to the referenced document was included
   primarily because of a commercial relationship between people
-  affiliated with the two pages.</p><h5 id="link-type-noreferrer"><span class="secno">4.12.4.10 </span>Link type "<dfn title="rel-noreferrer"><code>noreferrer</code></dfn>"</h5><p>The <code title="rel-noreferrer"><a href="#link-type-noreferrer">noreferrer</a></code> keyword may be
+  affiliated with the two pages.</p><h5 id="link-type-noreferrer"><span class="secno">4.12.4.10 </span>Link type "<dfn title="rel-noreferrer"><code>noreferrer</code></dfn>"</h5><p class="XXX annotation"><span><a href="http://www.w3.org/html/wg/tracker/issues/124">ISSUE-124</a> (rel-limits) blocks progress to Last Call</span></p><p>The <code title="rel-noreferrer"><a href="#link-type-noreferrer">noreferrer</a></code> keyword may be
   used with <code><a href="text-level-semantics.html#the-a-element">a</a></code> and <code><a href="the-map-element.html#the-area-element">area</a></code> elements. This
   keyword does not create a <a href="#hyperlink">hyperlink</a>, but <a href="#hyperlink-annotation" title="hyperlink annotation">annotates</a> any other hyperlinks
   created by the element (the implied hyperlink, if no other keywords
@@ -1030,7 +1030,7 @@
   must also treat the keywords "<code title="">top</code>", "<code title="">contents</code>", and "<code title="">toc</code>" like the
   <code title="rel-index"><a href="#link-type-index">index</a></code> keyword.</p>
 
-  </div><h6 id="link-type-up"><span class="secno">4.12.4.17.2 </span>Link type "<dfn title="rel-up"><code>up</code></dfn>"</h6><p>The <code title="rel-up"><a href="#link-type-up">up</a></code> keyword may be used with
+  </div><h6 id="link-type-up"><span class="secno">4.12.4.17.2 </span>Link type "<dfn title="rel-up"><code>up</code></dfn>"</h6><p class="XXX annotation"><span><a href="http://www.w3.org/html/wg/tracker/issues/119">ISSUE-119</a> (rel-repetition) blocks progress to Last Call</span></p><p>The <code title="rel-up"><a href="#link-type-up">up</a></code> keyword may be used with
   <code><a href="semantics.html#the-link-element">link</a></code>, <code><a href="text-level-semantics.html#the-a-element">a</a></code>, and <code><a href="the-map-element.html#the-area-element">area</a></code>
   elements. This keyword creates a <a href="#hyperlink">hyperlink</a>.</p><p>The <code title="rel-up"><a href="#link-type-up">up</a></code> keyword indicates that the
   document is part of a hierarchical structure, and that the link is

Index: spec.html
===================================================================
RCS file: /sources/public/html5/spec/spec.html,v
retrieving revision 1.1206
retrieving revision 1.1207
diff -u -d -r1.1206 -r1.1207
--- spec.html	10 Sep 2010 23:46:33 -0000	1.1206
+++ spec.html	23 Sep 2010 17:46:44 -0000	1.1207
@@ -315,7 +315,7 @@
 
    <h1>HTML5</h1>
    <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>
-   <h2 class="no-num no-toc" id="editor-s-draft-10-september-2010">Editor's Draft 10 September 2010</h2>
+   <h2 class="no-num no-toc" id="editor-s-draft-23-september-2010">Editor's Draft 23 September 2010</h2>
    <dl><dt>Latest Published Version:</dt>
     <dd><a href="http://www.w3.org/TR/html5/">http://www.w3.org/TR/html5/</a></dd>
     <dt>Latest Editor's Draft:</dt>
@@ -336,7 +336,7 @@
     <a href="Overview.html">single page HTML</a>,
     <a href="spec.html">multipage HTML</a>,
     <a href="author/">web developer edition</a>.
-This is revision 1.4360.
+This is revision 1.4362.
    </p> 
      <p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a>
    &#169; 2010 <a href="http://www.w3.org/"><abbr title="World Wide
@@ -421,7 +421,7 @@
   Group</a> is the W3C working group responsible for this
   specification's progress along the W3C Recommendation
   track.
-  This specification is the 10 September 2010 Editor's Draft.
+  This specification is the 23 September 2010 Editor's Draft.
   </p><!-- UNDER NO CIRCUMSTANCES IS THE PRECEDING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><!-- relationship to other work (required) --><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 --><!-- required patent boilerplate --><p>This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5

Received on Thursday, 23 September 2010 17:46:49 UTC