[uf-new] Microformats parsing, in general (was: hAudio final draft)

David Janes davidjanes at blogmatrix.com
Sun Jun 17 11:55:59 PDT 2007

On 6/17/07, Manu Sporny <msporny at digitalbazaar.com> wrote:
> David, I was under the same false assumption. Microformats are
> scope-less. There is no such thing as scope and binding... the only
> thing that matters is the order that the Microformat elements are listed
> on the page.
> Here's some markup to demonstrate:
> haudio
> * hreview
> ** reviewer
> *** vcard
> **** fn  <---- the reviewer's name is used as the title for haudio
> * fn <---- this is ignored by any Microformat-compliant parser
> The parser would perform the following steps:
> 1. haudio detected
> 2. find elements for haudio
> 3. find name of audio recording (search for 'fn')
> 4. 'fn' found in haudio/hreview/reviewer/vcard/fn *OOPS!*
> 5. hreview detected
> 6. find elements for hreview
> 6. reviewer detected
> 7. find name of reviewer in vcard (search for 'fn')
> 8. reviewer's name found in vcard/fn
> 9. superfluous 'fn' detected, ignore 'fn'. *OOPS!*

Has this been articulated anywhere on the Wiki? For example, it's not
here [1]. I'm not agreeing or disagreeing with this, but I haven't
quite seen this listed so clearly.

Note that this causes a conflict with the microformats naming
principles [2]. That is, let's assume for argument's sake that "fn" is
the best thing to use for Audio Title. Under the rules Manu gives,
"fn" isn't available for use (unless "item" or similar is injected, as
mentioned earlier in this thread)

Regards, etc...

[1] http://microformats.org/wiki/parsing-microformats
[2] http://microformats.org/wiki/naming-principles

David Janes
Founder, BlogMatrix

More information about the microformats-new mailing list