<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Yahoo to support OpenID 2.0</title>
	<atom:link href="http://blogs.kuppingercole.com/gaehtgens/2008/01/21/yahoo-to-support-openid-20/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.kuppingercole.com/gaehtgens/2008/01/21/yahoo-to-support-openid-20/</link>
	<description>Kuppinger Cole</description>
	<lastBuildDate>Fri, 04 May 2012 06:56:02 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Carsten P&#246;tter</title>
		<link>http://blogs.kuppingercole.com/gaehtgens/2008/01/21/yahoo-to-support-openid-20/comment-page-1/#comment-113</link>
		<dc:creator>Carsten P&#246;tter</dc:creator>
		<pubDate>Sat, 09 Feb 2008 13:19:00 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.kuppingercole.de/gaehtgens/2008/01/21/yahoo-to-support-openid-20/#comment-113</guid>
		<description>Actually AOL is consuming OpenIDs as well; though it is whitelisting providers (&lt;a href=&quot;http://dev.aol.com/node/578). &quot;&gt;http://dev.aol.com/node/578). &lt;/a&gt;&lt;br /&gt;
The IPR policy is finalized since the end of December, btw. </description>
		<content:encoded><![CDATA[<p>Actually AOL is consuming OpenIDs as well; though it is whitelisting providers (<a href="http://dev.aol.com/node/578). "></a><a href="http://dev.aol.com/node/578" rel="nofollow">http://dev.aol.com/node/578</a>). <br />
The IPR policy is finalized since the end of December, btw. </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Carsten Pötter</title>
		<link>http://blogs.kuppingercole.com/gaehtgens/2008/01/21/yahoo-to-support-openid-20/comment-page-1/#comment-17</link>
		<dc:creator>Carsten Pötter</dc:creator>
		<pubDate>Sat, 09 Feb 2008 12:19:00 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.kuppingercole.de/gaehtgens/2008/01/21/yahoo-to-support-openid-20/#comment-17</guid>
		<description>Actually AOL is consuming OpenIDs as well; though it is whitelisting providers (&lt;a href=&quot;http://dev.aol.com/node/578&quot; rel=&quot;nofollow&quot;&gt;http://dev.aol.com/node/578&lt;/a&gt;). &lt;br&gt;&lt;br&gt; 

The IPR policy is finalized since the end of December, btw.  </description>
		<content:encoded><![CDATA[<p>Actually AOL is consuming OpenIDs as well; though it is whitelisting providers (<a href="http://dev.aol.com/node/578" rel="nofollow">http://dev.aol.com/node/578</a>). </p>
<p>The IPR policy is finalized since the end of December, btw.  </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sampo_kello4686</title>
		<link>http://blogs.kuppingercole.com/gaehtgens/2008/01/21/yahoo-to-support-openid-20/comment-page-1/#comment-117</link>
		<dc:creator>sampo_kello4686</dc:creator>
		<pubDate>Tue, 22 Jan 2008 15:44:54 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.kuppingercole.de/gaehtgens/2008/01/21/yahoo-to-support-openid-20/#comment-117</guid>
		<description>OpenID is on path of reinventing the wheel: SAML 2.0 addresses broad &lt;br /&gt;
spectrum of use cases from zero-trust (aka OpenID 1.1) to enterprise &lt;br /&gt;
grade managed trust. OpenID&#039;s percieved &quot;lightness&quot; evaporates as it &lt;br /&gt;
tries to address the use cases where trust matters - in the end it &lt;br /&gt;
will be just about as complicated and as &quot;heavy weight&quot; as SAML, but &lt;br /&gt;
it is a new wheel. Or conversely, when SAML is deployed with OpenIDish &lt;br /&gt;
trust, then it is just as light weight. OpenID&#039;s &quot;openness&quot; is also &lt;br /&gt;
suspect: while spec is available and many open source implementations &lt;br /&gt;
exist, there is curious silence about IPR licensing. While various &lt;br /&gt;
vague promises &quot;not to sue&quot; have been circulated, there is scant &lt;br /&gt;
little contractual obligations to back these up. &lt;br /&gt;
 </description>
		<content:encoded><![CDATA[<p>OpenID is on path of reinventing the wheel: SAML 2.0 addresses broad <br />
spectrum of use cases from zero-trust (aka OpenID 1.1) to enterprise <br />
grade managed trust. OpenID&#039;s percieved &quot;lightness&quot; evaporates as it <br />
tries to address the use cases where trust matters &#8211; in the end it <br />
will be just about as complicated and as &quot;heavy weight&quot; as SAML, but <br />
it is a new wheel. Or conversely, when SAML is deployed with OpenIDish <br />
trust, then it is just as light weight. OpenID&#039;s &quot;openness&quot; is also <br />
suspect: while spec is available and many open source implementations <br />
exist, there is curious silence about IPR licensing. While various <br />
vague promises &quot;not to sue&quot; have been circulated, there is scant <br />
little contractual obligations to back these up. </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sampo Kellomäki</title>
		<link>http://blogs.kuppingercole.com/gaehtgens/2008/01/21/yahoo-to-support-openid-20/comment-page-1/#comment-16</link>
		<dc:creator>Sampo Kellomäki</dc:creator>
		<pubDate>Tue, 22 Jan 2008 14:44:54 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.kuppingercole.de/gaehtgens/2008/01/21/yahoo-to-support-openid-20/#comment-16</guid>
		<description>OpenID is on path of reinventing the wheel: SAML 2.0 addresses broad spectrum of use cases from zero-trust (aka OpenID 1.1) to enterprise grade managed trust. OpenID&#039;s percieved &quot;lightness&quot; evaporates as it tries to address the use cases where trust matters - in the end it  will be just about as complicated and as &quot;heavy weight&quot; as SAML, but it is a new wheel. Or conversely, when SAML is deployed with OpenIDish trust, then it is just as light weight. &lt;br&gt;&lt;br&gt;OpenID&#039;s &quot;openness&quot; is also suspect: while spec is available and many open source implementations exist, there is curious silence about IPR licensing. While various vague promises &quot;not to sue&quot; have been circulated, there is scant little contractual obligations to back these up.</description>
		<content:encoded><![CDATA[<p>OpenID is on path of reinventing the wheel: SAML 2.0 addresses broad spectrum of use cases from zero-trust (aka OpenID 1.1) to enterprise grade managed trust. OpenID&#8217;s percieved &#8220;lightness&#8221; evaporates as it tries to address the use cases where trust matters &#8211; in the end it  will be just about as complicated and as &#8220;heavy weight&#8221; as SAML, but it is a new wheel. Or conversely, when SAML is deployed with OpenIDish trust, then it is just as light weight. </p>
<p>OpenID&#8217;s &#8220;openness&#8221; is also suspect: while spec is available and many open source implementations exist, there is curious silence about IPR licensing. While various vague promises &#8220;not to sue&#8221; have been circulated, there is scant little contractual obligations to back these up.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

