[uf-new] Re: hAudio FN or Title
andy at pigsonthewing.org.uk
Sat Feb 2 11:54:46 PST 2008
In message <47A4C290.5000306 at digitalbazaar.com>, Manu Sporny
<msporny at digitalbazaar.com> writes
>Martin McEvoy wrote:
>> On Fri, 2008-02-01 at 22:09 , Andy Mabbett wrote:
>>> The more I consider this, the more I am convinced that class names
>>> should not be shared between microformats.
>> For what its worth I think you may be right for example "fn" was only
>> used in hcard this meant just the name of a person or organization,
>> great stuff powerful and clearly defined. hAudio and hreview re-use "fn"
>> to mean other things too, haudio it means, a title of a playlist, album,
>> or track and the name of a contributor or organization
>This is the start of an argument for namespaces:
While namespaces are one possible solution, this is not necessarily an
argument for that solution to be employed.
>Andy, Martin - are you proposing 'context-aware vocabularies' or
>something similar to that?
I don't know what you mean by that term.
>there is no need to pull in the entire Dublin Core metadata vocabulary
>set. For example, all we would need to pull in for hAudio would be 'dc-
>title' at this point. That or we would need to be allowed to use
>'title' for hAudio, since that is the word that makes the most amount
>of sense for what we are describing.
I think we should be warn of conflating two different issues:
1 A microformat, or microformat-like system, for marking up DC
metadata in published content; about which I wrote yesterday:
2 Re-using terms from DC, as a "deciding vote", when there is no
obvious choice among several possibilities, as with the current
debate around hAudio.
* Say "NO!" to compulsory UK ID Cards: <http://www.no2id.net/>
* Free Our Data: <http://www.freeourdata.org.uk>
* Are you using Microformats, yet: <http://microformats.org/> ?
More information about the microformats-new