Re: 'role' should be property

I am pretty sure the whole thing is a horrible idea. Not only the
separation of concerns is compromised, but think about it: in order to
understand semantics of an HTML document, you'll also need to parse
the stylesheet. Now you're doubling the effort for non-browser user
agents. Semantics should stay in the markup and certainly not require
additional documents to parse in order to understand the meaning of
the document.


On 5/23/07, Dannii <> wrote:
> On 5/23/07, Philip Taylor (Webmaster) <> wrote:
> >
> > Isn't the reason simply that CSS = CSS = "Cascading Style Sheets",
> > a medium through which to express /style/ (which is inherently
> > presentational) ?  You could posit (say) CWS (Cascading whatever
> > sheets) that have the same syntax as CSS but which allow aspects
> > other than style to be defined, but by conflating dissimilar ideas
> > you would weaken both ...
> >
> I like this idea. Microformats/roles/whatever all seem to require a lot of
> extra markup, whatever type it ends up being. If you plan to style the
> content as well as express it's meaning you can end up with lots of
> attributes.

Received on Wednesday, 23 May 2007 12:48:45 UTC