W3C home > Mailing lists > Public > public-html-diffs@w3.org > September 2010

hixie: Suggest that 'data-*-*' should allow the prefix to be changed in libraries. (whatwg r5469)

From: poot <cvsmail@w3.org>
Date: Fri, 24 Sep 2010 02:41:50 +0900 (JST)
To: public-html-diffs@w3.org
Message-Id: <20100923174150.5EDAE2BC46@toro.w3.mag.keio.ac.jp>
hixie: Suggest that 'data-*-*' should allow the prefix to be changed in
libraries. (whatwg r5469)

http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.4360&r2=1.4361&f=h
http://html5.org/tools/web-apps-tracker?from=5468&to=5469

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.4360
retrieving revision 1.4361
diff -u -d -r1.4360 -r1.4361
--- Overview.html	10 Sep 2010 23:27:06 -0000	1.4360
+++ Overview.html	23 Sep 2010 17:41:29 -0000	1.4361
@@ -311,7 +311,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>
@@ -417,7 +417,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
@@ -8495,11 +8495,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.<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.<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:<dl><dt>Categories</dt>
@@ -40200,7 +40208,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>The <code title="rel-nofollow"><a href="#link-type-nofollow">nofollow</a></code> keyword may be
   used with <code><a href="#the-a-element">a</a></code> and <code><a href="#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
@@ -40208,7 +40216,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.<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.<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>The <code title="rel-noreferrer"><a href="#link-type-noreferrer">noreferrer</a></code> keyword may be
   used with <code><a href="#the-a-element">a</a></code> and <code><a href="#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
@@ -40292,7 +40300,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>The <code title="rel-up"><a href="#link-type-up">up</a></code> keyword may be used with
   <code><a href="#the-link-element">link</a></code>, <code><a href="#the-a-element">a</a></code>, and <code><a href="#the-area-element">area</a></code>
   elements. This keyword creates a <a href="#hyperlink">hyperlink</a>.<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
Received on Thursday, 23 September 2010 17:42:46 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:09:10 UTC