This is very nice. <div><br> </div><div>In fact, in our announcement of OpenID Japan, we have articulated four out of the five RP benefits below stated. One missing one was "Thought Leadership". </div><div><br> </div>
<div>These are publicized through magazines etc., and hopefully, will change the peoples mind. </div><div><br> </div><div>Also, we have to address the trust problem. </div><div><br> </div><div>That is why I am pushing for a working group on reputation and certification scoring. </div>
<div><br> </div><div>=nat</div><div><br> </div><div><br><br><div><span class="gmail_quote">2008/3/20, Brendon J. Wilson <<a href="mailto:brendon.wilson@gmail.com">brendon.wilson@gmail.com</a>>:</span><blockquote class="gmail_quote" style="margin:0;margin-left:0.8ex;border-left:1px #ccc solid;padding-left:1ex">
+1 Snorri's comment.<br> <br> I've been looking at OpenID for a client, and as I survey the OpenID<br> landscape it's become apparent very quickly that there's lots of<br> identity providers, but not a lot of relying parties. Any of the big<br>
players seem to be staying out of that space, with the exception of<br> the blog platforms and open source CMS systems. Examples: AOL - only<br> Propeller seems to have OpenID as a login option. Yahoo! - haven't<br> found an OpenID login yet. All of the focus right now seems to be on<br>
getting people to get an OpenID.<br> <br> I think any discussion of how to evangelize OpenID to the general<br> public also requires the foundation to clearly articulate the value of<br> being a relying party, otherwise we risk stalled growth when users<br>
finally decide to get an OpenID, but have nowhere to use it. JanRain<br> claims 8,000 relying parties, but I've seen little justification for<br> that number; OpenIDDirectory.com lists about 530 or so OpenID-related<br>
sites, and 60 or so of them are identity providers. Demonstrating<br> value to potential relaying parties also requires showing, in no<br> uncertain terms, just how many people already use it.<br> <br> I'd like to propose the following strawman benefits of being a relying<br>
party for the group to eviscerate (warning: businesspeak ahead):<br> <br> 1) Expedited customer acquisition: OpenID allows user to quickly and<br> easily complete the account creation process by eliminating entry of<br> commonly requested fields (email address, sex, birthdate), thus<br>
reducing the friction to adopt a new service.<br> <br> 2) Reduced user account management costs: The primary cost for most IT<br> organizations is resetting forgotten authentication credentials. By<br> reducing the number of credentials, a user is less likely to forget<br>
their credentials. By outsourcing the authentication process to a<br> third-party, the relying party can avoid those costs entirely.<br> <br> 3) "Thought leadership": There is an inherent marketing value for an<br>
organization to associate itself activities that promote it as a<br> thought leader. It provides an organization with the means to<br> distinguish itself from its competitors. This is your chance to<br> outpace your competitors.<br>
<br> 4) Your competitors are already doing it: Whoops! So you missed out on<br> number 4, so you have to do it, otherwise you're falling behind the<br> times. Ketchup!<br> <br> 5) Simplified user experience: Logical follow on from 1 & 2. However,<br>
it's at the end of the list because that's not the business priority.<br> The business priority is the benefit that results from a simplified<br> user experience, not the simplified user experience itself.<br> <br>
Thoughts?<br> <br> Brendon<br> ---<br> <br>Brendon J. Wilson<br> <a href="http://www.brendonwilson.com">www.brendonwilson.com</a><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">http://openid.net/mailman/listinfo/general</a><br> </blockquote></div><br><br clear="all"><br>-- <br>Nat Sakimura (=nat)<br><a href="http://www.sakimura.org/en/">http://www.sakimura.org/en/</a>
</div>