[Openid-specs-ab] Feedback on UserInfo schema

Breno de Medeiros breno at google.com
Wed Mar 6 17:14:40 UTC 2013


Google returns phone numbers in two different formats: The
display-friendly displayable format that follows the user preferences
on how they see the number, and a standard-compliant form for
machines.

The UserInfo spec documents a 'phone_number' field that appears to try
to be both. It's the user 'preferred' phone number (indicating some
allowance for display-friendliness) and then only RECOMMENDS format
compliance.

Option 1. Define two fields: display_phone_number and
std_phone_number, where the latter MUST be in the E164 or RFC3966 (the
latter deals with phone extensions as well).

Option 2. Clarify the current language by replacing RECOMMENDED with
MUST if the desire is to support machine use cases

Option 3. Clarity the current language by saying that this is for
display purposes only.

-- 
--Breno


More information about the Openid-specs-ab mailing list