<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet title="XSL_formatting" type="text/xsl" href="/blogs/shared/nolsol.xsl"?>

<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>

<title>
BBC Internet Blog
 - 
Zac Bjelogrlic
</title>
<link>https://bbcbreakingnews.pages.dev/blogs/bbcinternet/</link>
<description>Staff from the BBC&apos;s online and technology teams talk about BBC Online, BBC iPlayer, and the BBC&apos;s digital and mobile services. The blog is reactively moderated. Posts are normally closed for comment after three months. Your host is Eliza Kessler. </description>
<language>en</language>
<copyright>Copyright 2012</copyright>
<lastBuildDate>Fri, 03 Oct 2008 17:00:25 +0000</lastBuildDate>
<generator>http://www.sixapart.com/movabletype/?v=4.33-en</generator>
<docs>http://blogs.law.harvard.edu/tech/rss</docs> 


<item>
	<title>OpenID Foundation Meeting: what is OpenID today?</title>
	<description><![CDATA[<p>Earlier this year, Jem Stone <a href="https://bbcbreakingnews.pages.dev/blogs/bbcinternet/2008/04/bbc_joins_openid_foundation.html">blogged</a> that the BBC had joined the OpenID Foundation.</p>

<p>And a week ago, the BBC hosted a meeting of the <a href="http://openid.net/foundation/">OpenID Foundation</a> Content Provider Advisory Committee in New York. </p>

<p>I was there, among the BBC people and participants from major media companies. This was the first time that we had participation from a wide collection of companies interested in the possibilities of OpenID.</p>

<p>There is <a href="http://openid.net/2008/10/01/openid-content-provider-advisory-committee-kickoff-meeting/">more detail</a> about the meeting at the Foundation's blog.</p>

<p>The committee gathered quite a selection of companies interested in understanding how web audiences can benefit from OpenID and where it fits into the business of a media or content company.</p>

<p align="center"><img alt="openid_orgs.png" src="https://bbcbreakingnews.pages.dev/blogs/bbcinternet/img/openid_orgs.png" width="430" height="220" /></p>

<p>So what is OpenID? </p>

<p>The <a href="http://openid.net/what/">concept</a> is simple.</p>

<p>OpenID eliminates the need for multiple usernames across different websites, simplifying your online experience. It's based on a federated approach and relatively simple standards. Open source solutions are available for both providers and consumers. </p>

<p>While the original protocol for Open ID was <a href="http://community.livejournal.com/lj_dev/683939.html">developed in 2005</a>, significant changes happened only last year. Big internet players like <a href="http://openid.yahoo.com/">Yahoo!</a>, <a href="http://developer.myspace.com/Community/blogs/devteam/archive/tags/OpenID/default.aspx">MySpace</a>, <a href="http://dev.aol.com/aol-and-63-million-openids">AOL</a>, Google as well as telecoms like <a href="http://www.orange.fr/bin/frame.cgi?u=http%3A//openid.orange.fr/home/noint/">Orange</a> and <a href="http://www.openideurope.eu/2008/07/31/telecom-italia-alice-adopt-openid/">Telecom Italia</a> joined the fray and are now offering OpenIDs to users. They are "identity providers".</p>

<p align="center"><img alt="open_id_meeting.jpg" src="https://bbcbreakingnews.pages.dev/blogs/bbcinternet/img/open_id_meeting.jpg" width="429" height="287"  /><br><em><small>Participants at the OpenID Foundation Content Provider Advisory Committe meeting</small></em></p>

<p>By the end of September 2007, over 22,000 sites were accepting OpenID logins.</p>

<p>However, as you may note from the numbers above, the landscape is unbalanced: there are a few big providers and myriad small consumers. Only bloggers and a few social sites show a balanced model where sites are providers and consumers at the same time.</p>

<p>There's a strong sense of momentum, but it needs a slightly more critical approach.</p>

<p>On paper, there are hundreds of millions of OpenID-enabled users. In practice, these are <em>potential users</em> and few of them even know that OpenID exists. Figures on the real adoption rate are not easy to obtain and the precise profile of initial users is even more difficult. </p>

<p>At first glance, it would be easy to define OpenID as just <em>a geek's wave</em> - a phenomenon limited to a small proportion of web-savvy people actively participating on different blogs or present in multiple social spaces. And the cynical might say that the big internet players' participation is an identity landgrab - taking part in OpenID in case something significant develops. </p>

<p>For average users, the OpenID user experience is still very poor, for two main reasons:<ul><li>First, you can be redirected from one website (the one accepting the identifier) to a different domain (that of the provider) and then returned to the first. This is confusing for an average user, especially if different wording, layout and styles are used. The attribute exchange part of the OpenID protocol works: it's a good idea to exchange the <a href="http://openid.net/specs/openid-simple-registration-extension-1_0.html">registration parameters</a> and to simplify steps at the receiving site. However, if implemented badly (or not implemented at all), it adds even more confusion to the journey. The confusion also adds a weak point where <a href="http://www.direct.gov.uk/en/Governmentcitizensandrights/Yourrightsandresponsibilities/DG_10031451">scammers</a> and <a href="http://news.bbc.co.uk/1/shared/spl/hi/picture_gallery/06/technology_how_to_spot_a_phish/html/2.stm">phishers</a> can jump in.</li><li>Second, all users are familiar with the username and password as the login paradigm. Suddenly using URLs, like http://openid.foo.bar/john/smith, may be difficult for a mainstream user to understand.<br>(However, the <a href="http://www.businessweek.com/magazine/content/05_50/b3963001.htm">so-called "Generation @"</a>, which uses instant messaging and social spaces as well as traditional email, is aging, and so the main audience segments will be people used to representing themselves with the URL of a blog, MySpace profile or Flickr account).</li></ul></p>

<p>Security is also not at the level that I (and the BBC) want to see. With <a href="http://openid.net/specs/openid-provider-authentication-policy-extension-1_0-02.html">improvements around the corner</a>, this will improve. But more complex problems are responsibility and liability in the case of misuse. Who is responsible in a fully federated system?</p>

<p>Let's return to my first question. Where is the value for our audience and where is the business case for a media company?</p>

<p>It is difficult to give a precise answer today, but two aspects are emerging.<ul><li>First, an OpenID ecosystem that is simple to use and which allows sharing of user attributes would help with the migration of users from site to site. This can be a simple way to offer progressive services and content to new users.</li><li>Second, OpenID can be used to make participation in social features much wider. Participation can be opened up as much as possible to avoid limiting it to a single social site.</li></ul></p>

<p>This is how OpenID is used for commenting across different blogging systems and at <a href="http://www.radiopop.co.uk/">Radio Pop</a>, the <a href="https://bbcbreakingnews.pages.dev/blogs/radiolabs/2008/09/radio_pop_social_radio_listeni.shtml">social radio site</a> that's the BBC's first OpenID prototype.</p>

<p><img alt="openid_user_privacy430.jpg" src="https://bbcbreakingnews.pages.dev/blogs/bbcinternet/img/openid_user_privacy430.jpg" width="430" height="400"/></p>

<p><strong>So what's the value for audiences?</strong></p>

<p>&bull; Better personalised or localised services without the burden of full registration</p>

<p>&bull; An "appetiser" before accessing the full menu of services</p>

<p>&bull; More freedom to pick a social site and "be yourself" independently of the web platform used</p>

<p><strong>And what would businesses and media providers get out of OpenID?</strong></p>

<p>&bull; Better user acquisition rate and lower cost per user</p>

<p>&bull; Wider user base for social features and more space to develop viral effects</p>

<p>&bull; More flexibility in making agreements with social sites</p>

<p>Of course, the high figures of potential OpenID users must be matched with the real adoption rate and the demographics of "Generation @".</p>

<p><strong>What can the BBC and others do, in addition to watching from the coast what's happening in the OpenID ocean? </strong></p>

<p>Here are some simple possibilities: </p>

<p>&bull; Work on best practice shared among providers and consumers.</p>

<p>&bull; Improve radically the user experience and simplify it to so that it is more intuitive and easier for mainstream users - the user experience is shared and needs to be modified in co-operation between providers and consumers</p>

<p>&bull; Share basic registration data, with the explicit approval of the user. Email and date of birth are essential and other data desirable. This is a core point for any content provider to become a consumer of OpenID. </p>

<p>&bull; Work on common presentation and explanation of OpenID - part of the BBC's <a href="https://bbcbreakingnews.pages.dev/info/purpose/">mission</a> to "educate" - to make people ready for Internet of today and tomorrow...</p>

<p>An informal working group and a simple prototype or pilot applications is probably the best way to continue the work. </p>

<p>It's important that this is shared among providers and media companies so that all aspects of the OpenID ecosystem can be tested and improved.</p>

<p>How do you think OpenID could be improved and how do you think it could be used?</p>

<p>What do you think the BBC should do?</p>

<p>Please do leave a comment.</p>

<p><em>Zac Bjelogrlic is Programme Manager, BBC Future Media & Technology.</em></p>]]></description>
         <dc:creator>Zac Bjelogrlic 
Zac Bjelogrlic
</dc:creator>
	<link>https://bbcbreakingnews.pages.dev/blogs/bbcinternet/2008/10/openid_foundation_meeting_what.html</link>
	<guid>https://bbcbreakingnews.pages.dev/blogs/bbcinternet/2008/10/openid_foundation_meeting_what.html</guid>
	<category>social</category>
	<pubDate>Fri, 03 Oct 2008 17:00:25 +0000</pubDate>
</item>


</channel>
</rss>

 
