[uf-new] hAudio issue D2 "title"

David Janes davidjanes at blogmatrix.com
Mon Sep 1 17:21:15 PDT 2008

On Mon, Sep 1, 2008 at 7:34 PM, Tantek Celik <tantek at cs.stanford.edu> wrote:
> Martin,
> I agree with you that this is a larger issue impacting existing and new microformats, however, trying to come up with new names for the same meaning is not the answer, and will quickly fall apart.
> We likely need to come up with scoping rules for all microformats like (just thinking out loud here, please do not implement) - some options:
> 1. any class name starting with an "h" should be treated as a root microformat which introduces a new scope
> 2. introduce a root microformat classname like "hroot" or "hitem" which introduces a new scope and require its use in addition to any new microformat root class name (eg class="hitem haudio") this is essentially the mfo solution but with a friendlier generic root name. Feel free to brainstorm additional friendly generic root names.
> 3. same as 2 except don't introduce any other root microformat-specific class names, and use some other mechanism to specify what type/kind of microformat the item is. E.g. all new microformats would start with class="hitem" and then we come up with another way of "typing" them.
> 4 ... ? Additional suggestions?

The idea I've been kicking around in my head is to use "hitem" in
tandem for "top level" microformats, and then allowing "item" ... if
needed ... for scoping subparts within if needed. I'll add something
to the Wiki tomorrow [1] as it's bedtime for new schoolkids.

Regards, etc...

[1] http://microformats.org/wiki/item

David Janes
Mercenary Programmer

More information about the microformats-new mailing list