The CanonicalID Approach

[Recordon, David]

Hey Johnny,
My understanding, though don't have the appropriate spec reference, is
that the process would be:

1) User enters http://daveman692.livejournal.com
2) RP fetches Yadis doc for http://daveman692.livejournal.com
3) RP sees <CanonicalID> of
http://www.livejournal.com/userinfo.bml?userid=1356357
3) RP fetches Yadis doc for
http://www.livejournal.com/userinfo.bml?userid=1356357
4) RP sees <CanonicalID> of
http://www.livejournal.com/userinfo.bml?userid=1356357 is itself
5) RP sees <Ref> of http://daveman692.livejournal.com and thus has
verified that the pointer goes in both directions

Will have to ask Drummond his thoughts on how fragments would be used,
since this morning it isn't clear to me.

--David

-----Original Message-----
From: Johnny Bufu [mailto:johnny at sxip.com] 
Sent: Friday, June 08, 2007 10:42 AM
To: Recordon, David
Cc: specs at openid.net
Subject: Re: The CanonicalID Approach

Hi David,

On 7-Jun-07, at 6:31 PM, Recordon, David wrote:

> You could also, don't shudder too hard Dick :), use an i-number
> as your persistent identifier via this method though on the flip-side
> could also use a fragment if that is the approach someone would  
> like to
> take.
>
> The nice thing is that this method is extremely flexible in terms of
> what you use as your persistent identifier in different cases.

The question (that we will need to specify or have a clear pointer  
to) is how the canonical ID verification is done. (BTW: Was this  
section updated on Wed in the XRI draft?)

Your HTTP URL canonical ID example is straight-forward and simple. Do  
you have an example of how it would work with fragments, say:

http://openid.aol.com/daveman692 - reassignable
http://openid.aol.com/daveman692#1234 - persistent


Thanks,
Johnny