9239 2010-03-13 06:36:34 +0000 specify a convention for preventing vendor-specific non-standard extensions from clashing with themselves and future standard development 2010-10-04 14:56:34 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified PC All RESOLVED FIXED NE P3 normal --- 1 ian ian ayg ian mike mjs public-html-admin public-html-wg-issue-tracking rubys public-html-bugzilla oldest_to_newest 32927 0 ian 2010-03-13 06:36:34 +0000 We should specify a convention for preventing vendor-specific non-standard extensions from clashing with themselves and future standard development, similar to CSS vendor-specific extensions. 32945 1 mike 2010-03-14 12:15:46 +0000 Is this about element names, or attribute names, or both, or neither? 33611 2 mike 2010-03-16 05:27:36 +0000 see Rob Ennals related change proposal: http://www.w3.org/html/wg/wiki/ChangeProposals/fixedprefixsimple 34348 3 ian 2010-04-01 23:20:29 +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: Accepted Change Description: see diff given below Rationale: Concurred with reporter's comments. 34349 4 contributor 2010-04-01 23:20:33 +0000 Checked in as WHATWG revision r4939. Check-in comment: Include some advice on how to do experimental non-standard attributes. http://html5.org/tools/web-apps-tracker?from=4938&to=4939