There is a list of current classes on the wiki, though being able to
insert rel values is also important:
http://microformats.org/wiki/existing-classes
On Oct 5, 2006, at 10:22 PM, Chris Messina wrote:
This kind of delves into the "authoritative standards" doesn't it? And
how do you keep up with an ever-growing repository of microformats?
Obviously it can be done -- and it's something that we need,
especially if we're to get support for microformats into client-side
software... so isn't that where remote definitions/profiles come in?
Sorry for showing my ignorance here, but how would, for example,
Flock, (or better, Lucene) stay up-to-date with the most current
listing/definitions of all the available microformats?
Chris
On 10/5/06, Matt Augustine <[EMAIL PROTECTED]> wrote:
Yes, this is currently the case. We are working on a solution,
although I can't make any specific commitments.
>From what I've gathered, one of the reasons that some blogging
platforms strip class attributes is to prevent users from marking up
posts in a manner that uses existing CSS definitions to alter the
layout of the page, hide ads etc. One solution we've discussed is to
create a white list of known microformat classes and to allow them.
What do you all think about this? Any other suggestions?
_______________________________________________
microformats-discuss mailing list
microformats-discuss@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
