[OpenID] guid openid delegate
Johnny Bufu
johnny at sxip.com
Thu Sep 13 18:50:32 UTC 2007
On 13-Sep-07, at 10:36 AM, Peter Williams wrote:
> B "Claimed Identifier:
>
> An Identifier that the end user claims to own; the overall aim of the
> protocol is verifying this claim. The Claimed Identifier is either:
>
> - The Identifier obtained by normalizing (Normalization) the
> User-Supplied Identifier, if it was an URL.
>
> - The CanonicalID (XRI and the CanonicalID Element), if it was an
> XRI."
>
>
> B1. Change "Identifier obtained by normalizing (Normalization)" to
> "Identifier obtained as a result of normalizing (Normalizing) and
> performing discovery on"
For URLs, the claimed identifier is not the result of the (las part
of) discovery; it is determined only by the normalization (i.e. the
URI-normalized form of the user-supplied id after following all
redirects).
> B2. That B1 re-definition would constrain solicited Auth (with non XRI
> Identifier input) so that Claimed ID has to be an Identifier - even if
> delegation was used.
Claimed ID is already an identifier, as the definition is worded now.
> B3. To allow a Claimed_Identifier to be a non Identifier or
> non-CanonicalID, one could add a third case that allows for "custom
> discovery" during discovery, and the discovery associated with
> unsolicited Auth/Err
The discovery type is determined by the type of the identifier: only
HTTP(s) and XRI identifiers are supported, so only XRI/Yadis/HTML
discoveries. Whenever there's a supported identifier (e.g.
unsolicited assertions), discovery can be performed.
Johnny
More information about the general
mailing list