[OpenID] Should Openid's resolve to their descriptors in v.next?

[Dirk Balfanz]

On Thu, Nov 19, 2009 at 9:04 AM, Santosh Rajan <santrajan at gmail.com> wrote:

> When i said "resolves to", i meant exactly what is said, type in the OpenID
> and get the resource descriptor straight.


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.

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...


> The point is, whether the user typed in his http: uri or acct: uri, we need
> to get to his resource descriptor.


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.

Dirk.


> 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.
>
> As for directed identity, i am quite clear that we need to dump it, because
> it is the root cause of the nascar problem.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-general/attachments/20091119/9c8a7b86/attachment-0001.htm>