On Thu, Feb 14, 2008 at 2:55 PM, Manu Sporny <[EMAIL PROTECTED]> wrote: .... > We're not trying to boil the oceans here - there will always be corner > cases that won't fit into Microformats... that's why we have the 80/20 rule. > > You still haven't addressed what is being broken? What will stop > functioning as a result of us using TITLE in both hCard and hAudio? > > -- manu
This is the same problem that the citation efforts ran across. Following the microformats process, I helped collect *existing* examples of how books are marked up on the web. If you look (and I know Brian helped formulate this) at the results, TITLE gets used quite often. [1] The same argument was made back then: "hCard came first so you can't reuse TITLE." What if citation or hAudio came first? Would the same argument be made? Would hCard have been prevented from using TITLE? Somehow I doubt it (yes, complete supposition on my part, made only because hCard is based on vCard which uses TITLE and that is the prior art issue that is holding this up). We need to resolve this because, as Manu points out, it will continue to happen. I don't write parsers or pretend to know how to, but... (yes, here I go again) it seems to me that if you have this: <div class="hAudio"> <span class="title">Name of Album</span> <div class="vcard"> <span class="fn">Bob</span>, <span class="title">Composer</span> </div> <!-- end vcard --> </div><!-- end haudio --> the parser should be able to determine that the "title" contained directly inside "haudio" is an album name and that the "title" nested inside "vcard" inside "haudio" belongs to the vcard and not haudio. I'm sure cases exist (or could exist) where it won't be this simple, but shouldn't this cover the 80%? Certainly if we agree that microformats are a way to extend meaning to content, TITLE is much more meaningful (and easier for authors to adopt) than FN. I'm tired and sick, so I hope this makes sense. Tim [1] http://microformats.org/wiki/citation-examples-markup _______________________________________________ microformats-new mailing list [email protected] http://microformats.org/mailman/listinfo/microformats-new
