- From: Michael Smith via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 05 Jan 2010 00:48:01 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/spec-author-view
In directory hutz:/tmp/cvs-serv24010
Modified Files:
Overview.html elements.html spec.html
Log Message:
data-* attributes and JS libraries: some advice (whatwg r4462)
[updated by splitter]
Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec-author-view/Overview.html,v
retrieving revision 1.561
retrieving revision 1.562
diff -u -d -r1.561 -r1.562
--- Overview.html 5 Jan 2010 00:37:08 -0000 1.561
+++ Overview.html 5 Jan 2010 00:47:47 -0000 1.562
@@ -281,7 +281,7 @@
</dl><p>This specification is available in the following formats:
<a href="spec.html">single page HTML</a>,
<a href="Overview.html">multipage HTML</a>.
-This is revision 1.3561.
+This is revision 1.3562.
</p>
<p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a>
© 2009 <a href="http://www.w3.org/"><abbr title="World Wide
Index: elements.html
===================================================================
RCS file: /sources/public/html5/spec-author-view/elements.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -d -r1.9 -r1.10
--- elements.html 3 Jan 2010 15:15:05 -0000 1.9
+++ elements.html 5 Jan 2010 00:47:54 -0000 1.10
@@ -769,7 +769,17 @@
</div><p>Authors should carefully design such extensions so that when the
attributes are ignored and any associated CSS dropped, the page is
- still usable.</p><h4 id="element-definitions"><span class="secno">3.2.4 </span>Element definitions</h4><p class="XXX annotation"><b>Status: </b><i>Last call for comments</i></p><p>Each element in this specification has a definition that includes
+ still usable.</p><p>JavaScript libraries may use the <span>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><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>
+
+ </div><h4 id="element-definitions"><span class="secno">3.2.4 </span>Element definitions</h4><p class="XXX annotation"><b>Status: </b><i>Last call for comments</i></p><p>Each element in this specification has a definition that includes
the following information:</p><dl><dt>Categories</dt>
<dd>A list of <a href="content-models.html#content-categories" title="content categories">categories</a> to
Index: spec.html
===================================================================
RCS file: /sources/public/html5/spec-author-view/spec.html,v
retrieving revision 1.566
retrieving revision 1.567
diff -u -d -r1.566 -r1.567
--- spec.html 5 Jan 2010 00:37:08 -0000 1.566
+++ spec.html 5 Jan 2010 00:47:54 -0000 1.567
@@ -279,7 +279,7 @@
</dl><p>This specification is available in the following formats:
<a href=spec.html>single page HTML</a>,
<a href=Overview.html>multipage HTML</a>.
-This is revision 1.3561.
+This is revision 1.3562.
</p>
<p class=copyright><a href=http://www.w3.org/Consortium/Legal/ipr-notice#Copyright>Copyright</a>
© 2009 <a href=http://www.w3.org/><abbr title="World Wide
@@ -3108,7 +3108,17 @@
</div><p>Authors should carefully design such extensions so that when the
attributes are ignored and any associated CSS dropped, the page is
- still usable.</p><h4 id=element-definitions><span class=secno>3.2.4 </span>Element definitions</h4><p class="XXX annotation"><b>Status: </b><i>Last call for comments</i></p><p>Each element in this specification has a definition that includes
+ still usable.</p><p>JavaScript libraries may use the <span>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><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>
+
+ </div><h4 id=element-definitions><span class=secno>3.2.4 </span>Element definitions</h4><p class="XXX annotation"><b>Status: </b><i>Last call for comments</i></p><p>Each element in this specification has a definition that includes
the following information:</p><dl><dt>Categories</dt>
<dd>A list of <a href=#content-categories title="content categories">categories</a> to
Received on Tuesday, 5 January 2010 00:48:07 UTC