On Fri, Feb 15, 2008 at 12:24 AM, Manu Sporny <[EMAIL PROTECTED]> wrote:
> Yes, you are correct. Usually, each Microformat states how this should > be handled. So far, the general parsing rule has been "use whatever > value you hit first if the Microformat can only have one value for the > given property". While the example above shows it going right, the > example below shows how it can go wrong: > > <div class="haudio"> > <div class="vcard"> > The <span class="title">Composer</span> named > <span class="fn">Bob</span> created > <span class="title">Awesome Song</span> > > </div> <!-- end vcard --> > </div> <!-- end haudio --> ... > Every time you overlap two Microformats that share a common property, > you could have this issue. That shouldn't scare us off from re-using > common properties, though! Thank you for the example. You are right, it doesn't scare me from using it, just something for those that write parsers to worry about. > > 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. > > So, does that mean you're a +1 for using TITLE over FN in hAudio as well? Absolutely +1 (can I be +10?) Tim _______________________________________________ microformats-new mailing list [email protected] http://microformats.org/mailman/listinfo/microformats-new
