<?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: Sun Defends Open Source Cred Badly</title>
	<atom:link href="http://obviousdiversion.com/technology/sun-open-source-credentials/feed/" rel="self" type="application/rss+xml" />
	<link>http://obviousdiversion.com/technology/sun-open-source-credentials/</link>
	<description></description>
	<pubDate>Sat, 22 Nov 2008 03:51:45 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7-beta3</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Simon Phipps</title>
		<link>http://obviousdiversion.com/technology/sun-open-source-credentials/comment-page-1/#comment-123</link>
		<dc:creator>Simon Phipps</dc:creator>
		<pubDate>Sat, 09 Oct 2004 00:39:53 +0000</pubDate>
		<guid isPermaLink="false">http://obviousdiversion.com/?p=119#comment-123</guid>
		<description>The language is there because Sun had been suing Microsoft for anticompetitive behaviour concerning Office, and this is part of Microsoft's settlement of the case. You are entitled to your opinion on that, which I don't share because it's based on an attempt to use general thinking on a technical document, but you should equally weight the commitment Jonathan Schwartz made to stand by the OpenOffice.org community in his reply to a journalist making a similar assertion (misinterpreted by Michael Tiemann as an attack on himself and people like him).</description>
		<content:encoded><![CDATA[<p>The language is there because Sun had been suing Microsoft for anticompetitive behaviour concerning Office, and this is part of Microsoft&#8217;s settlement of the case. You are entitled to your opinion on that, which I don&#8217;t share because it&#8217;s based on an attempt to use general thinking on a technical document, but you should equally weight the commitment Jonathan Schwartz made to stand by the OpenOffice.org community in his reply to a journalist making a similar assertion (misinterpreted by Michael Tiemann as an attack on himself and people like him).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Christian Gloddy</title>
		<link>http://obviousdiversion.com/technology/sun-open-source-credentials/comment-page-1/#comment-122</link>
		<dc:creator>Christian Gloddy</dc:creator>
		<pubDate>Fri, 08 Oct 2004 21:13:20 +0000</pubDate>
		<guid isPermaLink="false">http://obviousdiversion.com/?p=119#comment-122</guid>
		<description>I have fixed my link, but I first discovered this in the &lt;a href="http://seattlepi.nwsource.com/business/190801_openoffice15.html"&gt;Seattle P-I article on the subject&lt;/a&gt;.  &lt;a href="http://www.linuxelectrons.com/article.php/20040914141417417"&gt;LinuxElectrons points out the language used in litigation&lt;/a&gt;.  I have yet to see a retraction or correction from the Seattle P-I on the subject.  I refer to LinuxElectrons simply to see the language itself.

Far from omitting language about OpenOffice in the litigation at all, it is specifically singled out as not being protected beyond a certain date.  This doesn't play well into a 'there was nothing Sun could do' defense.  Clearly, Sun did do something and it was to clarify the future vulnerability of OpenOffice in relation to the safety secured for Sun's other initiatives.

I have no doubt that OpenOffice will roll along for some time, but if it should ever become a threat in the marketplace to other commercial solutions, the ability to bury it legally has been aided by Sun's agreement.</description>
		<content:encoded><![CDATA[<p>I have fixed my link, but I first discovered this in the <a href="http://seattlepi.nwsource.com/business/190801_openoffice15.html">Seattle P-I article on the subject</a>.  <a href="http://www.linuxelectrons.com/article.php/20040914141417417">LinuxElectrons points out the language used in litigation</a>.  I have yet to see a retraction or correction from the Seattle P-I on the subject.  I refer to LinuxElectrons simply to see the language itself.</p>
<p>Far from omitting language about OpenOffice in the litigation at all, it is specifically singled out as not being protected beyond a certain date.  This doesn&#8217;t play well into a &#8216;there was nothing Sun could do&#8217; defense.  Clearly, Sun did do something and it was to clarify the future vulnerability of OpenOffice in relation to the safety secured for Sun&#8217;s other initiatives.</p>
<p>I have no doubt that OpenOffice will roll along for some time, but if it should ever become a threat in the marketplace to other commercial solutions, the ability to bury it legally has been aided by Sun&#8217;s agreement.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Simon Phipps</title>
		<link>http://obviousdiversion.com/technology/sun-open-source-credentials/comment-page-1/#comment-121</link>
		<dc:creator>Simon Phipps</dc:creator>
		<pubDate>Fri, 08 Oct 2004 13:06:04 +0000</pubDate>
		<guid isPermaLink="false">http://obviousdiversion.com/?p=119#comment-121</guid>
		<description>Do tell me what you're alluding to and how your view is authoritative (the link you provide to yourself is broken). 

My sources (involved in the litigation first-hand) tell me that nothing has changed with regard to OpenOffice.org and liability - like all open source projects it has no defence from patent claims and there was nothing Sun could do to force Microsoft to create any haven outside the bound of a corporation - not really a surprise since anything &#038; anyone could have taken haven in it once created, as far as they are concerned. Someone commented that "you get what you negotiate for" but that's only true if what you negotiate for is actually possible. 

Far from throwing OpenOffice.org in the path of destruction, Sun has invested in a rewrite that makes community involvement much easier, has created import filters for the Office XML formats to release into the LGPLed source and is ensuring the OpenOffice.org file format is standardised and widely used in government so that any attack by a patent farmer looks ridiculous. If you have other realistic views about how to solve the disgusting problem that software patents place in the path of F/OSS I would be pleased to hear it.</description>
		<content:encoded><![CDATA[<p>Do tell me what you&#8217;re alluding to and how your view is authoritative (the link you provide to yourself is broken). </p>
<p>My sources (involved in the litigation first-hand) tell me that nothing has changed with regard to OpenOffice.org and liability - like all open source projects it has no defence from patent claims and there was nothing Sun could do to force Microsoft to create any haven outside the bound of a corporation - not really a surprise since anything &#038; anyone could have taken haven in it once created, as far as they are concerned. Someone commented that &#8220;you get what you negotiate for&#8221; but that&#8217;s only true if what you negotiate for is actually possible. </p>
<p>Far from throwing OpenOffice.org in the path of destruction, Sun has invested in a rewrite that makes community involvement much easier, has created import filters for the Office XML formats to release into the LGPLed source and is ensuring the OpenOffice.org file format is standardised and widely used in government so that any attack by a patent farmer looks ridiculous. If you have other realistic views about how to solve the disgusting problem that software patents place in the path of F/OSS I would be pleased to hear it.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
