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. > > > > -BenReceived on Wednesday, 14 February 2007 15:36:58 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:17:28 GMT