Question for LID & TypeKey with Yadis identification

[Johannes Ernst]

> I have two question for Yadis working with LID and TypeKey.

Let me try and answer the first one. I don't know the answer to the  
second one.

> 1.
> UA gives Yadis URL to RP, like this:
>        http://example.com/myid
>
> And RP finds Yadis Resource Descriptor, which shows:
> <xrds:XRDS>
>   <XRD>
>     <Service>
>       <Type>http://lid.netmesh.org/sso/2.0</Type>
>       <URI>http://mylid.net/myid</URI>
>     </Service>
>   </XRD>
> </xrds:XRDS>
>
> This case, needless to say RP can identify UA by interacting with
> http://mylid.net/myid on LID protocol.
> But, RP should identify UA as :
>   a. http://example.com/myid
>   b. http://mylid.net/myid
> which is correct?

Chances are that if the user entered  http://example.com/myid, they  
wanted this to be the URL that is being displayed visually. (just  
like the OpenID convention)

> If case a. is correct, Yadis protocol can work like OpenID's delegate
> specification with LID.
> Is this true?

Yes. That was one of the use cases we all wanted to support from the  
very Yadis beginning. Now we got more, because each Yadis service can  
have its own service endpoint, so Yadis is actually substantially  
more flexible than either LID or OpenID were before.

Johannes Ernst
NetMesh Inc.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: lid.gif
Type: image/gif
Size: 973 bytes
Desc: not available
Url : http://lists.danga.com/pipermail/yadis/attachments/20060306/b5b1339b/lid-0001.gif
-------------- next part --------------
  http://netmesh.info/jernst