<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:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:D="DAV:" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" 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 12 (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;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.apple-style-span
{mso-style-name:apple-style-span;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</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=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>At the Content Provider Advisory Committee we heard from several
RPs that the most important data they wanted from OPs was email address,
followed by age or date of birth for any sites that had COPPA compliance
goals. Further, if the OP can pass a “verified” email address so that RPs don’t
have to go through the 2 step registration dance of waiting for users to “verify”
their email address, that improves registration success rate. There’s a big
drop off from email registration due to verification emails going to spam
folders or users just forgetting to go through the last step to verify an
account.<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'>If all OPs would pass a verified email address (with end user consent)
I believe all RPs would certainly prefer it.<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:navy'>Cheers,</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:navy'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:navy'><br>
Brian<o:p></o:p></span></p>
<p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:navy'>==============<o:p></o:p></span></b></p>
<p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:navy'>Brian Kissel<o:p></o:p></span></b></p>
<p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:navy'>Cell: 503.866.4424<o:p></o:p></span></b></p>
<p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:navy'>Fax: 503.296.5502<o:p></o:p></span></b></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<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"'>
general-bounces@openid.net [mailto:general-bounces@openid.net] <b>On Behalf Of </b>Andrew
Arnott<br>
<b>Sent:</b> Friday, April 03, 2009 8:58 AM<br>
<b>To:</b> santrajan<br>
<b>Cc:</b> general@openid.net<br>
<b>Subject:</b> Re: [OpenID] About Facebook, MySpace and OpenID<o:p></o:p></span></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Santrajan,<o:p></o:p></p>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>I really don't understand this obsession you have about how
OpenID is a useless "extra step" without an email address being part
of it. Any shopping mall web site that requires a login will need to take a
username+password, plus email verification, or an OpenID, plus email
verification. There's no <span class=apple-style-span><i>extra</i></span> step
-- it's an exchange of one step for a different step. And yes, it
absolutely makes sense to do this because customers won't have to create yet
another username and password.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>I really don't care too much about jumping to my email
client for an email verification step. I don't mind that. What I really
mind is remembering another username and password because that lasts a long
time.<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'>I'm not disagreeing that
skipping email verification would be convenient, but geez, man, how long can
you beat this dead horse?<br clear=all>
--<br>
Andrew Arnott<br>
"I [may] not agree with what you have to say, but I'll defend to the death
your right to say it." - Voltaire<br>
<br>
<o:p></o:p></p>
<div>
<p class=MsoNormal>On Fri, Apr 3, 2009 at 8:43 AM, santrajan <<a
href="mailto:santrajan@gmail.com">santrajan@gmail.com</a>> wrote:<o:p></o:p></p>
<p class=MsoNormal><br>
I am posting the full text of my blog post with the same subject here.<br>
<a
href="http://santrajan.blogspot.com/2009/04/about-facebook-myspace-and-openid.html"
target="_blank">http://santrajan.blogspot.com/2009/04/about-facebook-myspace-and-openid.html</a><br>
<br>
MySpace recently announced there support for OpenID. The idea here is that<br>
MySpace users will be able to log in to third party sites with their MySpace<br>
Id's. MySpace users needn't get too exited about it too soon.<br>
<br>
Consider this. A MySpace user would like to log in to her favorite shopping<br>
site with her MySpace Account. The shopping site is unlikely to support<br>
MySpace Logins. The simple reason being that shopping sites need the email<br>
addresses of their authenticated users for various reasons (communicating<br>
orders, delivery, new stock etc etc). It doesnt make sence to the shopping<br>
site to authenticate using MySpace (An extra step) and then run the user<br>
through another email verification process. This will also be true for many<br>
other web sites that require their users to login.<br>
<br>
However MySpace could have made the users email available to the shopping<br>
site (Ofcource with the users consent only) via a provision in the OpenID<br>
specifications called SREG. So then why didnt MySpace choose to support<br>
SREG?<br>
<br>
This is not a problem for MySpace alone. When Facebook decides to support<br>
OpenID it will be faced with the same dilemma. It is really a frightening<br>
thought for social networking sites to hand over their users email address<br>
to a third party. For social networking sites keeping the users bound their<br>
network is of primary importance.<br>
<br>
However an equally frightening possibility for social networking sites is to<br>
see their users start using Google accounts and Yahoo accounts to log in<br>
into third party sites! They could start loosing users in that case too.<br>
<br>
The jury is out on what these guys should do.<br>
<br>
But I am clear on what MySpace should have done. Facebook being the no 1<br>
social networking site can wait this one out a bit more. However MySpace<br>
should really have capitalized on this opportunity. Supported SREG and tried<br>
to rope in third party sites to support MySpace logins, and tried to build a<br>
small advantage over Facebook on this account.<br>
<span style='color:#888888'><br>
<br>
--<br>
View this message in context: <a
href="http://www.nabble.com/About-Facebook%2C-MySpace-and-OpenID-tp22871070p22871070.html"
target="_blank">http://www.nabble.com/About-Facebook%2C-MySpace-and-OpenID-tp22871070p22871070.html</a><br>
Sent from the OpenID - General mailing list archive at Nabble.com.<br>
<br>
_______________________________________________<br>
general mailing list<br>
<a href="mailto:general@openid.net">general@openid.net</a><br>
<a href="http://openid.net/mailman/listinfo/general" target="_blank">http://openid.net/mailman/listinfo/general</a></span><o:p></o:p></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p>__________ Information from ESET NOD32 Antivirus, version of virus signature
database 3985 (20090403) __________<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p>The message was checked by ESET NOD32 Antivirus.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p>http://www.eset.com<o:p></o:p></p>
</div>
</body>
</html>