<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2.1" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: OpenXML and patents - Part 2</title>
	<link>http://doyoulovems.com/archives/61</link>
	<description></description>
	<pubDate>Thu, 11 Mar 2010 11:26:13 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2.1</generator>

	<item>
		<title>By: Do you love Microsoft? : Clarification from MS - and time to eat some humble pie?</title>
		<link>http://doyoulovems.com/archives/61#comment-61</link>
		<author>Do you love Microsoft? : Clarification from MS - and time to eat some humble pie?</author>
		<pubDate>Thu, 02 Aug 2007 09:43:10 +0000</pubDate>
		<guid>http://doyoulovems.com/archives/61#comment-61</guid>
		<description>[...] have discussed in an earlier article the issue, which many have raised, that it does not apply to future versions of the standard. My [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] have discussed in an earlier article the issue, which many have raised, that it does not apply to future versions of the standard. My [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Do you love Microsoft? : Open XML and patents - Part 3</title>
		<link>http://doyoulovems.com/archives/61#comment-51</link>
		<author>Do you love Microsoft? : Open XML and patents - Part 3</author>
		<pubDate>Tue, 31 Jul 2007 04:56:44 +0000</pubDate>
		<guid>http://doyoulovems.com/archives/61#comment-51</guid>
		<description>[...] OpenXML and patents - Part 1 and Part 2, I discussed whether MS&#8217;s Open Specification Promise (OSP) was (1) compliant with ISO/IEC [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] OpenXML and patents - Part 1 and Part 2, I discussed whether MS&#8217;s Open Specification Promise (OSP) was (1) compliant with ISO/IEC [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Scholes</title>
		<link>http://doyoulovems.com/archives/61#comment-48</link>
		<author>John Scholes</author>
		<pubDate>Mon, 30 Jul 2007 19:16:19 +0000</pubDate>
		<guid>http://doyoulovems.com/archives/61#comment-48</guid>
		<description>Having reflected on it a little more, I am inclined to think that, although it is unclear, the better view is that X in v3 would not be covered.

In other words, Sun goes a little beyond IBM and MS, in that their pledge automatically applies to later versions of the standard so long as Sun remains involved in the standards process, whereas the IBM and MS pledges only apply when they add the new version to the list.

So on this point MS is not out of line.

I also agree that it is interesting that Simon Phipps is apparently in favour of strengthening the Sun language so that everyone would (indisputably) get permission on X (but not Y) in v3. It would be excellent if Sun could be persuaded to make that change, and even better if IBM and MS could be persuaded to follow suit.</description>
		<content:encoded><![CDATA[<p>Having reflected on it a little more, I am inclined to think that, although it is unclear, the better view is that X in v3 would not be covered.</p>
<p>In other words, Sun goes a little beyond IBM and MS, in that their pledge automatically applies to later versions of the standard so long as Sun remains involved in the standards process, whereas the IBM and MS pledges only apply when they add the new version to the list.</p>
<p>So on this point MS is not out of line.</p>
<p>I also agree that it is interesting that Simon Phipps is apparently in favour of strengthening the Sun language so that everyone would (indisputably) get permission on X (but not Y) in v3. It would be excellent if Sun could be persuaded to make that change, and even better if IBM and MS could be persuaded to follow suit.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://doyoulovems.com/archives/61#comment-45</link>
		<author>Anonymous</author>
		<pubDate>Mon, 30 Jul 2007 17:25:30 +0000</pubDate>
		<guid>http://doyoulovems.com/archives/61#comment-45</guid>
		<description>Thank-you for re-reading - I think you have succinctly described the situation, which seems, at the very least, to be open to interpretation.  It would be good if Sun were to clarify.

By the way - thank-you for your blog - it has removed the fog around voting procedures and other areas very well indeed.</description>
		<content:encoded><![CDATA[<p>Thank-you for re-reading - I think you have succinctly described the situation, which seems, at the very least, to be open to interpretation.  It would be good if Sun were to clarify.</p>
<p>By the way - thank-you for your blog - it has removed the fog around voting procedures and other areas very well indeed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Scholes</title>
		<link>http://doyoulovems.com/archives/61#comment-44</link>
		<author>John Scholes</author>
		<pubDate>Mon, 30 Jul 2007 16:41:19 +0000</pubDate>
		<guid>http://doyoulovems.com/archives/61#comment-44</guid>
		<description>Thanks for coming back. You are right, I had not read the interesting Wikipedia article when I replied to your earlier comment! Sorry, that was lazy.

So the scenario is that X in v1.0 requires a Sun patent, after v2 Sun stops participating  and v3 is approved. It still contains X. Does Sun's pledge still cover X, or is it entitled to enforce all its patent rights, including those relating to X, because it stopped participating?

It is clear that if B produces software which uses the v1.0 or the v2 format, then it is still entitled to rely on the pledge. But suppose it produces software which uses the v3 format, can it rely on the pledge for X? [It obviously cannot rely on the pledge for technology Y if that is covered by a Sun patent but was not in the standard before v3 when Sun stopped participating.]

The argument that it cannot rely on the wording is that it only covers "any subsequent version ... in which Sun participates". v3 is not such a version, so it does not cover implementations of v3.

The argument that it can rely is presumably that v2 is a subset of v3 and so that subset is covered.

I am inclined to agree with you that the matter is far from clear. My experience with UK litigation is that even where you are totally confident about the legal position you can still lose 10-20% of the time. Here there seems enough ambiguity for an experienced litigant to assess the chances of losing as rather higher. So yes, I think it would be highly desirable, in the event that Sun stops participating in ODF revisions, for it to clarify the position.</description>
		<content:encoded><![CDATA[<p>Thanks for coming back. You are right, I had not read the interesting Wikipedia article when I replied to your earlier comment! Sorry, that was lazy.</p>
<p>So the scenario is that X in v1.0 requires a Sun patent, after v2 Sun stops participating  and v3 is approved. It still contains X. Does Sun&#8217;s pledge still cover X, or is it entitled to enforce all its patent rights, including those relating to X, because it stopped participating?</p>
<p>It is clear that if B produces software which uses the v1.0 or the v2 format, then it is still entitled to rely on the pledge. But suppose it produces software which uses the v3 format, can it rely on the pledge for X? [It obviously cannot rely on the pledge for technology Y if that is covered by a Sun patent but was not in the standard before v3 when Sun stopped participating.]</p>
<p>The argument that it cannot rely on the wording is that it only covers &#8220;any subsequent version &#8230; in which Sun participates&#8221;. v3 is not such a version, so it does not cover implementations of v3.</p>
<p>The argument that it can rely is presumably that v2 is a subset of v3 and so that subset is covered.</p>
<p>I am inclined to agree with you that the matter is far from clear. My experience with UK litigation is that even where you are totally confident about the legal position you can still lose 10-20% of the time. Here there seems enough ambiguity for an experienced litigant to assess the chances of losing as rather higher. So yes, I think it would be highly desirable, in the event that Sun stops participating in ODF revisions, for it to clarify the position.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://doyoulovems.com/archives/61#comment-43</link>
		<author>Anonymous</author>
		<pubDate>Mon, 30 Jul 2007 16:19:25 +0000</pubDate>
		<guid>http://doyoulovems.com/archives/61#comment-43</guid>
		<description>In the Wikipedia talk page referenced before that point is raised - I'm not sure if you read it - apologies if you did.

Sun's pledge says "...or of any subsequent version thereof ("OpenDocument Implementation") in which development Sun participates to the point of incurring an obligation,..."

"For example, if ODF 1.0 used method 'foobar' patented by Sun, the current wording means that Sun can enforce rights in relation to 'foobar' in ODF 3.7 if Sun have not participated in 3.7's development. All they simply need[ed] to say is that any technology used in a version developed with the aid of Sun can be freely used in a later version not developed with the aid of Sun, but any new technologies in later versions not developed by Sun are susceptible to litigation. "

The issue is that if Sun do not participate in the development of a subsequent version of ODF, Sun can enforce rights associated with intellectual property used in earlier versions that Sun did participate in the development of.

This isn't to disagree with your conclusion - Microsoft does seem to be in line with current industry practice.  However, current industry practice doesn't look as nice as it could or should be.

It is interesting that Simon Phipps, Chief Open Source Officer of Sun Microsystems,  says that this specific issue was raised when discussing the pledge with Sun's lawyers, and their interpretation was at variance with the reading given in the Wikipedia talk page above.

As far as I can tell, no-one else has picked up on this - not even Groklaw!</description>
		<content:encoded><![CDATA[<p>In the Wikipedia talk page referenced before that point is raised - I&#8217;m not sure if you read it - apologies if you did.</p>
<p>Sun&#8217;s pledge says &#8220;&#8230;or of any subsequent version thereof (&#8221;OpenDocument Implementation&#8221;) in which development Sun participates to the point of incurring an obligation,&#8230;&#8221;</p>
<p>&#8220;For example, if ODF 1.0 used method &#8216;foobar&#8217; patented by Sun, the current wording means that Sun can enforce rights in relation to &#8216;foobar&#8217; in ODF 3.7 if Sun have not participated in 3.7&#8217;s development. All they simply need[ed] to say is that any technology used in a version developed with the aid of Sun can be freely used in a later version not developed with the aid of Sun, but any new technologies in later versions not developed by Sun are susceptible to litigation. &#8221;</p>
<p>The issue is that if Sun do not participate in the development of a subsequent version of ODF, Sun can enforce rights associated with intellectual property used in earlier versions that Sun did participate in the development of.</p>
<p>This isn&#8217;t to disagree with your conclusion - Microsoft does seem to be in line with current industry practice.  However, current industry practice doesn&#8217;t look as nice as it could or should be.</p>
<p>It is interesting that Simon Phipps, Chief Open Source Officer of Sun Microsystems,  says that this specific issue was raised when discussing the pledge with Sun&#8217;s lawyers, and their interpretation was at variance with the reading given in the Wikipedia talk page above.</p>
<p>As far as I can tell, no-one else has picked up on this - not even Groklaw!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Scholes</title>
		<link>http://doyoulovems.com/archives/61#comment-42</link>
		<author>John Scholes</author>
		<pubDate>Mon, 30 Jul 2007 10:38:49 +0000</pubDate>
		<guid>http://doyoulovems.com/archives/61#comment-42</guid>
		<description>That interpretation of &lt;a href="http://www.oasis-open.org/committees/office/ipr.php" rel="nofollow"&gt;Sun's pledge&lt;/a&gt; is clearly wrong. Your quote above leaves out the immediately following words "or of any subsequent version thereof".

However, the Sun pledge does have a caveat about subsequent versions (that Sun has to have participated in their development). 

I think I stick by the conclusion in the article - that MS is not, on this point, significantly out of line with best practice.</description>
		<content:encoded><![CDATA[<p>That interpretation of <a href="http://www.oasis-open.org/committees/office/ipr.php" rel="nofollow">Sun&#8217;s pledge</a> is clearly wrong. Your quote above leaves out the immediately following words &#8220;or of any subsequent version thereof&#8221;.</p>
<p>However, the Sun pledge does have a caveat about subsequent versions (that Sun has to have participated in their development). </p>
<p>I think I stick by the conclusion in the article - that MS is not, on this point, significantly out of line with best practice.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://doyoulovems.com/archives/61#comment-41</link>
		<author>Anonymous</author>
		<pubDate>Mon, 30 Jul 2007 09:48:21 +0000</pubDate>
		<guid>http://doyoulovems.com/archives/61#comment-41</guid>
		<description>If you talk a look at the Wikipedia talk page here:

http://en.wikipedia.org/wiki/Talk:OpenDocument#Sun.27s_Patent_Pledge

you'll see someone arguing that Sun's Patent Pledge is not as unencumbered as it could and should be.

Essentially: "It says that Sun "will not seek to enforce any of its enforceable U.S. or foreign patents against any implementation of the Open Document Format for Office Applications (OpenDocument) v1.0 Specification". That says nothing about later specs. Perhaps I'm just being over-suspicious, but it seems to me that Sun could enforce patents that it doesn't enforce against v1.0 against a later spec - e.g v3.17 or whatever. I'd prefer your interpretation, but my natural suspicion makes me think otherwise. I'm sure the wording has been subject to very careful legal approval.".</description>
		<content:encoded><![CDATA[<p>If you talk a look at the Wikipedia talk page here:</p>
<p><a href="http://en.wikipedia.org/wiki/Talk:OpenDocument#Sun.27s_Patent_Pledge" rel="nofollow">http://en.wikipedia.org/wiki/Talk:OpenDocument#Sun.27s_Patent_Pledge</a></p>
<p>you&#8217;ll see someone arguing that Sun&#8217;s Patent Pledge is not as unencumbered as it could and should be.</p>
<p>Essentially: &#8220;It says that Sun &#8220;will not seek to enforce any of its enforceable U.S. or foreign patents against any implementation of the Open Document Format for Office Applications (OpenDocument) v1.0 Specification&#8221;. That says nothing about later specs. Perhaps I&#8217;m just being over-suspicious, but it seems to me that Sun could enforce patents that it doesn&#8217;t enforce against v1.0 against a later spec - e.g v3.17 or whatever. I&#8217;d prefer your interpretation, but my natural suspicion makes me think otherwise. I&#8217;m sure the wording has been subject to very careful legal approval.&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom Welsh</title>
		<link>http://doyoulovems.com/archives/61#comment-40</link>
		<author>Tom Welsh</author>
		<pubDate>Sun, 29 Jul 2007 16:16:59 +0000</pubDate>
		<guid>http://doyoulovems.com/archives/61#comment-40</guid>
		<description>"Accordingly, it is completely unclear at first sight, what effect these exclusions have." 

... mission accomplished.</description>
		<content:encoded><![CDATA[<p>&#8220;Accordingly, it is completely unclear at first sight, what effect these exclusions have.&#8221; </p>
<p>&#8230; mission accomplished.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
