<?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: Improving my vision: Some views on Microsoft&#8217;s Open Specification Promise</title>
	<atom:link href="http://confusedofcalcutta.com/2006/09/13/improving-my-vision-some-views-on-microsofts-open-specification-promise/feed/" rel="self" type="application/rss+xml" />
	<link>http://confusedofcalcutta.com/2006/09/13/improving-my-vision-some-views-on-microsofts-open-specification-promise/</link>
	<description>a blog about information</description>
	<lastBuildDate>Mon, 06 Feb 2012 01:37:12 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Thought Leadership</title>
		<link>http://confusedofcalcutta.com/2006/09/13/improving-my-vision-some-views-on-microsofts-open-specification-promise/comment-page-1/#comment-59172</link>
		<dc:creator>Thought Leadership</dc:creator>
		<pubDate>Thu, 28 Dec 2006 15:08:27 +0000</pubDate>
		<guid isPermaLink="false">http://confusedofcalcutta.com/2006/09/13/improving-my-vision-some-views-on-microsofts-open-specification-promise/#comment-59172</guid>
		<description>&lt;strong&gt;Maybe open source isn&#039;t all that open?...&lt;/strong&gt;

Tom Elrod of JBoss suggests...</description>
		<content:encoded><![CDATA[<p><strong>Maybe open source isn&#8217;t all that open?&#8230;</strong></p>
<p>Tom Elrod of JBoss suggests&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kim Cameron&#8217;s Identity Weblog &#187; Jamie Lewis on Open Specification Promise</title>
		<link>http://confusedofcalcutta.com/2006/09/13/improving-my-vision-some-views-on-microsofts-open-specification-promise/comment-page-1/#comment-9025</link>
		<dc:creator>Kim Cameron&#8217;s Identity Weblog &#187; Jamie Lewis on Open Specification Promise</dc:creator>
		<pubDate>Mon, 25 Sep 2006 20:01:43 +0000</pubDate>
		<guid isPermaLink="false">http://confusedofcalcutta.com/2006/09/13/improving-my-vision-some-views-on-microsofts-open-specification-promise/#comment-9025</guid>
		<description>[...] As has been widely reported, Microsoft announced its Open Specification Promise last week. A lot of folks have already posted about it (see here, here, and here ). But, given the overall importance of the announcement to the identity community, I wanted to make our thoughts on the subject known, and to give credit where itâ€™s due. (Note: This entry is cross posted at both my blog and our new Identity and Privacy Strategies blog.) In summary, Microsoft has decided to offer the Open Specification Promise (OSP) for the Web services protocols that support CardSpace in particular, and the InfoCards architecture in general. The OSP provides an alternative to Microsoftâ€™s â€œreasonable and non discriminatory/royalty freeâ€ (RAND/RF) licensing agreement, which most open source developers didnâ€™t like. As I understand it, the OSP essentially provides an assurance that Microsoft wonâ€™t sue anyone implementing the specifications covered by the document. So developers donâ€™t even have to agree to a license; they can implement the covered specifications without fear of being sued. (With certain, mostly comprehensible exceptions.) [...]</description>
		<content:encoded><![CDATA[<p>[...] As has been widely reported, Microsoft announced its Open Specification Promise last week. A lot of folks have already posted about it (see here, here, and here ). But, given the overall importance of the announcement to the identity community, I wanted to make our thoughts on the subject known, and to give credit where itâ€™s due. (Note: This entry is cross posted at both my blog and our new Identity and Privacy Strategies blog.) In summary, Microsoft has decided to offer the Open Specification Promise (OSP) for the Web services protocols that support CardSpace in particular, and the InfoCards architecture in general. The OSP provides an alternative to Microsoftâ€™s â€œreasonable and non discriminatory/royalty freeâ€ (RAND/RF) licensing agreement, which most open source developers didnâ€™t like. As I understand it, the OSP essentially provides an assurance that Microsoft wonâ€™t sue anyone implementing the specifications covered by the document. So developers donâ€™t even have to agree to a license; they can implement the covered specifications without fear of being sued. (With certain, mostly comprehensible exceptions.) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Yeomans</title>
		<link>http://confusedofcalcutta.com/2006/09/13/improving-my-vision-some-views-on-microsofts-open-specification-promise/comment-page-1/#comment-7768</link>
		<dc:creator>Andrew Yeomans</dc:creator>
		<pubDate>Thu, 14 Sep 2006 13:38:35 +0000</pubDate>
		<guid isPermaLink="false">http://confusedofcalcutta.com/2006/09/13/improving-my-vision-some-views-on-microsofts-open-specification-promise/#comment-7768</guid>
		<description>See Jerry Fishenden&#039;s suggestion http://ntouk.com/?view=plink&amp;id=135 of a Creative-Commons-style approach to a Data Protection licence. Jerry also has suggested the same approach could be made for software licences and EULAs.</description>
		<content:encoded><![CDATA[<p>See Jerry Fishenden&#8217;s suggestion <a href="http://ntouk.com/?view=plink&#038;id=135" rel="nofollow">http://ntouk.com/?view=plink&#038;id=135</a> of a Creative-Commons-style approach to a Data Protection licence. Jerry also has suggested the same approach could be made for software licences and EULAs.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

