- From: Simone Onofri <simone.onofri@gmail.com>
- Date: Wed, 14 Feb 2007 16:36:26 +0100
- To: "Steven Pemberton" <steven.pemberton@cwi.nl>
- Cc: "Ben Adida" <ben@adida.net>, "Ivan Herman" <ivan@w3.org>, "Hausenblas, Michael" <michael.hausenblas@joanneum.at>, RDFa <public-rdf-in-xhtml-tf@w3.org>, "SWD WG" <public-swd-wg@w3.org>, www-qa@w3.org
So, Using class with semantic meaning, this overload the current use of @class. Well: - Use for style in CSS - Use for semantics in Microformats (and also eRDF and more) So, if we use on a single page also more dialects we can have: ... class="mystile first-dialect second-dialect" ... and this is not clear also for humans and create more confusion also for machines. It's a good idea use only "namespaced" class but if we can use a specific @attribute for semantic layes, this should be the best choice. Simone > On Wed, 14 Feb 2007 14:39:16 +0100, Ben Adida <ben@adida.net> wrote: > > > Ivan Herman wrote: > >> +1 > >> > >> Steven Pemberton wrote: > >>> I want to reraise my position: leave class alone, and use something new > >>> for what we want. I still have the feeling that @role can do the job. > > > > There is a *huge* lost opportunity if we do this, which is that we don't > > show a natural progression from microformats to RDFa. Microformats > > already use the CLASS attribute for this kind of thing, and it's a well > > accepted practice. New attributes should be used sparingly. > > > > -Ben
Received on Wednesday, 14 February 2007 15:36:34 UTC