> I don't see how a class could "describe" an element (for UAs, not authors).
> If there was a known convention on possible values, then I'd agree to say
> that it could convey information (other than style), but AFAIK this is not
> the case.
> I may be missing something though, so I'd be happy to "hear" what others
> think about this...
Short and hefty:
http://code.google.com/webstats/2005-12/classes.html
:-)
It's not that it's supposed to be, it's allready reality. (hey this is a rime)
Not really, however you are right that some class names can be a lot
more than originally meets the eye. Enter Microformats:
http://microformats.org/
"footer" being the most used class on the google stats shows that when
it comes to semantics a lot has to be learnt still. A class, by
definition is something that can appear more than once on the page,
while an ID defines a unique element. How many footers would you use
on a page?
******************************************************
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list & getting help
******************************************************
