RE: <spoiler> element

What on earth are you talking about?

Mark Birbeck
CEO
x-port.net Ltd.

e: Mark.Birbeck@x-port.net
t: +44 (0) 20 7689 9232
w: http://www.formsPlayer.com/

Download our XForms processor from
http://www.formsPlayer.com/  

> -----Original Message-----
> From: www-html-request@w3.org 
> [mailto:www-html-request@w3.org] On Behalf Of Jukka K. Korpela
> Sent: 07 December 2005 10:39
> To: www-html@w3.org
> Subject: RE: <spoiler> element
> 
> 
> On Wed, 7 Dec 2005, Mark Birbeck wrote:
> 
> > On the *semantic* side of this, the purpose of @role is to provide 
> > features that may be an absolute necessity in one domain but 
> > completely irrelevant in another. So rather than having to 
> fight over 
> > them on the list all the time, each sphere that is using 
> XHTML 2 can 
> > add whatever they like. :)
> 
> It sounds like you're saying, in effect, that the role 
> attribute is included since it helps to avoid discussing and 
> solving problems.
> 
> I fail to see the difference between that and saying that 
> everyone and each "domain" (area of application) can use 
> extra attributes and tags to supplement the XHTML soup. Well, 
> there is a formal difference, and a technical difference too.
> 
> To apply similar strategy to _elements_, we could add, say, 
> the <dwim> element in XHTML 2.0, with a required attribute 'means'
> which contains the semantics in some formalism. Oops, we 
> already have <span> and <div>, and 'role' is shorter than 
> 'means' (so let's ignore its obscurity).
> 
> --
> Jukka "Yucca" Korpela, http://www.cs.tut.fi/~jkorpela/
> 
> 
>

Received on Wednesday, 7 December 2005 11:23:49 UTC