[html5] r5469 - [e] (0) Suggest that 'data-*-*' should allow the prefix to be changed in librari [...]

[whatwg at whatwg.org]

Author: ianh
Date: 2010-09-23 10:41:23 -0700 (Thu, 23 Sep 2010)
New Revision: 5469

Modified:
   complete.html
   index
   source
Log:
[e] (0) Suggest that 'data-*-*' should allow the prefix to be changed in libraries.
Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=9828

Modified: complete.html
===================================================================
--- complete.html	2010-09-10 23:27:01 UTC (rev 5468)
+++ complete.html	2010-09-23 17:41:23 UTC (rev 5469)
@@ -209,7 +209,7 @@
 
   <header class=head id=head><p><a class=logo href=http://www.whatwg.org/ rel=home><img alt=WHATWG height=101 src=/images/logo width=101></a></p>
    <hgroup><h1>Web Applications 1.0</h1>
-    <h2 class="no-num no-toc">Draft Standard — 10 September 2010</h2>
+    <h2 class="no-num no-toc">Draft Standard — 23 September 2010</h2>
    </hgroup><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>-->
@@ -9813,13 +9813,21 @@
   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>
+  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>
 

Modified: index
===================================================================
--- index	2010-09-10 23:27:01 UTC (rev 5468)
+++ index	2010-09-23 17:41:23 UTC (rev 5469)
@@ -213,7 +213,7 @@
 
   <header class=head id=head><p><a class=logo href=http://www.whatwg.org/ rel=home><img alt=WHATWG height=101 src=/images/logo width=101></a></p>
    <hgroup><h1>HTML5 (including next generation additions still in development)</h1>
-    <h2 class="no-num no-toc">Draft Standard — 10 September 2010</h2>
+    <h2 class="no-num no-toc">Draft Standard — 23 September 2010</h2>
    </hgroup><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>-->
@@ -9790,13 +9790,21 @@
   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>
+  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>
 

Modified: source
===================================================================
--- source	2010-09-10 23:27:01 UTC (rev 5468)
+++ source	2010-09-23 17:41:23 UTC (rev 5469)
@@ -9978,14 +9978,23 @@
   attribute">custom data attributes</span>, 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>
+  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>
+   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>