No subject

<BR>
&#8220;</SPAN></FONT><FONT SIZE=3D"2"><FONT FACE=3D"Lucida Grande"><SPAN ST=
YLE=3D'font-size:10pt'>The Service Provider&#8217;s responsibility is to en=
able Consumer Developers to establish a Consumer Key and Consumer Secret. T=
he process and requirements for provisioning these are entirely up to the S=
ervice Providers.&#8221;<BR>
</SPAN></FONT></FONT><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPA=
N STYLE=3D'font-size:11pt'><BR>
This highlights the fact that in order to build a truly useful stack, we ne=
ed to extend the core specs to allow for more data flow. The OpenID/OAuth h=
ybrid is a great example of the kind of work that&#8217;s going on to enabl=
e that. <BR>
<BR>
On 4/2/09 10:46 AM, &quot;Martin Atkins&quot; &lt;<a href=3D"mart at degenerat=
ion.co.uk">mart at degeneration.co.uk</a>&gt; wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"=
><SPAN STYLE=3D'font-size:11pt'>Allen Tom wrote:<BR>
&gt; santrajan wrote:<BR>
&gt;&gt; As a side note myspace has come out with there own version of Open=
ID<BR>
&gt;&gt; support, which is not compatible with the OpenID specification. An=
other<BR>
&gt;&gt; example of vested interests tearing apart the concept of OpenID.<B=
R>
&gt;<BR>
&gt; Can you elaborate on this? As far as I can tell, MySpace has implement=
ed<BR>
&gt; OpenID 2.0 along with the OpenID OAuth Extension. The OpenID &nbsp;OAu=
th<BR>
&gt; Extension is not finalized yet, but there is a &nbsp;draft spec availa=
ble.<BR>
&gt;<BR>
<BR>
MySpaceID currently requires an application to be pre-registered with<BR>
MySpace, so it doesn't do ad-hoc interop as most OpenID Providers do.<BR>
<BR>
_______________________________________________<BR>
general mailing list<BR>
<a href=3D"general at openid.net">general at openid.net</a><BR>
<a href=3D"http://openid.net/mailman/listinfo/general">http://openid.net/ma=
ilman/listinfo/general</a><BR>
<BR>
</SPAN></FONT></BLOCKQUOTE>
</BODY>
</HTML>


--_000_C5FA4A9B291A3lshepardfacebookcom_--