[Bug 16869] HTML5 is missing mechanism for preventing clashes of vendor-neutral extensions

https://www.w3.org/Bugs/Public/show_bug.cgi?id=16869

--- Comment #8 from Jirka Kosek <jirka@kosek.cz> 2012-05-02 13:41:43 UTC ---
(In reply to comment #7)
> New attributes (prefixed or not) are harmful as they increase the vocabulary
> authors are exposed to and therefore definitely a) require a specification
> (ideally defined in HTML itself) and b) require community recognition for
> validator support.

Hi Anne,

exactly for these reasons I proposed change that introduces new lightweight
registry where for each such vocabulary addition new entry including link to
specification will be created. Only those recognized vocabularies are going to
be added into registry. Wasn't this clear enough from my proposal?

Anyway there seems to be sort of egg & chicken problem.

Should we first create our own spec relying on its-* attributes, create
implementations and then eventually try to change HTML5 spec to allow such
attributes as valid? Or should we first change HTML5 spec to provide
infrastructure for defining such vocabulary additions?

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Wednesday, 2 May 2012 13:41:49 UTC