On 30-Jul-07, at 8:48 PM, Eran Hammer-Lahav wrote:
In this case, it sounds like an XRDS document MUST no include both
an OP Endpoint element and a Claimed Identifier element.
I don't see this implied anywhere. Do you have a specific pointer or
a clear reasoning for this?
If an XRDS has
The OpenID spec is not authoritative for what XRDS documents can or
cannot contain; it just says how to consume them for the purposes of
OpenID authentication.
Point taken.
As for the last few points, I now understand how all the little details from
the various sections come together. I
Subject: Re: Differentiating between User Identifier and OP Identifier
Eran Hammer-Lahav wrote:
Those do not come to the same conclusion - while support for XRIs
is
left for each RP to decide, the same does not apply to the XRDS /
Yadis
discovery for URLs.
So XRI is optional?
Yes
On 28-Jul-07, at 10:00 AM, Eran Hammer-Lahav wrote:
Section 7.3.1:
If more than one set of the following information has been
discovered, the
precedence rules defined in [XRI_Resolution_2.0] are to be applied.
This somewhat confusing when combined with section 7.3.2.2:
Once the
Thanks Johnny!
In this case, it sounds like an XRDS document MUST no include both
an OP Endpoint element and a Claimed Identifier element.
I don't see this implied anywhere. Do you have a specific pointer or
a clear reasoning for this?
If an XRDS has both elements, the RP will try the
Thanks Johnny!
It makes more sense now. Here are some further comments:
I started to rewrite section 7 to make it easier to read but as I was going
through it again and again, it became clearer. I think while all the terms
are properly explained elsewhere, it might help to repeat some of them
