9828 2010-06-02 03:35:43 +0000 Update "Embedding custom non-visible data" with guidance for library authors to avoid naming collisions 2010-10-04 14:45:21 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified All All CLOSED FIXED http://dev.w3.org/html5/spec/elements.html#embedding-custom-non-visible-data P2 normal --- 1 adrianba ian ian mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 35899 0 adrianba 2010-06-02 03:35:43 +0000 Based on the conversation between Tony and Jonas at: http://lists.w3.org/Archives/Public/public-html/2010May/0034.html Suggest that the text at the end of the section "Embedding custom non-visible data" be changed to: JavaScript libraries may use the custom data attributes, 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. Library authors are also encouraged to make their name customizable by the page author in order to resolve clashes between libraries (including different versions of the same library). For example, a library called "DoQuery" could use attribute names like data-doquery-range, and a library called "jJo" could use attributes names like data-jjo-range. The “jJo” library could also provide clash resolution through an API call like jjo.setDataPrefix("jjo2"), after which the previous example would change to data-jjo2-range. [The last sentence of each paragraph is new.] 37365 1 ian 2010-08-11 21:14:40 +0000 This seems reasonable in principle. I'll look at it more carefully once I'm back to going through the bugs (I'm dealing with the backlog of e-mails first, since some had been waiting for far too long). 39218 2 ian 2010-09-23 17:36:17 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Partially Accepted Change Description: see diff given below Rationale: I added equivalent sentences, though not quite using the same phrasing. 40263 3 adrianba 2010-09-30 18:59:12 +0000 Thanks.