[uf-new] hAudio issue D2 "title"

Martin McEvoy martin at weborganics.co.uk
Mon Sep 1 13:04:02 PDT 2008


Martin McEvoy wrote:
> Hello Tantek
>
> Tantek Celik wrote:
>> Martin,
>>
>> The first option you provide illustrates the fundamental problem with 
>> this issue, which is that the meaning we are trying to express is the 
>> name of the track / hAudio item. Even the iTunes UI refers to the 
>> "Name" (select a track in iTunes, Get Info, click the Info tab, note 
>> the first field).
>>
>> For microformats, we already have a property for the meaning of 
>> "name", and that's "fn". It specifically means "formatted name" but 
>> that simply reflects the fact that it means the name as published (as 
>> it is shown) rather than some abstract structural name, and "as 
>> published" is precisely what we want in microformats since we are 
>> marking up visible content *published* on the web.
>>
>> "fn" is already used to mean name in hCard (from vCard), and for the 
>> names of hReview items and hListing items.
>> Per the naming principle of not introducing two properties for the 
>> same meaning (see wiki/naming-principles ), we should have simply 
>> reused "fn" for this long ago.
>>   
> "fn" was changed to "title" because it was over used in haudio,
>
> haudio title => fn
> haudio contributor = fn
> item title = fn
>
> and what If the author of the audio came first? very messy and uninspired
>
> I will accept however that haudio Items should use "fn" because thats 
> how Item is used in all other Microformats
>
> <div class="item">
> <span class="fn">blah</span>
> </div>
>
> "n" simply wont do either "The name of the unit" what does that mean? 
> it seems deliberately vague to me what is a unit? is it defined in 
> microformats?, sorry Tantek I'm just thinking out loud :-)
>>  
>> In addition, from a process perspective, please use the wiki not 
>> email for brainstorming and opinions on proposals. Tracking this in 
>> email over time is nearly impossible.
>>
>> Please place the options on wiki/audio-brainstorming along with 
>> nested list items for individuals to offer their +/-1 (or 0) opinion 
>> with username and any comments explaining their opinion.
>>   
>
> Done see,  
> http://microformats.org/wiki/haudio-issues#D2:_2008-01-10_Overloading_.22fn.22 
>

oops! sorry changed to 
http://microformats.org/wiki/haudio-issues#D2:_2008-01-10_hAudio_Title_was_Overloading_.22fn.22.

Thanks

Martin McEvoy
>
> Please add your support for any of the resolutions on the page above, 
> or add your own resolution.
>> Thanks,
>>
>> Tantek
>>
>>   
> Best wishes
>
> Martin McEvoy
>> -----Original Message-----
>> From: Martin McEvoy <martin at weborganics.co.uk>
>>
>> Date: Mon, 01 Sep 2008 13:28:15 To: For discussion of new 
>> microformats.<microformats-new at microformats.org>
>> Subject: [uf-new] hAudio issue D2 "title"
>>
>>
>> Hello all
>>
>> I have left this issue until last because this is the longest and 
>> probably the most contentious issue of them all issue D2 hAudio 
>> Title[1] originally  marked as Overloading "fn"
>>
>> The current discussion around  hAudio Title[2] is at the moment that 
>> It can't be used because its already defined in hcard[3] to mean "Job 
>> Title"[4]
>>
>> [1] 
>> http://microformats.org/wiki/haudio-issues#D2:_2008-01-10_Overloading_.22fn.22. 
>>
>> [2] http://microformats.org/wiki/haudio#Title
>> [3] http://microformats.org/wiki/hcard
>> [3] http://www.w3.org/2002/12/cal/rfc2426#sec3.5.1
>>
>> There are currently three possible resolutions:
>> ------------------------------------------------------------------------------------------------------------------------- 
>>
>> Resolution 1:
>>
>> Use "NAME"
>>
>> [...]
>> Name http://en.wikipedia.org/wiki/Name
>> "A name is a label for a human or animal, thing, place, product (as in a
>> brand name) and even an idea or concept, normally used to distinguish
>> one from another. Names can identify a class or category of things, or a
>> single thing, either uniquely, or within a given context."
>> [...]
>>
>> A Proposal was made in an email on March 5th 2008 by Myself.
>> http://microformats.org/discuss/mail/microformats-new/2008-March/001555.html 
>>
>>
>> ------------------------------------------------------------------------------------------------------------------------- 
>>
>> Resoulution 2:
>>
>> Use  "HTITLE"
>>
>> [...]
>> "hTitle can then be reused in any microformat that needs a "title"
>> property. hTitle has been given a root class name as it is intended to
>> be used in conjunction with any other root class microformat and mirrors
>> the association semantics expressed by hfeed => hentry  in hAtom"
>> [...]
>>
>> A Proposal was made in an email on Aug 13th 2008 by Myself.
>> http://microformats.org/discuss/mail/microformats-new/2008-August/001692.html 
>>
>>
>> ------------------------------------------------------------------------------------------------------------------------- 
>>
>> Resoulution 3:
>>
>> Use "AUDIO-TITLE"
>>
>> As tentatively proposed by Manu Spony in an email on Wed Aug 13th 2008
>> http://microformats.org/discuss/mail/microformats-new/2008-August/001692.html 
>>
>>
>> ------------------------------------------------------------------------------------------------------------------------- 
>>
>>
>> If anyone would like to support any of the above resolutions please 
>> add a +1(plus one) to the resolution along with any comments you 
>> would like to add similarly you can add your disapproval and reasons 
>> why with a -1(minus one). Of course If you have another resolution 
>> please reply to this email with your proposal.
>>
>>
>> Best Wishes
>>
>> Martin McEvoy
>>
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> microformats-new mailing list
>> microformats-new at microformats.org
>> http://microformats.org/mailman/listinfo/microformats-new
>>
>> _______________________________________________
>> microformats-new mailing list
>> microformats-new at microformats.org
>> http://microformats.org/mailman/listinfo/microformats-new
>>   
>



More information about the microformats-new mailing list