[uf-discuss] Authoritative hCards [was RE: Canonical hCards (was:
Search on CSS element)]
john at westciv.com
Mon Jan 29 17:50:41 PST 2007
> For my money, John Allsopp's idea to reuse rel="bookmark self" 
> makes most sense. As well as being gorgeously consistent with other
> existing microformats, it's also a completely graceful addition to
> existing hCards.
There's a lot of goodness to reuse from other ufs, for sure.
> The only concern I can see to check is if this would conflict with
> and break the parsing of hAtom/hReview that already use those rel
> values in combination?
When rel-license is inside an hReview, it is taken to be associated
with the review, rather than the larger fragment it would otherwise
be associated with (e.g. post or page)
I wonder whether that makes sense more generally - things apply at
the finest level of granularity at which it mkes sense - so
rel="bookmark self" applies to the microformatted content it is most
directly descended from.
Are there reasons people think this is a bad idea?
An analogy again is categories in hAtom
You can have either feed categories or entry categories. Both are
encoded using rel-tag. The difference is that entry categories are
inside the hentry element, while feed categories are in the hFeed
element (but not in the hEntry element). The point is that hEntry
elements descend from hFeed elements, so all entry categories are
inside an hFeed element.
Indeed, Brian Suda, Michael Kaply, or someone else who does a bit of
parsing might weigh in on whether or not this is an implicit
assumption they make more generally with their parsers, or whether it
might become an explicit convention - to try and formulate it (badly)
"where a feature of microformats may apply to more than one element
in a descendent tree, it is associated with the element which most
directly contains it ."
> It would take the guesswork out of parsing, whilst publishing
> useful information. Additionally, what do people think to
> situations where an hCard contains a A/@REL="bookmark self" but not
> @class=url? The use case being when I don't regard my /about page
> as being a relevant URL for inclusion in my hCard parsing, but do
> wish to have it followed and parsed as the authoritative version.
Not sure whether this is straying into the 20% part of the problem
space? Just my initial response, with little real thought ;-)
More information about the microformats-discuss