<?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: Granting Language in a Software License Agreement</title>
	<atom:link href="http://www.adamsdrafting.com/2008/08/18/granting-language/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.adamsdrafting.com/2008/08/18/granting-language/</link>
	<description></description>
	<lastBuildDate>Tue, 16 Mar 2010 21:26:31 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: AdamsDrafting &#187; Blog Archive &#187; License-Granting Language Is Just Another Contract Provision</title>
		<link>http://www.adamsdrafting.com/2008/08/18/granting-language/comment-page-1/#comment-93668</link>
		<dc:creator>AdamsDrafting &#187; Blog Archive &#187; License-Granting Language Is Just Another Contract Provision</dc:creator>
		<pubDate>Sun, 29 Nov 2009 20:32:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2008/08/18/granting-language/#comment-93668</guid>
		<description>[...] this all sounds familiar, it&#8217;s because it cropped up in this August 2008 post on license-agreement granting language. So I revisited the issue with Michael Fleming, who in the [...]</description>
		<content:encoded><![CDATA[<p>[...] this all sounds familiar, it&#8217;s because it cropped up in this August 2008 post on license-agreement granting language. So I revisited the issue with Michael Fleming, who in the [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Music Business 101 - Licensing &#124; GrindEFX</title>
		<link>http://www.adamsdrafting.com/2008/08/18/granting-language/comment-page-1/#comment-92769</link>
		<dc:creator>Music Business 101 - Licensing &#124; GrindEFX</dc:creator>
		<pubDate>Mon, 10 Aug 2009 12:02:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2008/08/18/granting-language/#comment-92769</guid>
		<description>[...] professionals. Attorney Ken Adams, who literally wrote the book on drafting contracts, once asked why certain portions of intellectual property licenses couldn’t be phrased better. It was quickly pointed out that this would probably be a bad idea because of the nature of [...]</description>
		<content:encoded><![CDATA[<p>[...] professionals. Attorney Ken Adams, who literally wrote the book on drafting contracts, once asked why certain portions of intellectual property licenses couldn’t be phrased better. It was quickly pointed out that this would probably be a bad idea because of the nature of [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Frederic Wilf</title>
		<link>http://www.adamsdrafting.com/2008/08/18/granting-language/comment-page-1/#comment-63359</link>
		<dc:creator>Frederic Wilf</dc:creator>
		<pubDate>Sun, 14 Sep 2008 21:15:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2008/08/18/granting-language/#comment-63359</guid>
		<description>As noted by others in this thread, the string of licensing terms is fairly common in software licenses.  I agree with Ken and others that careful drafting reduces ambiguity, with the additional benefit that our clients can better understand what they&#039;ve agreed to.

Jacobsen v. Katzer is an interesting case in many respects.  There&#039;s the lengthy discussion of &quot;provided that&quot; as used in the draft (which Ken has separately blogged about).  There&#039;s the Brandeis brief on which open source is a good thing.  But I&#039;m personally find interesting the discussion of covenants vs. conditions.  

The Federal Circuit finds that all of the &quot;provided that&quot; language were conditions of the copyright grant.  Uses outside of the grant were held to be infringing uses.  However, the court does not provide much guidance on how one drafts a *condition* in a license as opposed to drafting a *covenant*. 

Certainly, when drafting a license I could (and sometimes do) say,

     &quot;Any uses of the Software in violation of Sections  through  of this Agreement are violations of the license granted by Licensor to Licensee, and thus are infringing uses under the U.S. Copyright Act.&quot;

Not surprisingly, opposing counsel occasionally objects to such language.   ;-)

So, if I write or receive a software license that is one page long or 50 pages long, how do I determine whether a provision agreed to by the parties in writing is a condition of the license grant or a covenant of the contract?

What do you think?

Thanks,

Fred Wilf</description>
		<content:encoded><![CDATA[<p>As noted by others in this thread, the string of licensing terms is fairly common in software licenses.  I agree with Ken and others that careful drafting reduces ambiguity, with the additional benefit that our clients can better understand what they&#8217;ve agreed to.</p>
<p>Jacobsen v. Katzer is an interesting case in many respects.  There&#8217;s the lengthy discussion of &#8220;provided that&#8221; as used in the draft (which Ken has separately blogged about).  There&#8217;s the Brandeis brief on which open source is a good thing.  But I&#8217;m personally find interesting the discussion of covenants vs. conditions.  </p>
<p>The Federal Circuit finds that all of the &#8220;provided that&#8221; language were conditions of the copyright grant.  Uses outside of the grant were held to be infringing uses.  However, the court does not provide much guidance on how one drafts a *condition* in a license as opposed to drafting a *covenant*. </p>
<p>Certainly, when drafting a license I could (and sometimes do) say,</p>
<p>     &#8220;Any uses of the Software in violation of Sections  through  of this Agreement are violations of the license granted by Licensor to Licensee, and thus are infringing uses under the U.S. Copyright Act.&#8221;</p>
<p>Not surprisingly, opposing counsel occasionally objects to such language.   ;-)</p>
<p>So, if I write or receive a software license that is one page long or 50 pages long, how do I determine whether a provision agreed to by the parties in writing is a condition of the license grant or a covenant of the contract?</p>
<p>What do you think?</p>
<p>Thanks,</p>
<p>Fred Wilf</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard</title>
		<link>http://www.adamsdrafting.com/2008/08/18/granting-language/comment-page-1/#comment-62269</link>
		<dc:creator>Richard</dc:creator>
		<pubDate>Mon, 08 Sep 2008 21:10:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2008/08/18/granting-language/#comment-62269</guid>
		<description>On the exclusive front, I use the words &quot;exclusive license&quot; when the licensor will not have any residual rights to the licensed property (and typically couple that with an express statement to that fact, so there is no confusion), and then use the words &quot;sole licensee&quot; when the licensor will continue to practice what is licensed, but is agreeing that there will be only one licensee.</description>
		<content:encoded><![CDATA[<p>On the exclusive front, I use the words &#8220;exclusive license&#8221; when the licensor will not have any residual rights to the licensed property (and typically couple that with an express statement to that fact, so there is no confusion), and then use the words &#8220;sole licensee&#8221; when the licensor will continue to practice what is licensed, but is agreeing that there will be only one licensee.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ivan Hoffman</title>
		<link>http://www.adamsdrafting.com/2008/08/18/granting-language/comment-page-1/#comment-60130</link>
		<dc:creator>Ivan Hoffman</dc:creator>
		<pubDate>Thu, 28 Aug 2008 17:38:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2008/08/18/granting-language/#comment-60130</guid>
		<description>I often see language whereby someone &quot;grants a license.&quot;  A grant is, by definition, not a license nor is a license, by defintion, a grant.  Thus the use of the 2 words in the clause makes for lack of clarity.  I have a number of articles on my site dealing with precision in contract drafting and how it almost always affects the outcome.  Click on &quot;Articles About Being an Entrepreneur.&quot;</description>
		<content:encoded><![CDATA[<p>I often see language whereby someone &#8220;grants a license.&#8221;  A grant is, by definition, not a license nor is a license, by defintion, a grant.  Thus the use of the 2 words in the clause makes for lack of clarity.  I have a number of articles on my site dealing with precision in contract drafting and how it almost always affects the outcome.  Click on &#8220;Articles About Being an Entrepreneur.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Carol Ruth Shepherd</title>
		<link>http://www.adamsdrafting.com/2008/08/18/granting-language/comment-page-1/#comment-60075</link>
		<dc:creator>Carol Ruth Shepherd</dc:creator>
		<pubDate>Thu, 28 Aug 2008 05:49:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2008/08/18/granting-language/#comment-60075</guid>
		<description>This is a fascinating discussion.  I&#039;ve been working with software license agreements for over 30 years and I&#039;ve seen and negotiated both long and short versions of these grants with strings of license qualifiers.

Software licenses evolved when software began to be thought of as a contract subject separate from hardware (because initially, hardware and software were inseparable and were provided at the same time by the same vendor).  Lawyers did what lawyers always do when something new comes along: work from something familiar and make adaptations where the status quo doesn&#039;t fit.  In the case of software, the typical contracts at hand we looked at as templates, were patent and trade secret/know-how licenses (developed by industry), and copyright licenses (coming from publishing and the music and movie industries).  We simply spliced these contract forms together.  Why did we splice them together?  It completely reflected back on the intellectual property rights underlying (or not underlying) the subject of the contract.

Software was not expressly protected by copyright until 1980, and even after that, it was not patentable for several years.  And it was still an open question in 1985 whether patent and copyright protection could both apply to any one intellectual property, and at that time, the courts had not yet completely interpreted how copyright law would interact with contract law and whether contract law would be preempted (it is preempted, where contract law seeks to affect the same rights as are provided for and covered by copyright law.  17 USC section 301).  But this was when the IBM PC and clones were exploding all over the place and mass-market software was becoming the norm.  We were covering all the bases.

I agree with the line of thought expressed in the earlier comments that while these long strings of adjectives may or may not be appropriate to a particular situation and may or may not be duplicative -- they go on being used on a daily basis because of a. familiarity and comfort level of purchasing and procurement departments with pattern language, and b. caselaw interpreting particular contract terms, terms of art, and legal jargon. (As a young lawyer I heard several times that there is apparently a Michigan case which discusses the meaning of &quot;witnesseth&quot; at length).

For Eric Goldman: I for one do not believe that &quot;exclusive&quot; is ever ambiguous in a software license -- can you provide an example?  The parties may be making a mutual mistake in using the term &quot;exclusive license&quot; because they do not mean to exclude the licensor, but that&#039;s a separate issue from its meaning as a legal term. 

I was taught in law school as a general principle that an exclusive license always excludes the grantor.  In the context of US copyright law, the &quot;exclusive rights&quot; in software being referred to are the section 106 rights of the owner.  Surely in this context the owner&#039;s rights exclude the exercise of those rights by all others (subject to the balancing factors of the copyright act such as &quot;fair use.&quot;) The patent law uses the word &quot;exclusive&quot; in a similar manner.  

When you look at copyright cases like the Franklin Mint case (the &#039;cardinal on a branch&#039; case) and progeny, there is plenty of caselaw in the copyright context saying that an owner who transfers exclusive rights by license excludes himself from subsequently enjoying those rights. (In the Franklin Mint case, which is widely used in casebooks as a leading case, the artist excludes himself from the right to make derivative works by transferring all rights in his painting of a cardinal on a branch.  The court said he was an infringer by making other paintings of cardinals on branches similar to the one he sold the rights to -- these were derivative works and though he was the original creator, he had effectively excluded himself from making these kinds of paintings).  

This is a meaning of &quot;exclusive&quot; coming out of copyright law, rather than a contract law interpretation.  

Patent, trade secret and know how license grants are highly formulaic as well.  It is typical in these to grant an exclusive license to the licensee in one subparagraph, and have a &quot;grantback&quot; of certain rights to the licensor in the next subparagraph, and these are simultaneous so that the licensor is never excluded.  This drafting technique obviously implies the belief that the licensor would otherwise be excluded.

I haven&#039;t looked into it, but how does a court construe the meaning of &quot;exclusive&quot; in a requirements, exclusive output, or exclusive dealing contract?  I&#039;d be interested in knowing if &quot;exclusive&quot; becomes ambiguous out of the intellectual property law context.

I&#039;m not taking away from Ken&#039;s thoughtful dissection of the utility of these strings of words by merely saying &quot;always has been&quot; -- I&#039;m just pointing out that it&#039;s more than a &#039;plain English&#039; question to revise how these grants are made.

Carol Shepherd
Arborlaw PLC</description>
		<content:encoded><![CDATA[<p>This is a fascinating discussion.  I&#8217;ve been working with software license agreements for over 30 years and I&#8217;ve seen and negotiated both long and short versions of these grants with strings of license qualifiers.</p>
<p>Software licenses evolved when software began to be thought of as a contract subject separate from hardware (because initially, hardware and software were inseparable and were provided at the same time by the same vendor).  Lawyers did what lawyers always do when something new comes along: work from something familiar and make adaptations where the status quo doesn&#8217;t fit.  In the case of software, the typical contracts at hand we looked at as templates, were patent and trade secret/know-how licenses (developed by industry), and copyright licenses (coming from publishing and the music and movie industries).  We simply spliced these contract forms together.  Why did we splice them together?  It completely reflected back on the intellectual property rights underlying (or not underlying) the subject of the contract.</p>
<p>Software was not expressly protected by copyright until 1980, and even after that, it was not patentable for several years.  And it was still an open question in 1985 whether patent and copyright protection could both apply to any one intellectual property, and at that time, the courts had not yet completely interpreted how copyright law would interact with contract law and whether contract law would be preempted (it is preempted, where contract law seeks to affect the same rights as are provided for and covered by copyright law.  17 USC section 301).  But this was when the IBM PC and clones were exploding all over the place and mass-market software was becoming the norm.  We were covering all the bases.</p>
<p>I agree with the line of thought expressed in the earlier comments that while these long strings of adjectives may or may not be appropriate to a particular situation and may or may not be duplicative &#8212; they go on being used on a daily basis because of a. familiarity and comfort level of purchasing and procurement departments with pattern language, and b. caselaw interpreting particular contract terms, terms of art, and legal jargon. (As a young lawyer I heard several times that there is apparently a Michigan case which discusses the meaning of &#8220;witnesseth&#8221; at length).</p>
<p>For Eric Goldman: I for one do not believe that &#8220;exclusive&#8221; is ever ambiguous in a software license &#8212; can you provide an example?  The parties may be making a mutual mistake in using the term &#8220;exclusive license&#8221; because they do not mean to exclude the licensor, but that&#8217;s a separate issue from its meaning as a legal term. </p>
<p>I was taught in law school as a general principle that an exclusive license always excludes the grantor.  In the context of US copyright law, the &#8220;exclusive rights&#8221; in software being referred to are the section 106 rights of the owner.  Surely in this context the owner&#8217;s rights exclude the exercise of those rights by all others (subject to the balancing factors of the copyright act such as &#8220;fair use.&#8221;) The patent law uses the word &#8220;exclusive&#8221; in a similar manner.  </p>
<p>When you look at copyright cases like the Franklin Mint case (the &#8216;cardinal on a branch&#8217; case) and progeny, there is plenty of caselaw in the copyright context saying that an owner who transfers exclusive rights by license excludes himself from subsequently enjoying those rights. (In the Franklin Mint case, which is widely used in casebooks as a leading case, the artist excludes himself from the right to make derivative works by transferring all rights in his painting of a cardinal on a branch.  The court said he was an infringer by making other paintings of cardinals on branches similar to the one he sold the rights to &#8212; these were derivative works and though he was the original creator, he had effectively excluded himself from making these kinds of paintings).  </p>
<p>This is a meaning of &#8220;exclusive&#8221; coming out of copyright law, rather than a contract law interpretation.  </p>
<p>Patent, trade secret and know how license grants are highly formulaic as well.  It is typical in these to grant an exclusive license to the licensee in one subparagraph, and have a &#8220;grantback&#8221; of certain rights to the licensor in the next subparagraph, and these are simultaneous so that the licensor is never excluded.  This drafting technique obviously implies the belief that the licensor would otherwise be excluded.</p>
<p>I haven&#8217;t looked into it, but how does a court construe the meaning of &#8220;exclusive&#8221; in a requirements, exclusive output, or exclusive dealing contract?  I&#8217;d be interested in knowing if &#8220;exclusive&#8221; becomes ambiguous out of the intellectual property law context.</p>
<p>I&#8217;m not taking away from Ken&#8217;s thoughtful dissection of the utility of these strings of words by merely saying &#8220;always has been&#8221; &#8212; I&#8217;m just pointing out that it&#8217;s more than a &#8216;plain English&#8217; question to revise how these grants are made.</p>
<p>Carol Shepherd<br />
Arborlaw PLC</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kurt</title>
		<link>http://www.adamsdrafting.com/2008/08/18/granting-language/comment-page-1/#comment-59388</link>
		<dc:creator>Kurt</dc:creator>
		<pubDate>Sat, 23 Aug 2008 06:40:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2008/08/18/granting-language/#comment-59388</guid>
		<description>&quot;Why say “without restrictions to Territory” when “worldwide” suffices?&quot;

Because in a patent license license &quot;worldwide&quot; creates an implication that rights are granted, or will be sought, in countries in which no patent has been issued or granted and in which no one in their right mind would seek patent protection.  Particularly where you have a pending PCT or EPO application, you don&#039;t as the licensor want any language implying an obligation to nationalize the application in each country in the world.  &quot;without geographic restriction&quot; is the modern and more precise way to address the concept.</description>
		<content:encoded><![CDATA[<p>&#8220;Why say “without restrictions to Territory” when “worldwide” suffices?&#8221;</p>
<p>Because in a patent license license &#8220;worldwide&#8221; creates an implication that rights are granted, or will be sought, in countries in which no patent has been issued or granted and in which no one in their right mind would seek patent protection.  Particularly where you have a pending PCT or EPO application, you don&#8217;t as the licensor want any language implying an obligation to nationalize the application in each country in the world.  &#8220;without geographic restriction&#8221; is the modern and more precise way to address the concept.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike</title>
		<link>http://www.adamsdrafting.com/2008/08/18/granting-language/comment-page-1/#comment-59246</link>
		<dc:creator>Mike</dc:creator>
		<pubDate>Fri, 22 Aug 2008 00:34:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2008/08/18/granting-language/#comment-59246</guid>
		<description>To Eric&#039;s point, exclusive can be ambiguous. I in fact meant to include a footnote where the * in my previous post is.

Exclusive can mean &quot;you&#039;re the only one,&quot; or it can mean &quot;you&#039;re the last one that can ever have this license, but there are others out there that may have the license already,&quot; or it can be &quot;only you and the licensor.&quot;

In some contexts, I&#039;ve seen &quot;co-exclusive licenses&quot; that are essentially &quot;non-exclusive&quot; licenses with a prohibition on future licenses (aka standstill).

To make matters worse, if you license from a university, there&#039;s inevitably a qualification in an exclusive patent license agreement for government rights from Bayh-Dole.

I&#039;ll also point out that exclusive grants have other implications like in antitrust, taxation, standing to sue, etc. The point being, there&#039;s a lot within the definition and grants are definitely a trap for the unwary.

Finally, there are definite differences between patent, copyright, and trademark. So, you need to check the right rules for determining what applies when.</description>
		<content:encoded><![CDATA[<p>To Eric&#8217;s point, exclusive can be ambiguous. I in fact meant to include a footnote where the * in my previous post is.</p>
<p>Exclusive can mean &#8220;you&#8217;re the only one,&#8221; or it can mean &#8220;you&#8217;re the last one that can ever have this license, but there are others out there that may have the license already,&#8221; or it can be &#8220;only you and the licensor.&#8221;</p>
<p>In some contexts, I&#8217;ve seen &#8220;co-exclusive licenses&#8221; that are essentially &#8220;non-exclusive&#8221; licenses with a prohibition on future licenses (aka standstill).</p>
<p>To make matters worse, if you license from a university, there&#8217;s inevitably a qualification in an exclusive patent license agreement for government rights from Bayh-Dole.</p>
<p>I&#8217;ll also point out that exclusive grants have other implications like in antitrust, taxation, standing to sue, etc. The point being, there&#8217;s a lot within the definition and grants are definitely a trap for the unwary.</p>
<p>Finally, there are definite differences between patent, copyright, and trademark. So, you need to check the right rules for determining what applies when.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anti-trust and OS</title>
		<link>http://www.adamsdrafting.com/2008/08/18/granting-language/comment-page-1/#comment-59145</link>
		<dc:creator>Anti-trust and OS</dc:creator>
		<pubDate>Thu, 21 Aug 2008 08:37:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2008/08/18/granting-language/#comment-59145</guid>
		<description>10803 wrong again.
&quot;Perpetual means the license lasts as long as the contract.&quot;

As Roger correctly states &quot;If they say, I want to terminate the license, then I don’t accept irrevocable or perpetual language, although I have been forced to accept the words followed by the paranthetical “(except as provided in the termination provision)” to express the intent that it’s perpetual until its not.&quot;

Perpetual means, well, perpetual (yes, this definition is for Mr. Adams).  If the contract does not explicitly terminate the license on contract termination then the license will not be terminated.</description>
		<content:encoded><![CDATA[<p>10803 wrong again.<br />
&#8220;Perpetual means the license lasts as long as the contract.&#8221;</p>
<p>As Roger correctly states &#8220;If they say, I want to terminate the license, then I don’t accept irrevocable or perpetual language, although I have been forced to accept the words followed by the paranthetical “(except as provided in the termination provision)” to express the intent that it’s perpetual until its not.&#8221;</p>
<p>Perpetual means, well, perpetual (yes, this definition is for Mr. Adams).  If the contract does not explicitly terminate the license on contract termination then the license will not be terminated.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anti-trust and OS</title>
		<link>http://www.adamsdrafting.com/2008/08/18/granting-language/comment-page-1/#comment-59141</link>
		<dc:creator>Anti-trust and OS</dc:creator>
		<pubDate>Thu, 21 Aug 2008 08:14:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2008/08/18/granting-language/#comment-59141</guid>
		<description>Re MF:&quot;A license grant is not itself a contractual undertaking — It’s the widget that’s being sold in the contract. &quot;

From http://www.cafc.uscourts.gov/opinions/08-1001.pdf.
 
&quot;Thus, if the terms of the Artistic License allegedly violated are both covenants and conditions, they may serve to limit the scope of the license and are governed by copyright law. If they are merely covenants, by contrast, they are governed by contract law.&quot;

As for exclusive vs. non-exclusive, I suggest those who believe the distinction is straight forward examine &quot;exclusive&quot; licenses and their relation to anti-trust laws in Europe and the US.</description>
		<content:encoded><![CDATA[<p>Re MF:&#8221;A license grant is not itself a contractual undertaking — It’s the widget that’s being sold in the contract. &#8221;</p>
<p>From <a href="http://www.cafc.uscourts.gov/opinions/08-1001.pdf" rel="nofollow">http://www.cafc.uscourts.gov/opinions/08-1001.pdf</a>.</p>
<p>&#8220;Thus, if the terms of the Artistic License allegedly violated are both covenants and conditions, they may serve to limit the scope of the license and are governed by copyright law. If they are merely covenants, by contrast, they are governed by contract law.&#8221;</p>
<p>As for exclusive vs. non-exclusive, I suggest those who believe the distinction is straight forward examine &#8220;exclusive&#8221; licenses and their relation to anti-trust laws in Europe and the US.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
