<HTML>
<HEAD>
<TITLE>Re: Yahoo available AX attrs</TITLE>
</HEAD>
<BODY>
<FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>I’d recommend using a timestamp indicating when it was last verified, with a special value to indicate that the OP is also the email provider and has 100% certainty. (perhaps just setting the verification time==now is sufficient)<BR>
<BR>
Allen<BR>
<BR>
<BR>
On 12/7/09 8:29 PM, "Chris Messina" <<a href="chris.messina@gmail.com">chris.messina@gmail.com</a>> wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>Sounds like something to add to PoCo... perhaps something as simple as a "verified" boolean added to email addresses?<BR>
<BR>
<a href="http://portablecontacts.net/draft-schema.html#anchor4">http://portablecontacts.net/draft-schema.html#anchor4</a><BR>
<BR>
Chris<BR>
<BR>
On Mon, Dec 7, 2009 at 8:25 PM, Brian Kissel <<a href="bkissel@janrain.com">bkissel@janrain.com</a>> wrote:<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>+1 on email address metadata, many RPs definitely want this.<BR>
<BR>
Cheers,<BR>
<BR>
Brian<BR>
___________<BR>
<FONT COLOR="#888888"><BR>
Brian Kissel<BR>
CEO, JanRain - WebID and Social Publishing for User Engagement<BR>
Email: <a href="bkissel@janrain.com">bkissel@janrain.com</a> Cell: 503.866.4424 Fax: 503.296.5502<BR>
</FONT><BR>
<BR>
-----Original Message-----<BR>
From: <a href="openid-specs-bounces@lists.openid.net">openid-specs-bounces@lists.openid.net</a> [<a href="mailto:openid-specs-bounces@lists.openid.net">mailto:openid-specs-bounces@lists.openid.net</a>] On Behalf Of Allen Tom<BR>
Sent: Monday, December 07, 2009 7:46 PM<BR>
To: Peter Watkins; Chris Obdam; <a href="openid-specs@lists.openid.net">openid-specs@lists.openid.net</a><BR>
Subject: Re: Yahoo available AX attrs<BR>
<BR>
Oops - I clicked send too early.<BR>
<BR>
The bad UX with AX is the security warning that most browsers display when<BR>
POSTing a form from HTTPS to HTTP, which is the case when the Yahoo OP<BR>
returns a lot of attributes. AX attribute names are excessively long, so<BR>
it's very likely that using different attribute names for first/last/middle<BR>
name will cause the response to be returned via POST. (2KB is the cutoff<BR>
point)<BR>
<BR>
With regards to email address - unless we're 100% sure about the email<BR>
address, we'd like to return metadata about the email address. Specifically,<BR>
we'd like to indicate whether or not the email address was verified, and if<BR>
so, when it was verified. This is definitely something that we'd like to get<BR>
in to AX 2.0.<BR>
<BR>
Allen<BR>
<BR>
<BR>
<BR>
On 12/7/09 7:39 PM, "Allen Tom" <<a href="atom@yahoo-inc.com">atom@yahoo-inc.com</a>> wrote:<BR>
<BR>
> It definitely makes sense to use different attributes for givennanme/surname<BR>
> so that RPs don't have to parse the string, and a few other RPs have also<BR>
> asked for it. Our initial goal for our AX implementation was just to match<BR>
> SREG, and SREG only has a single openid.sreg.fullname attribute.<BR>
><BR>
> We'll add support for separate first/last/middle/suffix attributes in a<BR>
> followup release - probably early next year. I do hope that we're able to<BR>
> standardize the attribute names, and also keep them short and compact. If you<BR>
> ask for all our supported attributes, the response will exceed 2KB, which<BR>
> requires that the response is returned via POST, causing a really bad UX.<BR>
><BR>
> With regards to email address - we'd like to be able to return metadata about<BR>
> the email address w<BR>
><BR>
><BR>
><BR>
> On 12/7/09 7:25 AM, "Peter Watkins" <<a href="peterw@tux.org">peterw@tux.org</a>> wrote:<BR>
><BR>
>> On Mon, Dec 07, 2009 at 09:16:46AM +0100, Chris Obdam wrote:<BR>
>>>> Chris (Obdam) - which additional attributes would you like to see<BR>
>>>> available? The attributes that we’ll be adding early next year will include<BR>
>>>> Yahoo Profile URL and account creation date. A bunch of people have asked<BR>
>>>> for Flickr Photos URL and Upcoming Profile URL, so we’ll probably get<BR>
>>>> around<BR>
>>>> to adding those too.<BR>
>>> I would like to access every attr specified in de AXschema? :-)<BR>
>>><BR>
>>> In my Yahoo profile i have provided my address (home and work). I would like<BR>
>>> to use those in a sign form somewhere else.<BR>
>>> Same goes for my phone numbers.<BR>
>><BR>
>> So would I. One of the simpler goals of our Single Sign On is prepopulating<BR>
>> form fields; having postal address and phone number would be a help.<BR>
>><BR>
>> I'd also like to see First and Last names available as separate attributes,<BR>
>> otherwise we're trying to intelligently split both "Mary Jane Parker" and<BR>
>> "Malcom Mac Murray".<BR>
>><BR>
>> Also I would prefer that you give us the user's *primary* email address. In<BR>
>> my Yahoo profile, my Yahoo email address is flagged as "Share with no one"<BR>
>> and I have a different email address flagged as primary, but your AX sends<BR>
>> my yahoo email address. That's bad from usability in part because I very,<BR>
>> very seldom check my Yahoo email inbox.<BR>
>><BR>
>> The Yahoo website attribute would also be nice to have; as we start<BR>
>> building more "social" features on our sites, it would be nice to make<BR>
>> it easier for our users to share links to their primary web presences,<BR>
>> although I can understand if Yahoo management prefers to only expose the<BR>
>> Profile URL for business reasons.<BR>
>><BR>
>> Thanks,<BR>
>><BR>
>> Peter<BR>
>><BR>
<BR>
_______________________________________________<BR>
specs mailing list<BR>
<a href="specs@lists.openid.net">specs@lists.openid.net</a><BR>
<a href="http://lists.openid.net/mailman/listinfo/openid-specs">http://lists.openid.net/mailman/listinfo/openid-specs</a><BR>
_______________________________________________<BR>
specs mailing list<BR>
<a href="specs@lists.openid.net">specs@lists.openid.net</a><BR>
<a href="http://lists.openid.net/mailman/listinfo/openid-specs">http://lists.openid.net/mailman/listinfo/openid-specs</a><BR>
</SPAN></FONT></BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'><BR>
<BR>
</SPAN></FONT></BLOCKQUOTE>
</BODY>
</HTML>