[uf-new] An argument against 'fn' in hAudio

Manu Sporny msporny at digitalbazaar.com
Tue May 8 12:20:19 PDT 2007

Brian Suda wrote:
>> None of this applies to hAudio - and we don't want Microformat
>> implementors confusing how to use 'fn' in hAudio and how to use 'fn' in
>> hCard.
> --- these are two very different things. This is a non-issue. hCard
> parsers do onething, and you can defined Media parsers to do something
> completely different. FN is just a semantic value not defining parsing
> instructions, that is up to the format.

You almost had me convinced until you said this. It seems very strange
to me that something that is supposed to be 'semantically equivalent' is
parsed in very different ways between two Microformats.

If things are semantically equivalent, why aren't they parsed in the
exact same way?

To illustrate the implications of calling two things the same thing when
they are different:

Here's a duck, it quacks and floats on water. Here's another duck, it
whinnies and gallops on land.

If two things have to be parsed in different ways, how can they be
semantically equivalent?

I would have no problem with using 'fn' if it didn't have all of the
parsing cruft from hCard. If something is parsed differently, isn't it
intrinsically different?

-- manu

More information about the microformats-new mailing list