Good summary, though: Steven Pemberton wrote: > > Let me try and summarise the positions as I see them > > For class: > Used by microformats in a similar way > HTML Spec allows it > Already there, no new attribute > Implementations already using it > > Against class: > Special rule for namespaced/non-namespaced values > Confusion/objection by/upset for current class users > Used by microformats in a similar way >
I am not sure why this would be counted as a counter argument... > For role: > Clean start, no legacy > No special namespace-prefix rules; can use default namespace rules. > > Against role: > Potential conflict with WAI use of role needs to be resolved > My question: is the WAI the only possible conflict? What will be the future evolution of @role in XHTML2? Is this predictable? > For yet another attribute: > Clean start, no legacy > No special namespace rules > > Against yet another attribute: > Yet another attribute > :-) > Steven > -- Ivan Herman, W3C Semantic Web Activity Lead URL: http://www.w3.org/People/Ivan/ PGP Key: http://www.cwi.nl/%7Eivan/AboutMe/pgpkey.html FOAF: http://www.ivan-herman.net/foaf.rdf
smime.p7s
Description: S/MIME Cryptographic Signature
