Hello.
Not so long ago some of you may remember an interesting discussion[1]
about the proposal to replace "fn" with "title" in hAudio[2] the result
being "fn" was changed to "title".
I was one of the people supporting this proposal, my reason being that a
title property has been "discovered" and its not the same as "title"
(job title) in hcard and is also needed for many proposed or existing
microformats such as...
Recipes [3]
Books [4]
Products [5]
Videos [6]
Art [7]
Job Listings [8]
Citations [9]
There three Main reasons why hAudio and all the above proposed
microformats can't realistically use "title"
1, Its already been defined as "Job Title" in hcard
2, It breaks some microformats naming principles such as "Ignoring all
earlier work" and "Using others' names to mean different things"
3, It Breaks meta data profiles(xmdp)[10], because if you do include
meta-data profiles in the head of your document and you have both a
haudio and hcard profiles and you have markup that looks like
this....(real markup from a future project)
<div class="haudio">
<span class="title">A broadcast to the Nation</span>,
<span class="category">speech</span> by
<span class="contributor">
<span class="vcard">
<span class="title">Sir</span>,
<span class="fn n">
<span class="given-name">Winston</span>
<span class="family-name">Churchill</span>.
</span>
</span>
</span>
<span class="description">
An encouraging military, economic and political assessment of the
first ten weeks of war.
</span>
Recorded on <abbr class="published" title="1939-11-12">November 12,
1939</abbr>
</div>
Only the FIRST discovered Title definition will be used , in this case
its a haudio title, which is wrong when it comes to the title in the
hcard because it will be defined as a haudio title
So a resolution use *htitle* definition:
"What is to be used as a title for the object. Contents are a short
textual description used to identify the object among interested parties."
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[11]
The most desirable thing about a htile microformat is that we dont have
to invent new names that mean the same thing such as recipe-title,
book-title, product-title etc... they can all use just one.
[1]
http://microformats.org/discuss/mail/microformats-new/2008-February/001468.html
[2] http://microformats.org/wiki/haudio
[3] http://microformats.org/wiki/recipe-examples
[4] http://microformats.org/wiki/book-info-formats
[5] http://microformats.org/wiki/product-examples
[6] http://microformats.org/wiki/video-info-examples#Properties
[7] http://microformats.org/wiki/workofart-brainstorming#Proposals
[8] http://microformats.org/wiki/job-listing-examples
[9] http://microformats.org/wiki/citation-examples
[10] http://gmpg.org/xmdp/
[11] http://microformats.org/wiki/hatom
Thanks all
Martin McEvoy
_______________________________________________
microformats-new mailing list
[email protected]
http://microformats.org/mailman/listinfo/microformats-new
