OpenID Auth 2.1 should allow string-text as an OpenID Identifier if an XRD document can be located for the Identifier.
By
David Fuelling
on June 05, 2009
The aim of this claim is to determine how many people support/oppose the idea that the OpenID Auth 2.1 spec should allow any string-text to be an OpenID Identifier, so long as the string-text can be de-referenced to produce an XRD document that can be used in OpenID Discovery.
Currently, the core spec supports only URL's and XRI's as Identifiers, so voting yes on this claim indicates that you support the idea of expanding the definition of an OpenID Identifier.
Note that voting no on this claim does not preclude the use of email (or other) Identifier types in OpenID via direct inclusion in the spec or an extension.
This claim is part of a broader set of claims located here:
https://openid.pbworks.com/Identifier-and-Discovery-2_1-Questions
4
1
80.0% 20.0%
Embed Claim
Make a related claim
This claim was inspired by
Similar claims
- 7-1 OpenID Auth 2.1 should use XRD as its primary discovery mechanism.
- 1-2 OpenID Auth 2.1 MUST mandate legacy support for older OpenID Discovery mechanisms.
- 1-3 There should be separate WG's for OpenID 2.1 and OpenID 2.1 Discovery.
- 2-4 OpenID Auth 2.1 should mandate XRI Identifier support as part of the *core* OpenID 2.1 specification.
- 1-5 OpenID Auth 2.1 should mandate email-like Identifier support as part of the *core* OpenID 2.1 specification.
Discussion