<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:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" 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.EmailStyle18
{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'>Great feedback Chris, agree with your points. Also agree we may
still want to have separate Marketing and Adoption Committees. There is some
overlap, but there are some separate activities and goals. Depends who shows
up for which committees and who is willing to volunteer some meaningful time
and effort. FB is all full time paid employees doing a lot of the heavy
lifting, whereas OpenID is volunteers. Linux has done a lot with volunteers,
but the Bluetooth SIG had to hire a lot of people to start getting meaningful
adoption. To date, we have not had the widespread volunteer support of
something like Linux. Welcome input from those monitoring this list on how to
facilitate and enable more volunteer support. We get lots of email
suggestions, but not much in the way of people tackling specific projects and
deliverables.<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:#0033CC'>Cheers,<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#0033CC'><br>
Brian<o:p></o:p></span></p>
<p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#0033CC'>___________</span></b><span style='font-size:11.0pt;font-family:
"Calibri","sans-serif";color:#0033CC'><o:p></o:p></span></p>
<p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#0033CC'><o:p> </o:p></span></b></p>
<p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#0033CC'><a href="http://www.linkedin.com/pub/0/10/254"><span
style='color:#0033CC'>Brian Kissel</span></a><o:p></o:p></span></b></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#0033CC'>CEO - JanRain, Inc.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#0033CC'>bkissel@janrain.com<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#0033CC'>Mobile: </span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#0033CC'>503.342.2668 </span><span style='font-size:11.0pt;font-family:
"Calibri","sans-serif";color:#0033CC'>| Fax: </span><span style='font-size:
11.0pt;font-family:"Calibri","sans-serif";color:#0033CC'>503.296.5502</span><span
style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#0033CC'><o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#0033CC'><o:p> </o:p></span></p>
<p class=MsoNormal><b><i><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#0033CC'>Increase registrations, engage users, and grow your brand with
RPX. Learn more at </span></i></b><b><i><span style='font-size:11.0pt;
font-family:"Calibri","sans-serif";color:red'><a href="http://www.rpxnow.com/"><span
style='color:red'>www.rpxnow.com</span></a><o:p></o:p></span></i></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"'>
openid-board-bounces@lists.openid.net
[mailto:openid-board-bounces@lists.openid.net] <b>On Behalf Of </b>Chris Messina<br>
<b>Sent:</b> Friday, January 15, 2010 7:08 PM<br>
<b>To:</b> openid-board@lists.openid.net<br>
<b>Subject:</b> Re: [OpenID board] Adoption: are we ready? (Was: Re: board
Digest, Vol 37, Issue 10)<o:p></o:p></span></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>On Fri, Jan 15, 2010 at 12:04 PM, Brian Kissel <<a
href="mailto:bkissel@janrain.com">bkissel@janrain.com</a>> wrote:<o:p></o:p></p>
<div>
<blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;
margin-left:4.8pt;margin-right:0in'>
<div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#1F497D'>Regardless of how we get the
technologies to work with each other, from an adoption perspective it seems
like we do need to have a clear and consistent message on how RPs and end users
can leverage all the benefits of OpenID, OAuth, WRAP, Portable Contacts,
SREG/AX, Activity Streams, etc. in a robust and reliable way. Facebook
has done a great job providing a turnkey solution for website operators and end
users that provides benefits to both stakeholders. The open
standards-based alternatives need to offer similarly compelling functionality
and ease of deployment/use to see increased success in the market. What
suggestions do folks have on how we achieve that?</span><o:p></o:p></p>
</div>
</div>
</blockquote>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>I think that we need more demos and examples of how this
stuff works — whether we wire up <a href="http://openid.net">openid.net</a> or <a
href="http://openweb.org">openweb.org</a> as a demonstration of how this stuff
can be assembled, what Facebook has done better than most is:<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>1) lead by example<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>2) work with partners to demonstrate how far you can take
integrations<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>3) supported their product and shown continuous, active
development (even if that means breaking things from time to time, it proves
that they're at least changing things!)<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>4) have done lots of worldwide outreach to foment community
with Developer Garages<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>5) have made the technology relevant to their audience: site
and app builders, hobbyists, publishers, etc<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>6) have communicated clearly and consistently the value of
the technology<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>These pages are worth providing an OpenID.net answer to:<o:p></o:p></p>
</div>
<div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal><a href="http://developers.facebook.com/connect.php">http://developers.facebook.com/connect.php</a><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><a
href="http://www.facebook.com/connectnews?v=app_7146470109">http://www.facebook.com/connectnews?v=app_7146470109</a><o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</div>
<div>
<p class=MsoNormal>7) have provided overwhelming value that obviated the
concern about someone else "owning" the implementors' customers —
instead the upside for new customers was so great that it was worth the
perceived loss of control.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>8) have provided desktop, embedded, mobile, and web
solutions<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>9) have provided user interface guidelines, recommendations,
analytics, and other tools to measure the success of an implementation<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>10) have kept the FB Connect in the news and have continued
to roll out new features, improvements, optimizations, and functionality<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>So. We have our work cut out for us. <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>Especially aligning all the things that the companies
pushing the open solutions have been rolling out that would make for great news
stories.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<div>
<p class=MsoNormal>Perhaps we should really just break up what would have been
the marketing@ committee and create an adoption and press committees to help
make concrete and divide up responsibilities for some of the things that need
to happen in 2010?<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>Chris<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
<blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;
margin-left:4.8pt;margin-right:0in'>
<div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#0033CC'>Cheers,</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#0033CC'><br>
Brian</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span
style='font-size:11.0pt;color:#0033CC'>___________</span></b><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span
style='font-size:11.0pt;color:#0033CC'> </span></b><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span
style='font-size:11.0pt;color:#0033CC'><a
href="http://www.linkedin.com/pub/0/10/254" target="_blank"><span
style='color:#0033CC'>Brian Kissel</span></a></span></b><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#0033CC'>CEO - JanRain, Inc.</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#0033CC'><a href="mailto:bkissel@janrain.com"
target="_blank">bkissel@janrain.com</a></span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#0033CC'>Mobile: 503.342.2668 | Fax: 503.296.5502</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#0033CC'> </span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><i><span
style='font-size:11.0pt;color:#0033CC'>Increase registrations, engage users,
and grow your brand with RPX. Learn more at </span></i></b><b><i><span
style='font-size:11.0pt;color:red'><a href="http://www.rpxnow.com/"
target="_blank"><span style='color:red'>www.rpxnow.com</span></a></span></i></b><o:p></o:p></p>
</div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span
style='font-size:10.0pt'>From:</span></b><span style='font-size:10.0pt'> <a
href="mailto:openid-board-bounces@lists.openid.net" target="_blank">openid-board-bounces@lists.openid.net</a>
[mailto:<a href="mailto:openid-board-bounces@lists.openid.net" target="_blank">openid-board-bounces@lists.openid.net</a>]
<b>On Behalf Of </b>Allen Tom<br>
<b>Sent:</b> Friday, January 15, 2010 10:12 AM</span><o:p></o:p></p>
<div>
<p class=MsoNormal><br>
<b>To:</b> <a href="mailto:openid-board@lists.openid.net" target="_blank">openid-board@lists.openid.net</a><o:p></o:p></p>
</div>
<p class=MsoNormal><b>Subject:</b> Re: [OpenID board] Adoption: are we ready?
(Was: Re: board Digest, Vol 37, Issue 10)<o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:12.0pt'><span
style='font-size:11.0pt'>As one of the authors of OAuth-WRAP let me just say
that rewriting OpenID as a profile of WRAP is a bad idea, especially from a
marketing and perception perspective. <br>
<br>
However, I do think that we need a way for RPs to access the user’s data via
API, and some sort of WRAP integration does seem to make sense.<br>
<br>
Allen<br>
<br>
On 1/15/10 8:10 AM, "Chris Messina" <<a
href="http://chris.messina@gmail.com" target="_blank">chris.messina@gmail.com</a>>
wrote:</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
style='font-size:11.0pt'>On Fri, Jan 15, 2010 at 5:45 AM, daniel jacobson <<a
href="http://fragment37@yahoo.com" target="_blank">fragment37@yahoo.com</a>>
wrote:</span><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:12.0pt'><span
style='font-size:11.0pt'> <br>
<br>
While I'm not about to suggest that we wait for the "perfect"
solution — I want to be conscious of the cred that could be burned if we
decide, 3-6 months from now, that really OpenID should be rewritten as a
profile of OAuth WRAP (let's just say) and that adoption should really hinge on
getting WRAP out the door and THEN promoting OpenID v.Next on top of it.</span><o:p></o:p></p>
</div>
</div>
</div>
</div>
<p class=MsoNormal style='margin-bottom:12.0pt'><br>
_______________________________________________<br>
board mailing list<br>
<a href="mailto:board@lists.openid.net">board@lists.openid.net</a><br>
<a href="http://lists.openid.net/mailman/listinfo/openid-board" target="_blank">http://lists.openid.net/mailman/listinfo/openid-board</a><o:p></o:p></p>
</blockquote>
</div>
<p class=MsoNormal><br>
<br clear=all>
<br>
-- <br>
Chris Messina<br>
Open Web Advocate, Google<br>
<br>
Personal: <a href="http://factoryjoe.com">http://factoryjoe.com</a><br>
Follow me on Twitter: <a href="http://twitter.com/chrismessina">http://twitter.com/chrismessina</a><br>
<br>
This email is: [ ] shareable [X] ask first [ ]
private<o:p></o:p></p>
</div>
</body>
</html>