On Feb 8, 2007, at 2:23 PM, David Janes wrote:
On 2/8/07, Scott Reynen <[EMAIL PROTECTED]> wrote:
So as I understand that, the rules for getting the most authoritative
hCard for a given URL are:
1) parse hCard at current URL
2) If the hCard includes <a class="uid url">, load the URL in the
href, and return to step 1.
When the consumer gets to http://theryanking.com/blog/contact/#vcard
and finds no <a class="uid url">, it stops there and that's his
authoritative hCard.
OK (and I'm not trying to turn into Andy here), but doesn't this feel
at least a little unsatisfactory? That the authoritative hCard is the
one that _doesn't_ have a UID, i.e. potentially has less information
than a fragment hCard?!
I just thought of another base case in the recursive algorithm
if the uid of the current hcard equals that of the previous, you're
done.
I'm not killer against the idea or anything, but at least I think that
should be brought up.
I agree, what I'm proposing does less than what you proposed. But, I
think we need to solve this simpler problem first.
Here's one potential usage snag:
- I copy the hCard at http://theryanking.com/blog/contact/#vcard to my
"address book"
- I use it somewhere (to refer to Ryan King)
- It doesn't have a UID, so there's no tracing it back to source
Sure, that would be unfortunate, but with the addition of the second
base case (see above) it would be solved.
-ryan
--
Ryan King
[EMAIL PROTECTED]
_______________________________________________
microformats-discuss mailing list
[email protected]
http://microformats.org/mailman/listinfo/microformats-discuss
