<?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: Steve Ballmer Accused of Bending Report on Patents, Gets Perfect Punishement</title>
	<atom:link href="http://techrights.org/2007/05/16/report-bend/feed/" rel="self" type="application/rss+xml" />
	<link>http://techrights.org/2007/05/16/report-bend/</link>
	<description>Free Software Sentry – watching and reporting maneuvers of those threatened by software freedom</description>
	<lastBuildDate>Tue, 07 Feb 2012 14:00:35 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: gpl1</title>
		<link>http://techrights.org/2007/05/16/report-bend/comment-page-1/#comment-714</link>
		<dc:creator>gpl1</dc:creator>
		<pubDate>Thu, 17 May 2007 03:27:04 +0000</pubDate>
		<guid isPermaLink="false">http://boycottnovell.com/2007/05/16/report-bend/#comment-714</guid>
		<description>&quot;2) the IP access necessary for the technical collaboration to deliver interoperability between Windows and Linux.&quot;

Interesting, the same IP which EC Commissioner Neelie Kroes viewed as obvious and non-innovative...yes, I think MS is trying to outmaneuver the EC&#039;s decision on their antitrust non-compliance.

&quot;Microsoft has said it would charge for interoperability information because it was based on the company&#039;s own innovative work and protected by patents.

But the Commission charged in March this year that competitors gave away such software whether or not it was patented.

&quot;The Commission&#039;s current view is that there is no significant innovation in these protocols,&quot; European Competition Commissioner Neelie Kroes said in a statement that month.

&quot;I am therefore again obliged to take formal measures to ensure that Microsoft complies with its obligations,&quot; she said. 


http://www.crn.com/software/199200601 &quot;

http://boycottnovell.com/2007/05/04/novell-spin-deal/
http://boycottnovell.com/2007/01/19/microsoft-corrupts-term/
http://boycottnovell.com/2006/11/24/what-about-the-ec-ruling/</description>
		<content:encoded><![CDATA[<p>&#8220;2) the IP access necessary for the technical collaboration to deliver interoperability between Windows and Linux.&#8221;</p>
<p>Interesting, the same IP which EC Commissioner Neelie Kroes viewed as obvious and non-innovative&#8230;yes, I think MS is trying to outmaneuver the EC&#8217;s decision on their antitrust non-compliance.</p>
<p>&#8220;Microsoft has said it would charge for interoperability information because it was based on the company&#8217;s own innovative work and protected by patents.</p>
<p>But the Commission charged in March this year that competitors gave away such software whether or not it was patented.</p>
<p>&#8220;The Commission&#8217;s current view is that there is no significant innovation in these protocols,&#8221; European Competition Commissioner Neelie Kroes said in a statement that month.</p>
<p>&#8220;I am therefore again obliged to take formal measures to ensure that Microsoft complies with its obligations,&#8221; she said. </p>
<p><a href="http://www.crn.com/software/199200601" rel="nofollow">http://www.crn.com/software/199200601</a> &#8221;</p>
<p><a href="http://boycottnovell.com/2007/05/04/novell-spin-deal/" rel="nofollow">http://boycottnovell.com/2007/05/04/novell-spin-deal/</a><br />
<a href="http://boycottnovell.com/2007/01/19/microsoft-corrupts-term/" rel="nofollow">http://boycottnovell.com/2007/01/19/microsoft-corrupts-term/</a><br />
<a href="http://boycottnovell.com/2006/11/24/what-about-the-ec-ruling/" rel="nofollow">http://boycottnovell.com/2006/11/24/what-about-the-ec-ruling/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: shane</title>
		<link>http://techrights.org/2007/05/16/report-bend/comment-page-1/#comment-705</link>
		<dc:creator>shane</dc:creator>
		<pubDate>Wed, 16 May 2007 15:10:21 +0000</pubDate>
		<guid isPermaLink="false">http://boycottnovell.com/2007/05/16/report-bend/#comment-705</guid>
		<description>In my experience, Novell PR is pretty fair about their moderating (more than 75% of my comments are allowed, even with links to this site refuting their statements.)

My newest:

#  Bruce Lowry Says:
May 15th, 2007 at 5:24 pm

A quick point of correction on an issue raised in several of these comments. The Novell-Microsoft patent agreement frequently gets reported in the press as a cross-license, but it isn’t. Novell did not cross-license any patents with Microsoft. Novell and Microsoft made an agreement not to sue one another’s customers over patent issues. So we don’t have the rights to use Microsoft patents in Novell technologies, nor does Microsoft have the rights to our patents. So when I say we did this deal to take the patent issue off the table for customers, that’s all it does. It doesn’t entitle Novell to any patent protection vis-a-vis Microsoft, nor Microsoft any patent protection vis-a-vis Novell. Nor does it change any of the commitments we’ve made previously on patents, including our commitment to use our patents against anyone attacking our open source products, or our involvement in the Open Invention Network, which is designed to leverage patents to promote open source innovation. Thanks.

# shane Says: Your comment is awaiting moderation.
May 16th, 2007 at 9:13 am

&lt;em&gt;So we don’t have the rights to use Microsoft patents in Novell technologies…&lt;/em&gt;

Justin Steinman &lt;a href=&quot;http://boycottnovell.com/2007/05/13/lets-speculate-what-ip-did-novell-license/&quot; rel=&quot;nofollow&quot;&gt;recently indicated otherwise&lt;/a&gt;, care to explain?
&lt;blockquote cite=&quot;http://boycottnovell.com/2007/05/13/lets-speculate-what-ip-did-novell-license/&quot;&gt;
    This foundation falls into two primary categories: 1) the “covenant not to sue,” which provides customers with peace of mind when they deploy SUSE Linux Enterprise; and 2) the IP access necessary for the technical collaboration to deliver interoperability between Windows and Linux. 

&lt;/blockquote&gt;</description>
		<content:encoded><![CDATA[<p>In my experience, Novell PR is pretty fair about their moderating (more than 75% of my comments are allowed, even with links to this site refuting their statements.)</p>
<p>My newest:</p>
<p>#  Bruce Lowry Says:<br />
May 15th, 2007 at 5:24 pm</p>
<p>A quick point of correction on an issue raised in several of these comments. The Novell-Microsoft patent agreement frequently gets reported in the press as a cross-license, but it isn’t. Novell did not cross-license any patents with Microsoft. Novell and Microsoft made an agreement not to sue one another’s customers over patent issues. So we don’t have the rights to use Microsoft patents in Novell technologies, nor does Microsoft have the rights to our patents. So when I say we did this deal to take the patent issue off the table for customers, that’s all it does. It doesn’t entitle Novell to any patent protection vis-a-vis Microsoft, nor Microsoft any patent protection vis-a-vis Novell. Nor does it change any of the commitments we’ve made previously on patents, including our commitment to use our patents against anyone attacking our open source products, or our involvement in the Open Invention Network, which is designed to leverage patents to promote open source innovation. Thanks.</p>
<p># shane Says: Your comment is awaiting moderation.<br />
May 16th, 2007 at 9:13 am</p>
<p><em>So we don’t have the rights to use Microsoft patents in Novell technologies…</em></p>
<p>Justin Steinman <a href="http://boycottnovell.com/2007/05/13/lets-speculate-what-ip-did-novell-license/" rel="nofollow">recently indicated otherwise</a>, care to explain?</p>
<blockquote cite="http://boycottnovell.com/2007/05/13/lets-speculate-what-ip-did-novell-license/"><p>
    This foundation falls into two primary categories: 1) the “covenant not to sue,” which provides customers with peace of mind when they deploy SUSE Linux Enterprise; and 2) the IP access necessary for the technical collaboration to deliver interoperability between Windows and Linux. </p>
</blockquote>
]]></content:encoded>
	</item>
	<item>
		<title>By: Roy Schestowitz</title>
		<link>http://techrights.org/2007/05/16/report-bend/comment-page-1/#comment-704</link>
		<dc:creator>Roy Schestowitz</dc:creator>
		<pubDate>Wed, 16 May 2007 12:37:13 +0000</pubDate>
		<guid isPermaLink="false">http://boycottnovell.com/2007/05/16/report-bend/#comment-704</guid>
		<description>David, your message was in the moderation queue only becauseit contained a number of URLs. We neither have a deletion policy nor do we censor comments. Traffic on the site has gone up significally, so let us hope Bruce gets your message. I am aware of journalists and Novell staff who keep track of our writings.</description>
		<content:encoded><![CDATA[<p>David, your message was in the moderation queue only becauseit contained a number of URLs. We neither have a deletion policy nor do we censor comments. Traffic on the site has gone up significally, so let us hope Bruce gets your message. I am aware of journalists and Novell staff who keep track of our writings.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Mohring (NZheretic)</title>
		<link>http://techrights.org/2007/05/16/report-bend/comment-page-1/#comment-703</link>
		<dc:creator>David Mohring (NZheretic)</dc:creator>
		<pubDate>Wed, 16 May 2007 11:59:39 +0000</pubDate>
		<guid isPermaLink="false">http://boycottnovell.com/2007/05/16/report-bend/#comment-703</guid>
		<description>http://www.novell.com/prblogs/?p=336#comment-18834
( if it survives moderation )

Dear Bruce Lowry

By definition, a &quot;license&quot; is a &quot;covenant not to sue&quot;.

If the licensee abides by the stated terms then the licensor promises not to take legal action.

That the licensor Microsoft promises not to sue the licensee Novell&#039;s customers instead of Novell itself does not change the obvious fact that Microsoft stated terms represent a license for Novell. 

Let put it in the context of another case. 

Microsoft licensed patented data base technology from a company called Timeline Inc and put it in Microsoft SQL Server 7, Office 2000 other Microsoft products.

Timeline Inc license to Microsoft was a &quot;covenant not to sue&quot; Microsoft&#039;s customers for *using* code developed by Microsoft that infringed on Timeline&#039;s patents.

Note : &quot;covenant not to sue&quot; customers -- that what a license is. How is the Microsoft/Novell agreement not to sue Novell&#039;s customers any different?

However Microsoft chose a cheaper license option that granted Microsoft the right to develop infringing software but did not confer full use rights for the patented technology to downstream customers. ( The Washington Court of Appeal agreed with Timeline Inc
http://www.theregister.co.uk/2003/02/20/sql_server_developers_face_huge/ ). Timeline then threatened several of Microsoft&#039;s customers who were developing on top of Microsoft SQL Server and received very large payouts.

Since those infringing customers had already agreed to Microsoft&#039;s EULA, which included an effective agreement to recognise any patented technology that Microsoft had sub-licensed, it was a lot more difficult, if not impossible, for those Microsoft customers to challenge Timeline&#039;s patents in court. Such agreements can limit defensive options.

Microsoft is suppling &quot;coupons&quot; for Novel products. What terms do those customers have to abide by to accept the deal? What about making that license/terms public?</description>
		<content:encoded><![CDATA[<p><a href="http://www.novell.com/prblogs/?p=336#comment-18834" rel="nofollow">http://www.novell.com/prblogs/?p=336#comment-18834</a><br />
( if it survives moderation )</p>
<p>Dear Bruce Lowry</p>
<p>By definition, a &#8220;license&#8221; is a &#8220;covenant not to sue&#8221;.</p>
<p>If the licensee abides by the stated terms then the licensor promises not to take legal action.</p>
<p>That the licensor Microsoft promises not to sue the licensee Novell&#8217;s customers instead of Novell itself does not change the obvious fact that Microsoft stated terms represent a license for Novell. </p>
<p>Let put it in the context of another case. </p>
<p>Microsoft licensed patented data base technology from a company called Timeline Inc and put it in Microsoft SQL Server 7, Office 2000 other Microsoft products.</p>
<p>Timeline Inc license to Microsoft was a &#8220;covenant not to sue&#8221; Microsoft&#8217;s customers for *using* code developed by Microsoft that infringed on Timeline&#8217;s patents.</p>
<p>Note : &#8220;covenant not to sue&#8221; customers &#8212; that what a license is. How is the Microsoft/Novell agreement not to sue Novell&#8217;s customers any different?</p>
<p>However Microsoft chose a cheaper license option that granted Microsoft the right to develop infringing software but did not confer full use rights for the patented technology to downstream customers. ( The Washington Court of Appeal agreed with Timeline Inc<br />
<a href="http://www.theregister.co.uk/2003/02/20/sql_server_developers_face_huge/" rel="nofollow">http://www.theregister.co.uk/2003/02/20/sql_server_developers_face_huge/</a> ). Timeline then threatened several of Microsoft&#8217;s customers who were developing on top of Microsoft SQL Server and received very large payouts.</p>
<p>Since those infringing customers had already agreed to Microsoft&#8217;s EULA, which included an effective agreement to recognise any patented technology that Microsoft had sub-licensed, it was a lot more difficult, if not impossible, for those Microsoft customers to challenge Timeline&#8217;s patents in court. Such agreements can limit defensive options.</p>
<p>Microsoft is suppling &#8220;coupons&#8221; for Novel products. What terms do those customers have to abide by to accept the deal? What about making that license/terms public?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

