<br><br><div class="gmail_quote">On Thu, Nov 19, 2009 at 9:04 AM, Santosh Rajan <span dir="ltr"><<a href="mailto:santrajan@gmail.com">santrajan@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
When i said "resolves to", i meant exactly what is said, type in the OpenID and get the resource descriptor straight. </blockquote><div><br></div><div>Well if you mean "resolves to" in the web sense, this question doesn't make sense. If the OpenID is an HTTP URL, then it is already defined what it "resolves to" - the document you get when you access that URL. We can't change that, and we don't need to.</div>
<div><br></div><div>Asking whether the OpenID should resolve to a descriptor sounds to me like asking whether cows should lay eggs - they don't. Maybe I just don't understand the question...</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
The point is, whether the user typed in his http: uri or acct: uri, we need to get to his resource descriptor.</blockquote><div><br></div><div>No, what we "need" to get to is the OP endpoint. Going through the resource descriptor is _one_ way to get to the OP endpoint.</div>
<div><br></div><div>Dirk.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> In the case of http: uri we could skip the host-meta. I am not suggesting anything here. Instead I have posed a set of questions, which i hope to find some answers.<div>
<br></div><div>As for directed identity, i am quite clear that we need to dump it, because it is the root cause of the nascar problem.</div>
</blockquote></div><br>