<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2.1" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: RWW Live: OpenID</title>
	<link>http://readwritetalk.com/2009/01/20/rww-live-openid/</link>
	<description></description>
	<pubDate>Fri, 30 Jul 2010 09:35:43 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2.1</generator>

	<item>
		<title>By: acai</title>
		<link>http://readwritetalk.com/2009/01/20/rww-live-openid/#comment-70352</link>
		<author>acai</author>
		<pubDate>Sun, 01 Mar 2009 16:58:58 +0000</pubDate>
		<guid>http://readwritetalk.com/2009/01/20/rww-live-openid/#comment-70352</guid>
		<description>I love the idea behind OpenID but how far is it really going to go due to its limitations?</description>
		<content:encoded><![CDATA[<p>I love the idea behind OpenID but how far is it really going to go due to its limitations?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Google and Plaxo Combine OpenID and OAuth for Improved Usability - Indometric</title>
		<link>http://readwritetalk.com/2009/01/20/rww-live-openid/#comment-68742</link>
		<author>Google and Plaxo Combine OpenID and OAuth for Improved Usability - Indometric</author>
		<pubDate>Fri, 30 Jan 2009 06:04:37 +0000</pubDate>
		<guid>http://readwritetalk.com/2009/01/20/rww-live-openid/#comment-68742</guid>
		<description>[...] populous. And the ease-of-use demonstrated by Facebook Connect put some friendly pressure on the OpenID contingent to improve the way they were managing the login [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] populous. And the ease-of-use demonstrated by Facebook Connect put some friendly pressure on the OpenID contingent to improve the way they were managing the login [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PayPal Joins OpenID Foundation Board as Sustaining Member - Online Media Managers</title>
		<link>http://readwritetalk.com/2009/01/20/rww-live-openid/#comment-68703</link>
		<author>PayPal Joins OpenID Foundation Board as Sustaining Member - Online Media Managers</author>
		<pubDate>Thu, 29 Jan 2009 05:58:09 +0000</pubDate>
		<guid>http://readwritetalk.com/2009/01/20/rww-live-openid/#comment-68703</guid>
		<description>[...] the members of the OpenID Foundation, ReadWriteWeb recently had the opportunity to sit down for an OpenID podcast with Kissel, Kveton, Chris Messina, and Recordon to discuss OpenID and its [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] the members of the OpenID Foundation, ReadWriteWeb recently had the opportunity to sit down for an OpenID podcast with Kissel, Kveton, Chris Messina, and Recordon to discuss OpenID and its [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: OpenID &#187; Blog Archive &#187; PayPal joins OpenID Foundation Board as we enter 2009</title>
		<link>http://readwritetalk.com/2009/01/20/rww-live-openid/#comment-68683</link>
		<author>OpenID &#187; Blog Archive &#187; PayPal joins OpenID Foundation Board as we enter 2009</author>
		<pubDate>Wed, 28 Jan 2009 16:00:49 +0000</pubDate>
		<guid>http://readwritetalk.com/2009/01/20/rww-live-openid/#comment-68683</guid>
		<description>[...] Last week, four Board members joined Sean Ammirati and others from popular technology blog ReadWriteWeb for an hour long podcast about increasing overall OpenID adoption, future plans for the OpenID Foundation and our thoughts on Google Friend Connect and Facebook Connect. The interview has been published on ReadWriteTalk. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Last week, four Board members joined Sean Ammirati and others from popular technology blog ReadWriteWeb for an hour long podcast about increasing overall OpenID adoption, future plans for the OpenID Foundation and our thoughts on Google Friend Connect and Facebook Connect. The interview has been published on ReadWriteTalk. [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bkk</title>
		<link>http://readwritetalk.com/2009/01/20/rww-live-openid/#comment-68336</link>
		<author>bkk</author>
		<pubDate>Wed, 21 Jan 2009 00:23:58 +0000</pubDate>
		<guid>http://readwritetalk.com/2009/01/20/rww-live-openid/#comment-68336</guid>
		<description>Thanks to the RWW team for the chance to share our thoughts on OpenID with your readers and listeners.  In only 60 minutes, we couldn't completely cover the three topics you had suggested, so I wanted to summarize some thoughts for those who may not have time to listen to the entire podcast. 
 
&lt;B&gt;1. How to increase adoption of OpenID&lt;/B&gt;
 
&lt;B&gt;Better user experience (UX).&lt;/B&gt;  The URL type in box works for some users today, but not the mass market yet. Maybe that will change as users become more familiar with OpenID, but we're not waiting on that.  We’re working with end users and relying parties (RPs) to determine the “best practices” for UX, which may vary by industry and application.  The Content Provider Advisory Committee meeting in NYC http://openid.net/2008/10/01/openid-content-provider-advisory-committee-kickoff-meeting/ and resulting Yahoo UX Summit gave us a lot of thoughts and feedback.  Some specific initiatives aimed at improving UX include Verisign’s Seatbelt, Google’s LSO initiative, Vidoop’s IDIB, JanRain's RPX http://rpxnow.com , and SixApart's TypePad Connect.
 
&lt;B&gt;More data for RPs.&lt;/B&gt;  All the major OPs are starting to test and implement simple registration (SREG) and/or attribute exchange (AX) to allow users to share standard profile data with RPs including name, nickname, email, gender, DOB, zip code, time zone, language, etc.  This data makes it easier for users to register on a new site, and simpler for website operators to build profiles to personalize their users experiences.  Expect to see even more rich data (interests, friends data, lifestream data, etc.) coming from OpenID providers like the upcoming MySpaceID.
 
&lt;B&gt;Proof Points.&lt;/B&gt;  Get thought leaders in various categories to implement OpenID.  For example: Sourceforge &#038; Stack Overflow (developer resources); UserVoice &#038; Get Satisfaction (customer feedback); MapQuest (mapping services); MS HealthVault, AME Health Commission (health care); Plaxo (contact management); CNN, Interscope Records, DailyMotion, RadioPop, &#038; StumbleAudio (media); National 4-H (affinity groups), Oxfam International (non-profits), Portland Trailblazers (sports), etc.
 
&lt;B&gt;Easier deployment options for RPs.&lt;/B&gt; Solutions to simplify deployment including blogging platform plugins (TypePad, Wordpress, etc.), Google Friend Connect, MySpaceID, JanRain RPX http://rpxnow.com , Rails and .Net plugins, etc.
 
&lt;B&gt;Market Research. &lt;/B&gt;More thorough understanding of what various market segments want from OpenID. Expand beyond the Content Provider Advisory Committee to add additional Advisory Committees for other market segments and applications.
 
&lt;B&gt;ROI Analysis.&lt;/B&gt;  More case studies on quantitative and qualitative benefits for deploying and using OpenID.
 
&lt;B&gt;Education.&lt;/B&gt; The major OPs will begin more proactive education of their end users about how to use the OpenIDs they already have.  Additionally, the OpenID Foundation needs to do more seminars, conferences, and other outreach programs with press and analysts to promote awareness and understanding of what OpenID is and what the benefits are for end users and RPs.
 
 
&lt;B&gt;2. Plans for the OpenID Foundation&lt;/B&gt;
 
With the new board recently elected and an executive director search underway, we are still finalizing our plans for 2009, but the activities should align with the goals of driving adoption and usage of OpenID as described above
 
&lt;B&gt;Technology.&lt;/B&gt; We now have a solid technology platform and continue to work on extending and enhancing it: Provider Authentication Policy Extension (PAPE), Contract Exchange (CX), OpenID/Oauth, etc.
 
&lt;B&gt;Research.&lt;/B&gt; Increased emphasis on “voice of the customer” from end users and RPs – what do they want and need from OpenID and other user centric identity solutions (OAuth, Portable Contacts, Open Social, etc.)  We'll do this through our standing committees, working groups, participation in industry events, and advisory committees as discussed above.  Initiatives will certainly include technology specification development and enhancement, but also include services as requested by the market if within the charter of the Foundation.
 
&lt;B&gt;Representation.&lt;/B&gt; Expanded OpenID Foundation membership and representation on the board, especially from content providers (media and affinity groups) and other categories of existing and potential RPs.
 
&lt;B&gt;Marketing outreach.&lt;/B&gt; Systematically leverage press and analysts interactions, trade shows, blogs, etc. focused on awareness and education
 
&lt;B&gt;Guidelines.&lt;/B&gt; Best practice guides for OPs and RPs, tutorials, and other resources as requested
 
&lt;B&gt;Expanded international outreach and coordination.&lt;/B&gt;   We now have two international representatives on the OpenID board who have achieved significant results in Japan and Europe.  We're also adding an International Liaison to the Executive Committee of the OpenID Foundation.
 
&lt;B&gt; 3. Opinions on Google Friend Connect &#038; Facebook Connect&lt;/B&gt;
 
These are great catalysts for showcasing the benefits to website operators and end users of user-centric identity solutions as well as demonstrating compelling UX models.  Facebook and Google have been very involved in sharing their experiences and recommendations with the OpenID Foundation and other open standard initiatives, for which we’re grateful
 
The market will evolve to embrace the best of what all providers and vendors have to offer, some sites already accept both Facebook Connect and OpenID like Interscope Records http://www.interscope.com , User Voice http://www.uservoice.com/session/new , Mixx https://www.mixx.com/login?return=http%3A%2F%2Fwww.mixx.com%2F, etc.
 
One summary of the benefits of supporting multiple third party identity providers can be seen at  http://blog.janrain.com/2009/01/why-websites-should-accept-multiple.html 
 
Near term, offerings like Facebook may have an advantage in execution since they are a closed, proprietary system and can make decisions and implement solutions as decided by only one company.  Longer term, user-centric open standard solutions like OpenID, OAuth, Portable Contacts, OpenSocial,etc. will likely dominate since they have broader support from large players (AOL, Google, IBM, Microsoft, MySpace, Plaxo, Verisign, Yahoo, etc.) as well as an open standards community of individuals and small companies that innovate at a much higher rate than any one company could.  Additionally, there is significant benefit to end users and RPs to adopting open standards approaches vs. proprietary approaches in that interoperability is more likely to happen between websites and services that are open standards based.</description>
		<content:encoded><![CDATA[<p>Thanks to the RWW team for the chance to share our thoughts on OpenID with your readers and listeners.  In only 60 minutes, we couldn&#8217;t completely cover the three topics you had suggested, so I wanted to summarize some thoughts for those who may not have time to listen to the entire podcast. </p>
<p><b>1. How to increase adoption of OpenID</b></p>
<p><b>Better user experience (UX).</b>  The URL type in box works for some users today, but not the mass market yet. Maybe that will change as users become more familiar with OpenID, but we&#8217;re not waiting on that.  We’re working with end users and relying parties (RPs) to determine the “best practices” for UX, which may vary by industry and application.  The Content Provider Advisory Committee meeting in NYC <a href="http://openid.net/2008/10/01/openid-content-provider-advisory-committee-kickoff-meeting/" rel="nofollow">http://openid.net/2008/10/01/openid-content-provider-advisory-committee-kickoff-meeting/</a> and resulting Yahoo UX Summit gave us a lot of thoughts and feedback.  Some specific initiatives aimed at improving UX include Verisign’s Seatbelt, Google’s LSO initiative, Vidoop’s IDIB, JanRain&#8217;s RPX <a href="http://rpxnow.com" rel="nofollow">http://rpxnow.com</a> , and SixApart&#8217;s TypePad Connect.</p>
<p><b>More data for RPs.</b>  All the major OPs are starting to test and implement simple registration (SREG) and/or attribute exchange (AX) to allow users to share standard profile data with RPs including name, nickname, email, gender, DOB, zip code, time zone, language, etc.  This data makes it easier for users to register on a new site, and simpler for website operators to build profiles to personalize their users experiences.  Expect to see even more rich data (interests, friends data, lifestream data, etc.) coming from OpenID providers like the upcoming MySpaceID.</p>
<p><b>Proof Points.</b>  Get thought leaders in various categories to implement OpenID.  For example: Sourceforge &#038; Stack Overflow (developer resources); UserVoice &#038; Get Satisfaction (customer feedback); MapQuest (mapping services); MS HealthVault, AME Health Commission (health care); Plaxo (contact management); CNN, Interscope Records, DailyMotion, RadioPop, &#038; StumbleAudio (media); National 4-H (affinity groups), Oxfam International (non-profits), Portland Trailblazers (sports), etc.</p>
<p><b>Easier deployment options for RPs.</b> Solutions to simplify deployment including blogging platform plugins (TypePad, Wordpress, etc.), Google Friend Connect, MySpaceID, JanRain RPX <a href="http://rpxnow.com" rel="nofollow">http://rpxnow.com</a> , Rails and .Net plugins, etc.</p>
<p><b>Market Research. </b>More thorough understanding of what various market segments want from OpenID. Expand beyond the Content Provider Advisory Committee to add additional Advisory Committees for other market segments and applications.</p>
<p><b>ROI Analysis.</b>  More case studies on quantitative and qualitative benefits for deploying and using OpenID.</p>
<p><b>Education.</b> The major OPs will begin more proactive education of their end users about how to use the OpenIDs they already have.  Additionally, the OpenID Foundation needs to do more seminars, conferences, and other outreach programs with press and analysts to promote awareness and understanding of what OpenID is and what the benefits are for end users and RPs.</p>
<p><b>2. Plans for the OpenID Foundation</b></p>
<p>With the new board recently elected and an executive director search underway, we are still finalizing our plans for 2009, but the activities should align with the goals of driving adoption and usage of OpenID as described above</p>
<p><b>Technology.</b> We now have a solid technology platform and continue to work on extending and enhancing it: Provider Authentication Policy Extension (PAPE), Contract Exchange (CX), OpenID/Oauth, etc.</p>
<p><b>Research.</b> Increased emphasis on “voice of the customer” from end users and RPs – what do they want and need from OpenID and other user centric identity solutions (OAuth, Portable Contacts, Open Social, etc.)  We&#8217;ll do this through our standing committees, working groups, participation in industry events, and advisory committees as discussed above.  Initiatives will certainly include technology specification development and enhancement, but also include services as requested by the market if within the charter of the Foundation.</p>
<p><b>Representation.</b> Expanded OpenID Foundation membership and representation on the board, especially from content providers (media and affinity groups) and other categories of existing and potential RPs.</p>
<p><b>Marketing outreach.</b> Systematically leverage press and analysts interactions, trade shows, blogs, etc. focused on awareness and education</p>
<p><b>Guidelines.</b> Best practice guides for OPs and RPs, tutorials, and other resources as requested</p>
<p><b>Expanded international outreach and coordination.</b>   We now have two international representatives on the OpenID board who have achieved significant results in Japan and Europe.  We&#8217;re also adding an International Liaison to the Executive Committee of the OpenID Foundation.</p>
<p><b> 3. Opinions on Google Friend Connect &#038; Facebook Connect</b></p>
<p>These are great catalysts for showcasing the benefits to website operators and end users of user-centric identity solutions as well as demonstrating compelling UX models.  Facebook and Google have been very involved in sharing their experiences and recommendations with the OpenID Foundation and other open standard initiatives, for which we’re grateful</p>
<p>The market will evolve to embrace the best of what all providers and vendors have to offer, some sites already accept both Facebook Connect and OpenID like Interscope Records <a href="http://www.interscope.com" rel="nofollow">http://www.interscope.com</a> , User Voice <a href="http://www.uservoice.com/session/new" rel="nofollow">http://www.uservoice.com/session/new</a> , Mixx <a href="https://www.mixx.com/login?return=http%3A%2F%2Fwww.mixx.com%2F," rel="nofollow">https://www.mixx.com/login?return=http%3A%2F%2Fwww.mixx.com%2F,</a> etc.</p>
<p>One summary of the benefits of supporting multiple third party identity providers can be seen at  <a href="http://blog.janrain.com/2009/01/why-websites-should-accept-multiple.html" rel="nofollow">http://blog.janrain.com/2009/01/why-websites-should-accept-multiple.html</a> </p>
<p>Near term, offerings like Facebook may have an advantage in execution since they are a closed, proprietary system and can make decisions and implement solutions as decided by only one company.  Longer term, user-centric open standard solutions like OpenID, OAuth, Portable Contacts, OpenSocial,etc. will likely dominate since they have broader support from large players (AOL, Google, IBM, Microsoft, MySpace, Plaxo, Verisign, Yahoo, etc.) as well as an open standards community of individuals and small companies that innovate at a much higher rate than any one company could.  Additionally, there is significant benefit to end users and RPs to adopting open standards approaches vs. proprietary approaches in that interoperability is more likely to happen between websites and services that are open standards based.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
 

