Comments on: Scoping XFN and identifying authoritative hcards

By: the blog: tagging isnt just for hoodlums anymore » microformatting: all the cool kids are doing it

Fri, 02 Feb 2007 21:33:21 +0000

[...] trivial but it’s intended to be somewhat forward thinking. With ideas running around like a totally portable url-identity driven social network, and more portable resume formatting (see if you can find me on linked in, by the way), this is [...]

By: John Allsopp

John Allsopp — Tue, 30 Jan 2007 23:52:25 +0000

Chris,

I think self actually suffices for a definitive reference as per the Atom spec from which it is reused by hReview and hAtom.

See my recent post to uf-discuss for more detailed reasoning.

By: Ben Ward

Ben Ward — Tue, 30 Jan 2007 20:19:18 +0000

Well, in my hCard I have ADDRESS elements with it â€” wrapped around each contact address (IM, email and so on). In my experience that's the best that can be done. Whether that's of any help to parsers I'm not sure. It's not as easy to imply meaning about the parent from its children. What's more, rel=me> is relative to the page, so in terms of identifying the definitive hCard for the addressable owner of the page, rel=me implies the relevant part of the same semantic even without ADDRESS.

By: Chris Messina

Chris Messina — Tue, 30 Jan 2007 17:34:05 +0000

Good point. I wonder if simply wrapping the “FN URL” object (linked name) would be sufficient — since at least you’d have the person’s name and URL.

By: Ben Ward

Ben Ward — Tue, 30 Jan 2007 09:39:36 +0000

ADDRESS is of course optimal, but the fact remains that it cannot contain block level elements without triggering quirks mode in browsers, so you couldn't ever mandate it for all hCards.