Re: [uf-new] Re: hAudio issue: position
Andy Mabbett wrote: Items 1-5 have different meanings; that's why you were able to list fire items, not just one. How would you mark up position in: At number two in the chart this week is Pink Floyd's Fearless, track 3 on their Meddle album. Or, rather, which of the two different kinds of position would you mark up? Andy - could you please list the issues that you have with hAudio on the audio-info-issues page so that we can track them. I remember seeing 3 distinct issues that you raised in the past month (although, there may be more). I've been meaning to document them for several weeks, but haven't gotten around to doing so. You'd be the best person to word it in a way that you agree with: http://microformats.org/wiki/audio-info-issues -- manu ___ microformats-new mailing list microformats-new@microformats.org http://microformats.org/mailman/listinfo/microformats-new
Re: [uf-new] Re: Namespace anti-pattern and hAudio TITLE (was: hAudio FN or Title)
On Sun, 2008-02-03 at 14:31 -0500, Manu Sporny wrote: FN doesn't mean anything useful until it is wrapped by a Microformat - hCard, or hAudio, for example. This means that the wrapping Microformat brings context into the equation. The same as if we use title outside of hcard IT doesn't mean anything useful, wrap it in haudio the function of the object title would then become an audio title, nothing at all to do with hcard? Thanks Martin McEvoy ___ microformats-new mailing list microformats-new@microformats.org http://microformats.org/mailman/listinfo/microformats-new
Re: [uf-new] Re: Namespace anti-pattern and hAudio TITLE (was: hAudio FN or Title)
On 2/3/08 11:31 AM, Manu Sporny [EMAIL PROTECTED] wrote: Martin McEvoy wrote: I think he means Context-Aware I And to answer Manu's no I don't think its necessary, Microformats already ARE context aware? Yes! This is my point exactly. If Microformats ARE context aware, then there is the concept of namespaces in Microformats. Namespaces are NOT an anti-pattern afterall. Manu, context is not the same as namespaces. namespaces provide one form of context, but not all contexts are namespaces. in the case of compound microformats, the context that is used is hierarchical containment. fn *does* have meaning - it means formatted name. Inside an hCard it means the formatted name of either a person, organization, or location (depending on the specifics of the hCard). Inside an hReview item it means the formatted name of an item. So, who is going to make an argument against using TITLE in hAudio? The problem of such use of the term title is twofold. 1) it's already used to mean job title in the context of microformats. 2) the concept that it is being proposed to represent is the *name* of an audio item. fn already means the name of an item. we should not introduce a new term to mean the same thing as an existing term. Tantek ___ microformats-new mailing list microformats-new@microformats.org http://microformats.org/mailman/listinfo/microformats-new
