Comments on: Reflections over Microformats

By: Microformats in Plone — mrtopf.de

Microformats in Plone — mrtopf.de — Mon, 03 Mar 2008 18:38:49 +0000

[...] it pollutes the HTML class namespace and might conflict with CSS class definitions (as it actually happens in Plone). Still, as microformats seem to get popular it makes sense to support [...]

By: Christian Scholz

Christian Scholz — Sun, 10 Feb 2008 12:22:59 +0000

Well, I might need to use "vcard vevent" or "vcard vcalendar" then and I wonder if parser will not have a problem with that because vcard (which is used right now) is also introducing (a different) microformat.

Maybe the best would be to put the vcalendar around the element having the vcard and sort of expecting that a microformats parser will switch to hEvent mode once it encountered a vcalendar element. Then it might be "vcard vevent" later on.

By: Guido Stevens

Guido Stevens — Sun, 10 Feb 2008 11:39:02 +0000

@Sean: I think Christian refers to the scenario where an existing implementation uses class names that turn out to be "reserved words" in the context of a microformat.

This is actually a namespace problem, that has been solved in the XML context by namespace prefixes. You know: "tal:repeat …" and "browser:page …".

If we're going to use HTML classes, to be able to express meaningful semantics in a way that can be parsed and validated, we really need some kind of namespacing mechanism for HTML classes, too, methinks.

By: Sean Upton

Sean Upton — Sun, 10 Feb 2008 06:46:41 +0000

Why is replacement of class names a requirement to use? Why not add multiple classes delimited by spaces to your template/content output?

from class="myoriginalclass" to:
class="myoriginalclass dtstart"