<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">That’s in the JWT spec. See
<a href="http://tools.ietf.org/html/draft-ietf-oauth-json-web-token-06#section-4.2">
http://tools.ietf.org/html/draft-ietf-oauth-json-web-token-06#section-4.2</a> on Public Claim Names.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> -- Mike<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Nat Sakimura [mailto:sakimura@gmail.com]
<br>
<b>Sent:</b> Wednesday, March 06, 2013 2:50 PM<br>
<b>To:</b> Breno de Medeiros<br>
<b>Cc:</b> Mike Jones; openid-specs-ab@lists.openid.net<br>
<b>Subject:</b> Re: [Openid-specs-ab] Feedback on UserInfo schema<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">OK. If we were to add phone_number_formatted, we should state that this is <o:p></o:p></p>
<div>
<p class="MsoNormal">the string that the user entered. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">BTW, where can I find the text that claims can be extended with URI as claim names etc.? <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Nat<o:p></o:p></p>
<div>
<p class="MsoNormal">2013/3/7 Breno de Medeiros <<a href="mailto:breno@google.com" target="_blank">breno@google.com</a>><o:p></o:p></p>
<p class="MsoNormal">The display version is as user entered, or in the common format of the<br>
user's locale. It should be displayed as is.<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
On Wed, Mar 6, 2013 at 1:54 PM, Nat Sakimura <<a href="mailto:sakimura@gmail.com">sakimura@gmail.com</a>> wrote:<br>
> I am fine with it, though how to create "formatted phone number" needs to be<br>
> clarified. Is it just how the user entered or created algorithmically? If<br>
> the later, the OP needs to have translation template for each countries as<br>
> they widely varies. As to the syntax is concerned, I prefer<br>
> phone_number_formatted instead of formatted_phone_number. Also, a +1 for<br>
> making E.164 a MUST for the machine consumption.<br>
><br>
> With respect to phone number, it just reminded me of the fact that multiple<br>
> sources expressed desire to differentiate land line phone number and mobile<br>
> phone number. Their characteristics as to the binding strength to the<br>
> subject is very different. Land line usually is only bound to the "home /<br>
> household" or "office location", the mobile phone number is much more<br>
> tightly coupled with the person / subject. So, actually, you may not want to<br>
> treat them as a single class.<br>
><br>
> So, in addition to phone_number, I would like to propose mobile_number as<br>
> well.<br>
><br>
> Nat<br>
><br>
><br>
> 2013/3/7 Mike Jones <<a href="mailto:Michael.Jones@microsoft.com">Michael.Jones@microsoft.com</a>><br>
>><br>
>> I would be fine with having both phone number claims.<br>
>> "formatted_phone_number" could be the display form (just like "formatted" is<br>
>> the address display form) and "phone_number" could be an RFC 3966 phone<br>
>> number. The "phone" scope would request both.<br>
>><br>
>> What claim names is Google actually using for these values today?<br>
>><br>
>> What do others think?<br>
>><br>
>> -- Mike<br>
>><br>
>> -----Original Message-----<br>
>> From: <a href="mailto:openid-specs-ab-bounces@lists.openid.net">openid-specs-ab-bounces@lists.openid.net</a><br>
>> [mailto:<a href="mailto:openid-specs-ab-bounces@lists.openid.net">openid-specs-ab-bounces@lists.openid.net</a>] On Behalf Of Breno de<br>
>> Medeiros<br>
>> Sent: Wednesday, March 06, 2013 9:15 AM<br>
>> To: <a href="mailto:openid-specs-ab@lists.openid.net">openid-specs-ab@lists.openid.net</a><br>
>> Subject: [Openid-specs-ab] Feedback on UserInfo schema<br>
>><br>
>> Google returns phone numbers in two different formats: The<br>
>> display-friendly displayable format that follows the user preferences on how<br>
>> they see the number, and a standard-compliant form for machines.<br>
>><br>
>> The UserInfo spec documents a 'phone_number' field that appears to try to<br>
>> be both. It's the user 'preferred' phone number (indicating some allowance<br>
>> for display-friendliness) and then only RECOMMENDS format compliance.<br>
>><br>
>> Option 1. Define two fields: display_phone_number and std_phone_number,<br>
>> where the latter MUST be in the E164 or RFC3966 (the latter deals with phone<br>
>> extensions as well).<br>
>><br>
>> Option 2. Clarify the current language by replacing RECOMMENDED with MUST<br>
>> if the desire is to support machine use cases<br>
>><br>
>> Option 3. Clarity the current language by saying that this is for display<br>
>> purposes only.<br>
>><br>
>> --<br>
>> --Breno<br>
>> _______________________________________________<br>
>> Openid-specs-ab mailing list<br>
>> <a href="mailto:Openid-specs-ab@lists.openid.net">Openid-specs-ab@lists.openid.net</a><br>
>> <a href="http://lists.openid.net/mailman/listinfo/openid-specs-ab" target="_blank">
http://lists.openid.net/mailman/listinfo/openid-specs-ab</a><br>
>> _______________________________________________<br>
>> Openid-specs-ab mailing list<br>
>> <a href="mailto:Openid-specs-ab@lists.openid.net">Openid-specs-ab@lists.openid.net</a><br>
>> <a href="http://lists.openid.net/mailman/listinfo/openid-specs-ab" target="_blank">
http://lists.openid.net/mailman/listinfo/openid-specs-ab</a><br>
><br>
><br>
><br>
><br>
> --<br>
> Nat Sakimura (=nat)<br>
> Chairman, OpenID Foundation<br>
> <a href="http://nat.sakimura.org/" target="_blank">http://nat.sakimura.org/</a><br>
> @_nat_en<br>
<br>
<br>
<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal">--<br>
--Breno<o:p></o:p></p>
</div>
<p class="MsoNormal"><br>
<br clear="all">
<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal">-- <br>
Nat Sakimura (=nat)<o:p></o:p></p>
<div>
<p class="MsoNormal">Chairman, OpenID Foundation<br>
<a href="http://nat.sakimura.org/" target="_blank">http://nat.sakimura.org/</a><br>
@_nat_en<o:p></o:p></p>
</div>
</div>
</div>
</body>
</html>