<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">There already is work done on that part right?<div><br></div><div>See <a href="http://step2.googlecode.com/svn/spec/attribute_exchange_validate/trunk/openid-attribute-exchange-validate-mode.html">http://step2.googlecode.com/svn/spec/attribute_exchange_validate/trunk/openid-attribute-exchange-validate-mode.html</a></div><div><br><div><div><div><div>Op 8 dec 2009, om 05:36 heeft Allen Tom het volgende geschreven:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>
<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="x-msg://157/chris.messina@gmail.com">chris.messina@gmail.com</a>> wrote:<br>
<br>
</span></font><blockquote type="cite"><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="x-msg://157/bkissel@janrain.com">bkissel@janrain.com</a>> wrote:<br>
</span></font><blockquote type="cite"><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="x-msg://157/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="x-msg://157/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="x-msg://157/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="x-msg://157/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="x-msg://157/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="x-msg://157/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="x-msg://157/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>
</div>
</blockquote></div><br></div></div></div></body></html>