- From: Steve Faulkner <faulkner.steve@gmail.com>
- Date: Mon, 18 Feb 2013 09:49:08 +0000
- To: Robin Berjon <robin@w3.org>
- Cc: HTMLWG WG <public-html@w3.org>
- Message-ID: <CA+ri+VkaAAjgdKR=KnYyQwOixC47Tpp8uUz9+La27nigVAhGLw@mail.gmail.com>
Hi Robin, >We made a promise that data-* is an extension point. My understanding is that we're also committed never to standardise an element or attribute name with a >dash in it (again, extensibility promise). So it would certainly be a bad idea to hijack data-* for something we put in the standard. cool, good to know. >I'm not sure what you're trying to do exactly, but it looks to me like you'd want a subrole attribute? sounds like it. regards Steve On 18 February 2013 08:55, Robin Berjon <robin@w3.org> wrote: > On 18/02/2013 08:26 , Steve Faulkner wrote: > >> NOTE: this is just a wild idea. >> >> allow the data attribute [1] to be used to identify element sub >> roles: >> >> examples: >> >> <h1>heading</h1> <p data-p="subheading">**subheading</p> >> >> >> <article data-article="comment"> blog post comment </article> >> >> allow data-elementname="subRole" pairs to be added to a public >> registry. >> >> thoughts? >> > > We made a promise that data-* is an extension point. My understanding is > that we're also committed never to standardise an element or attribute name > with a dash in it (again, extensibility promise). So it would certainly be > a bad idea to hijack data-* for something we put in the standard. > > I'm not sure what you're trying to do exactly, but it looks to me like > you'd want a subrole attribute? > > -- > Robin Berjon - http://berjon.com/ - @robinberjon >
Received on Monday, 18 February 2013 09:50:21 UTC