In my experience, from a practical point of view, it's not really
needed - even if no microformats had any property names in common,
parsers still need to take care over microformat opacity due to
situations like:
<div class="vcard">
<div class="agent vcard">
<span class="title">...</span>
</div>
</div>
And it doesn't seem to have proved a problem for 'url', which is
defined fairly differently in RFC 2426 (vCard) and RFC 2445
(iCalendar). 'contact' also has different meanings in hCalendar and
XFN (though of course, one is a class and one a rel).
This seems to be a solution to a problem which doesn't exist.
A better issue to debate would be how to resolve problem that XMDP
knows nothing about nesting, making it a blunt tool to define the
meanings of properties within compound microformats.
--
Toby A Inkster
<mailto:[EMAIL PROTECTED]>
<http://tobyinkster.co.uk>
_______________________________________________
microformats-new mailing list
[email protected]
http://microformats.org/mailman/listinfo/microformats-new
