[OpenID] Calling OpenID 2.0 editors (was RE:ProblemswithOpenIDand TAG httpRange-14)

[Peter Williams]

OpenID, on the other hand, deals in identifiers. The documents involved
are just a convenient way of figuring out what identifiers to use.




Which is along the lines of what I said: we are not using http to collect web resources.

Openid does deal with identifiers, but they are not uris/urls in the formal sense of the uri rfc. Openid uses the syntax, but not the semantics - as to use the semantics would contradict the assumption above (uris identify web resources, including uri references that are resources in the semweb sense, in and of themselves)

We know the compliance argument has been dealt with : other upper layers have already done what openid discovery protocol does: ignore the link management semantics of http redirects.

This leaves the clickthru and the remembering issue - which is valid and pertinent. We could handle it openid.next by improving unsolicited auth, or standardizing openid discovery's use of redirects signals for openid purposes (only) when xris are not involved.