<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
The first XRD in my example is the "User Discovery" XRD in Dirk's post.
<br>
I am talking about what to use for <rel> URI here. <br>
In XRI TC's discussion, we disccussed that it probably is not right to <br>
use the same URI for both "User Discovery" document (which defines <br>
relationship, "Relationship URI") and "Provider Discovery" (which
defines the service). <br>
I suppose Dirk is using the same URI just for the lack of this
"Relationship URI". <br>
<br>
Also, in Dirk's example, in User Discovery, he is siting <br>
<URI><a class="moz-txt-link-freetext" href="http://openid.example.com/op">http://openid.example.com/op</a></URI><br>
<br>
I suppose this is somewhat misleading. <br>
I suppose it should be <br>
<br>
<URI><a class="moz-txt-link-freetext" href="http://example.com/#">http://example.com/#</a><URI><br>
<br>
(Note: I have added # to denote that it is pointing to a non
information resource. <br>
As it is a non-information resource, the matching information resource
has to be <br>
discovered by some other protocol, such as LRDD/site-meta.)<br>
<br>
As to the Provider Discovery is concerned, there is no <Host> in
the latest XRD schema. <br>
It is unified with <Subject>. How to express the "Subject Set" or
entire domain is <br>
still under discussion, I believe, in site-meta discussion. The last I
have seen is <br>
something like: <Subject>site-meta://example.com</Subject>.
<br>
Personally, I do not like it. (W3C people will not either, I think.) <br>
What some XRI TC people suggested was to use something like <br>
<Subject><a class="moz-txt-link-freetext" href="http://example.com/#">http://example.com/#</a></Subject> as in AWWW, but
this is something <br>
that should be discussed in another thread. <br>
<br>
What I was referring to as "not sure" was whether we need to support
all types of LRDD <br>
or just one, for OpenID. I have got an opinion on that but I am
intending to start <br>
yet another thread for that. (Or somebody else can do so. I am rather
time constrained.) <br>
<br>
I think it is a good practice to separate those threads and concentrate
on one issue <br>
per thread so that we can avoid drifting discussion. <br>
<br>
This thread is only about the Relationship URI. <br>
<br>
=nat<br>
<br>
<br>
Santosh Rajan wrote:
<blockquote
cite="mid:b6b112650909022127j67927124u99ffd7049679f88c@mail.gmail.com"
type="cite">There is an article posted here related to this.
<div><a moz-do-not-send="true"
href="http://www.hueniverse.com/hueniverse/2009/09/openid-and-lrdd.html">http://www.hueniverse.com/hueniverse/2009/09/openid-and-lrdd.html</a></div>
<div><br>
</div>
<div>So how does this work in the above framework?</div>
<div><br>
<br>
<div class="gmail_quote">On Thu, Sep 3, 2009 at 9:26 AM, Nat Sakimura
<span dir="ltr"><<a moz-do-not-send="true"
href="mailto:n-sakimura@nri.co.jp">n-sakimura@nri.co.jp</a>></span>
wrote:<br>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">So,
User's XRD would have something like<br>
<br>
<xrd id="foo"><br>
<Subject><a moz-do-not-send="true" href="http://sakimura.org/nat"
target="_blank">http://sakimura.org/nat</a></Subject><br>
<ds:Signature> ... </ds:Signature><br>
<link><br>
<rel><a moz-do-not-send="true"
href="http://openid.net/rels/myopenid_provider" target="_blank">http://openid.net/rels/myopenid_provider</a></rel><br>
<url><a moz-do-not-send="true" href="http://myopenid.net/"
target="_blank">http://myopenid.net/</a></url><br>
</link><br>
</xrd><br>
<br>
This is fetched during the discovery. (I am still not so sure about<br>
the relationship between X-XRDS-Location: header and site_meta etc.<br>
Are we abandoning the header model?)<br>
<br>
Then, the RP searches for my relationship with OP through <rel>.<br>
Once it was found, the RP goes to the url specified in the <link>
to<br>
get the Service's XRD like:<br>
<br>
<xrd id="baa"><br>
<Subject><a moz-do-not-send="true" href="http://myopenid.net/"
target="_blank">http://myopenid.net/</a></Subject><br>
<ds:Signature>...</ds:Signature><br>
<link><br>
<rel><a moz-do-not-send="true"
href="http://openid.net/op/endpoint" target="_blank">http://openid.net/op/endpoint</a></rel><br>
<url><a moz-do-not-send="true"
href="http://specs.openid.net/auth/2.0" target="_blank">http://specs.openid.net/auth/2.0</a></url><br>
</link><br>
</xrd><br>
<br>
to find out the concrete endpoint of this authentication service.<br>
<font color="#888888"><br>
=nat</font>
<div>
<div class="h5"><br>
<br>
John Bradley wrote:<br>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Allen,<br>
<br>
In XRD 1.0 we are moving to a link based model.<br>
<br>
So a users XRD rather than having to specify the openID providers
service can point to an openID provider.<br>
<br>
The URIs that we currently use describe the service not the provider.<br>
<br>
I think Nat is looking for a link relationship that describes a user
pointing to a service providers XRD rather than to the service itself.<br>
<br>
There will be a bunch of new link types required for various protocols.<br>
<br>
John B.<br>
<br>
<br>
On 2009-09-02, at 5:27 PM, Allen Tom wrote:<br>
<br>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi Nat,<br>
<br>
Can you explain the problem in a bit more detail? Can you give an
example use case?<br>
<br>
Thanks<br>
Allen<br>
<br>
<br>
Nat Sakimura wrote:<br>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
The second topic for OpenID 2.1<br>
<br>
Maybe, it should be separated to the Discovery but...<br>
<br>
In XRD 1.0, we need to define <Rel> type url for the user=OP
relationship.<br>
What shall we use?<br>
<br>
Something like:<br>
<br>
<a moz-do-not-send="true"
href="http://specs.openid.net/rel/openid_provider#" target="_blank">http://specs.openid.net/rel/openid_provider#</a><br>
<br>
=nat<br>
_______________________________________________<br>
specs mailing list<br>
<a moz-do-not-send="true" href="mailto:specs@lists.openid.net"
target="_blank">specs@lists.openid.net</a><br>
<a moz-do-not-send="true"
href="http://lists.openid.net/mailman/listinfo/openid-specs"
target="_blank">http://lists.openid.net/mailman/listinfo/openid-specs</a></blockquote>
<br>
_______________________________________________<br>
specs mailing list<br>
<a moz-do-not-send="true" href="mailto:specs@lists.openid.net"
target="_blank">specs@lists.openid.net</a><br>
<a moz-do-not-send="true"
href="http://lists.openid.net/mailman/listinfo/openid-specs"
target="_blank">http://lists.openid.net/mailman/listinfo/openid-specs</a></blockquote>
</blockquote>
_______________________________________________<br>
specs mailing list<br>
<a moz-do-not-send="true" href="mailto:specs@lists.openid.net"
target="_blank">specs@lists.openid.net</a><br>
<a moz-do-not-send="true"
href="http://lists.openid.net/mailman/listinfo/openid-specs"
target="_blank">http://lists.openid.net/mailman/listinfo/openid-specs</a><br>
</div>
</div>
</blockquote>
</div>
<br>
<br clear="all">
<br>
-- <br>
<a moz-do-not-send="true" href="http://santrajan.blogspot.com">http://santrajan.blogspot.com</a><br>
<a moz-do-not-send="true" href="http://twitter.com/santoshrajan">http://twitter.com/santoshrajan</a><br>
<a moz-do-not-send="true" href="http://www.facebook.com/santosh.rajan">http://www.facebook.com/santosh.rajan</a><br>
<br>
<br>
</div>
</blockquote>
</body>
</html>