<?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/"
	xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"
	>
<channel>
	<title>Comments on: When the Law Forces You to Sue</title>
	<atom:link href="http://blogs.law.harvard.edu/infolaw/2007/08/15/when-the-law-forces-you-to-sue/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.law.harvard.edu/infolaw/2007/08/15/when-the-law-forces-you-to-sue/</link>
	<description>Information, Law, and the Law of Information</description>
	<lastBuildDate>Sat, 28 Nov 2009 11:40:16 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Rainer</title>
		<link>http://blogs.law.harvard.edu/infolaw/2007/08/15/when-the-law-forces-you-to-sue/comment-page-1/#comment-18119</link>
		<dc:creator>Rainer</dc:creator>
		<pubDate>Tue, 28 Aug 2007 14:07:37 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/infolaw/2007/08/15/when-the-law-forces-you-to-sue/#comment-18119</guid>
		<description>That looks to me like a lot of waves for a small case. And I think it&#039;s owned the big names of the competitors.
First, J&amp;J were NOT forced to sue - they just risk losing control of a valuable mark. Second, there would have been a better solution by license agreements, wouldn`t it?

So maybe there&#039;s just one at J&amp;J having had a bad day.</description>
		<content:encoded><![CDATA[<p>That looks to me like a lot of waves for a small case. And I think it&#8217;s owned the big names of the competitors.<br />
First, J&amp;J were NOT forced to sue &#8211; they just risk losing control of a valuable mark. Second, there would have been a better solution by license agreements, wouldn`t it?</p>
<p>So maybe there&#8217;s just one at J&amp;J having had a bad day.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Drew</title>
		<link>http://blogs.law.harvard.edu/infolaw/2007/08/15/when-the-law-forces-you-to-sue/comment-page-1/#comment-16679</link>
		<dc:creator>Drew</dc:creator>
		<pubDate>Fri, 17 Aug 2007 15:04:52 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/infolaw/2007/08/15/when-the-law-forces-you-to-sue/#comment-16679</guid>
		<description>A license for a nominal fee crossed my mind, but ARC might then be impliedly conceding that they were required to take the license.  Some sort of estoppel argument might conceivably come back to haunt them later on.</description>
		<content:encoded><![CDATA[<p>A license for a nominal fee crossed my mind, but ARC might then be impliedly conceding that they were required to take the license.  Some sort of estoppel argument might conceivably come back to haunt them later on.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: William McGeveran</title>
		<link>http://blogs.law.harvard.edu/infolaw/2007/08/15/when-the-law-forces-you-to-sue/comment-page-1/#comment-16582</link>
		<dc:creator>William McGeveran</dc:creator>
		<pubDate>Thu, 16 Aug 2007 15:22:55 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/infolaw/2007/08/15/when-the-law-forces-you-to-sue/#comment-16582</guid>
		<description>Luis:  That&#039;s fascinating.  Of course, uses that still point correctly to the source of the code should be all right, because in principle they actually &lt;b&gt;strengthen&lt;/b&gt; the mark.  But it could be tricky to draft such a condition to apply to exactly the kinds of downstream uses you want to favor.

Chris:  Agreed, although &quot;token&quot; licenses are sometimes rejected as &quot;naked&quot; licenses.  Note the comments from Michael Froomkin and me on the Concurring Opinions cross post...  Also, I think you are correct that some of the backstory is the ARC&#039;s refusal to &lt;b&gt;agree&lt;/b&gt; to a license -- so should J&amp;J be able to do something unilateral?</description>
		<content:encoded><![CDATA[<p>Luis:  That&#8217;s fascinating.  Of course, uses that still point correctly to the source of the code should be all right, because in principle they actually <b>strengthen</b> the mark.  But it could be tricky to draft such a condition to apply to exactly the kinds of downstream uses you want to favor.</p>
<p>Chris:  Agreed, although &#8220;token&#8221; licenses are sometimes rejected as &#8220;naked&#8221; licenses.  Note the comments from Michael Froomkin and me on the Concurring Opinions cross post&#8230;  Also, I think you are correct that some of the backstory is the ARC&#8217;s refusal to <b>agree</b> to a license &#8212; so should J&amp;J be able to do something unilateral?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris S</title>
		<link>http://blogs.law.harvard.edu/infolaw/2007/08/15/when-the-law-forces-you-to-sue/comment-page-1/#comment-16572</link>
		<dc:creator>Chris S</dc:creator>
		<pubDate>Thu, 16 Aug 2007 14:06:48 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/infolaw/2007/08/15/when-the-law-forces-you-to-sue/#comment-16572</guid>
		<description>Well as another trademark geek here, while I do see the abandonment argument, or even possibly a laches problem if they were to send C&amp;D&#039;s and then not follow up, this to me sounds like a situation that could have easily been avoided without litigation through licensing.  TMs can be licensed (along with the good will) for limited purposes, and there is nothing which requires that the cost of such licensing be prohibitive (could even well be a token fee).  To me this says that if J&amp;J really was &quot;reluctant,&quot; they have options that allow them to assert their rights that do not involve bringing suit.  Unless of course we have a situation where both sides are stonewalling and there was no way forward...</description>
		<content:encoded><![CDATA[<p>Well as another trademark geek here, while I do see the abandonment argument, or even possibly a laches problem if they were to send C&amp;D&#8217;s and then not follow up, this to me sounds like a situation that could have easily been avoided without litigation through licensing.  TMs can be licensed (along with the good will) for limited purposes, and there is nothing which requires that the cost of such licensing be prohibitive (could even well be a token fee).  To me this says that if J&amp;J really was &#8220;reluctant,&#8221; they have options that allow them to assert their rights that do not involve bringing suit.  Unless of course we have a situation where both sides are stonewalling and there was no way forward&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Luis</title>
		<link>http://blogs.law.harvard.edu/infolaw/2007/08/15/when-the-law-forces-you-to-sue/comment-page-1/#comment-16499</link>
		<dc:creator>Luis</dc:creator>
		<pubDate>Wed, 15 Aug 2007 21:38:09 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/infolaw/2007/08/15/when-the-law-forces-you-to-sue/#comment-16499</guid>
		<description>This is going to become a more common problem as a collaborative-mashup-commentary culture becomes more widespread. We&#039;re already running into it full force in free software, where we&#039;d like to be able to say &#039;use the trademark unless you&#039;re a bad guy&#039; but can&#039;t because of this same risk.</description>
		<content:encoded><![CDATA[<p>This is going to become a more common problem as a collaborative-mashup-commentary culture becomes more widespread. We&#8217;re already running into it full force in free software, where we&#8217;d like to be able to say &#8216;use the trademark unless you&#8217;re a bad guy&#8217; but can&#8217;t because of this same risk.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
