ve7jtb at ve7jtb.com
Wed May 16 15:52:03 UTC 2012
In the Facebook case they are exposing the Facebook username. Is that what thou want or an indication of what username they would like?
I am not against the idea, just wanting to clarify the proposed semantics.
On 2012-05-16, at 11:27 AM, Justin Richer wrote:
> Whether or not we want to encourage them, we have systems that will use them. Facebook also has "username" now:
> So I say we just grab that and be done with it. PoCo has "preferredUsername" for the same purpose. This makes a lot more sense than "nickname", which really has a different (and potentially useful in parallel) semantic behind it.
> -- Justin
> On 05/16/2012 11:16 AM, John Bradley wrote:
>> That is not part of the basic set of attributes Facebook uses, That was where the list originally came from.
>> I thought that nickname was used by RP for that.
>> looking at the spec the example of shorting Michael to Mike may be slightly misleading, In my case my nickname is "ve7jtb". The other potential issue is that we don't preclude spaces.
>> Is there a need for a separate claim that is a single string not including spaces to be used as a local user name.
>> There is also the question of encouraging local user names.
>> John B.
>> On 2012-05-16, at 10:45 AM, Justin Richer wrote:
>>> I might be missing it, but it seems that there's a gap for specifying a user's preferred local username in the User Info schema. This is distinct from "user_id" which is a guaranteed unique identifier, "name" which is the actual name of the person, "nickname" which is a shortened first name, or anything else that I can see.
>>> Is there a specific reason for this omission? If not, I'd like us to add in a standard claim for this information.
>>> -- Justin
>>> Openid-specs-ab mailing list
>>> Openid-specs-ab at lists.openid.net
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 4937 bytes
Desc: not available
More information about the Openid-specs-ab