<?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: IpVenture v. Prostar—Language of Performance or Language of Obligation?</title>
	<atom:link href="http://www.adamsdrafting.com/2007/10/01/ipventure/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.adamsdrafting.com/2007/10/01/ipventure/</link>
	<description></description>
	<lastBuildDate>Thu, 18 Mar 2010 12:12:39 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Ken Adams</title>
		<link>http://www.adamsdrafting.com/2007/10/01/ipventure/comment-page-1/#comment-9708</link>
		<dc:creator>Ken Adams</dc:creator>
		<pubDate>Sat, 06 Oct 2007 16:37:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2007/10/01/ipventure/#comment-9708</guid>
		<description>Steve: In the comment I added after Anthony&#039;s, I alluded to the distinction you refer to. I assumed that the agreements Anthony was referring to involved a simultaneous signing and closing. If not, &lt;em&gt;The Purchaser hereby purchases&lt;/em&gt; would be an unfortunate choice. Ken</description>
		<content:encoded><![CDATA[<p>Steve: In the comment I added after Anthony&#8217;s, I alluded to the distinction you refer to. I assumed that the agreements Anthony was referring to involved a simultaneous signing and closing. If not, <em>The Purchaser hereby purchases</em> would be an unfortunate choice. Ken</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve</title>
		<link>http://www.adamsdrafting.com/2007/10/01/ipventure/comment-page-1/#comment-9707</link>
		<dc:creator>Steve</dc:creator>
		<pubDate>Sat, 06 Oct 2007 16:30:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2007/10/01/ipventure/#comment-9707</guid>
		<description>Anthony&#039;s comment regarding asset purchase agreements requires some context.  If he means the type of agreement by which one company buys the assets of another, then the language of obligation  is exactly right.  That style of agreement (see, for example, the Model Asset Purchase Agreement by the ABA Business Law Section Committee on Negotiated Acquisitions) contemplates a closing of the transaction on a subsequent date at which an instrument of assignment effecting the purchase would be delivered.  Indeed the entire structure of the obligations in that agreement depend on the transfer NOT taking place at the time of signing. (For example, there is a period of &quot;due diligence&quot; and express conditions to the closing taking place that would be nonsensical if the purchaser had purchased when it signed.)

Perhaps that is not the sort of agreement Anthony had in mind.</description>
		<content:encoded><![CDATA[<p>Anthony&#8217;s comment regarding asset purchase agreements requires some context.  If he means the type of agreement by which one company buys the assets of another, then the language of obligation  is exactly right.  That style of agreement (see, for example, the Model Asset Purchase Agreement by the ABA Business Law Section Committee on Negotiated Acquisitions) contemplates a closing of the transaction on a subsequent date at which an instrument of assignment effecting the purchase would be delivered.  Indeed the entire structure of the obligations in that agreement depend on the transfer NOT taking place at the time of signing. (For example, there is a period of &#8220;due diligence&#8221; and express conditions to the closing taking place that would be nonsensical if the purchaser had purchased when it signed.)</p>
<p>Perhaps that is not the sort of agreement Anthony had in mind.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mike</title>
		<link>http://www.adamsdrafting.com/2007/10/01/ipventure/comment-page-1/#comment-9499</link>
		<dc:creator>mike</dc:creator>
		<pubDate>Tue, 02 Oct 2007 20:56:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2007/10/01/ipventure/#comment-9499</guid>
		<description>Well, just to clarify. 

I think that &quot;hereby assigns&quot; could mean both current and future inventions, depending on the remainder of the clause (both shortened for simplicity):
Employee hereby assigns all interest in:
1. the Making Widgets invention. (current invention, but this isn&#039;t usually the employment agreement context)
2. any Inventions first conceived of or reduced to practice during his or her employment. (future invention, typical in the employment context)

We know that we can presently assign future inventions. In Filmtec v. Allied-Signal, 939 F.2d 1568, 1572, the Federal Circuit stated:
&quot;If an assignment of rights in an invention is made prior to the existence of the invention, this may be viewed as an assignment of an expectant interest. An assignment of an expectant interest can be a valid assignment.&quot;

I think that you can dispose of the &quot;and agrees to assign&quot; and rely solely on &quot;hereby assigns&quot; for the purpose of a present assignment of expectant interest, at least if you can get the Federal Circuit to take your case (remember, assignments are governed by state law even though they involve patents).

If the &quot;agrees to assign&quot; is meant to do something more like require that the assignor file the appropriate document, I would instead include a clause that actually requires the assignor to execute any documents upon request. This might be important, for example, if the assignee wants to record an actual assignment document that clearly lays out the assigned invention with the PTO. This can also be a safety valve if some court decides that you can&#039;t actually presently assign a future expectant interest.</description>
		<content:encoded><![CDATA[<p>Well, just to clarify. </p>
<p>I think that &#8220;hereby assigns&#8221; could mean both current and future inventions, depending on the remainder of the clause (both shortened for simplicity):<br />
Employee hereby assigns all interest in:<br />
1. the Making Widgets invention. (current invention, but this isn&#8217;t usually the employment agreement context)<br />
2. any Inventions first conceived of or reduced to practice during his or her employment. (future invention, typical in the employment context)</p>
<p>We know that we can presently assign future inventions. In Filmtec v. Allied-Signal, 939 F.2d 1568, 1572, the Federal Circuit stated:<br />
&#8220;If an assignment of rights in an invention is made prior to the existence of the invention, this may be viewed as an assignment of an expectant interest. An assignment of an expectant interest can be a valid assignment.&#8221;</p>
<p>I think that you can dispose of the &#8220;and agrees to assign&#8221; and rely solely on &#8220;hereby assigns&#8221; for the purpose of a present assignment of expectant interest, at least if you can get the Federal Circuit to take your case (remember, assignments are governed by state law even though they involve patents).</p>
<p>If the &#8220;agrees to assign&#8221; is meant to do something more like require that the assignor file the appropriate document, I would instead include a clause that actually requires the assignor to execute any documents upon request. This might be important, for example, if the assignee wants to record an actual assignment document that clearly lays out the assigned invention with the PTO. This can also be a safety valve if some court decides that you can&#8217;t actually presently assign a future expectant interest.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ken Adams</title>
		<link>http://www.adamsdrafting.com/2007/10/01/ipventure/comment-page-1/#comment-9498</link>
		<dc:creator>Ken Adams</dc:creator>
		<pubDate>Tue, 02 Oct 2007 20:02:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2007/10/01/ipventure/#comment-9498</guid>
		<description>10803: My reaction to &lt;em&gt;assigns and agrees to assign&lt;/em&gt; was largely driven by my understanding that Mike was advocating assigning now both current and future rights. Using &lt;em&gt;assigns and agrees to assign&lt;/em&gt; to accomplish that would be misguided.

&lt;em&gt;Assigns and agrees to assign&lt;/em&gt; expresses that I&#039;m transferring rights I have now and that I&#039;m under an obligation to transfer any rights I acquire in the future. If that&#039;s the approach you adopt, I wouldn&#039;t lump the two verbs together, given that one would be used with respect to current rights and the second with respect to future rights. I&#039;d say &lt;em&gt;Acme hereby assigns X and shall assign Y&lt;/em&gt;.

I&#039;m profoundly ill-informed when it comes to patents, so I wouldn&#039;t dare offer an opinion as to which of the two approaches is preferable.

Ken</description>
		<content:encoded><![CDATA[<p>10803: My reaction to <em>assigns and agrees to assign</em> was largely driven by my understanding that Mike was advocating assigning now both current and future rights. Using <em>assigns and agrees to assign</em> to accomplish that would be misguided.</p>
<p><em>Assigns and agrees to assign</em> expresses that I&#8217;m transferring rights I have now and that I&#8217;m under an obligation to transfer any rights I acquire in the future. If that&#8217;s the approach you adopt, I wouldn&#8217;t lump the two verbs together, given that one would be used with respect to current rights and the second with respect to future rights. I&#8217;d say <em>Acme hereby assigns X and shall assign Y</em>.</p>
<p>I&#8217;m profoundly ill-informed when it comes to patents, so I wouldn&#8217;t dare offer an opinion as to which of the two approaches is preferable.</p>
<p>Ken</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 10803</title>
		<link>http://www.adamsdrafting.com/2007/10/01/ipventure/comment-page-1/#comment-9496</link>
		<dc:creator>10803</dc:creator>
		<pubDate>Tue, 02 Oct 2007 19:36:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2007/10/01/ipventure/#comment-9496</guid>
		<description>&quot;Hereby assigns and agrees to assign&quot; isn&#039;t all that bad in the context of the employment agreement.  It&#039;s a statement of a present action (I assign every invention I have right now) and an agreement to take a future action (and I&#039;ll assign to you everything I come up with later).  

Query whether it is appropriate for someone to assign now something he doesn&#039;t yet have or, alternatively, to have this seemingly perpetual, renewing action in an &#039;ancient&#039; agreement (~by some agreement I signed 10 years ago I hereby assign to you today...)

I think the conveyance of future IP probably should be done in the future.  So I might say &quot;I assign and shall assign&quot; and then backstop that with a further-assurances clause with a specific performance remedy.  That way the employee conveys what he has now and I have an enforceable obligation to cause the conveyance of those things that arise in the future.</description>
		<content:encoded><![CDATA[<p>&#8220;Hereby assigns and agrees to assign&#8221; isn&#8217;t all that bad in the context of the employment agreement.  It&#8217;s a statement of a present action (I assign every invention I have right now) and an agreement to take a future action (and I&#8217;ll assign to you everything I come up with later).  </p>
<p>Query whether it is appropriate for someone to assign now something he doesn&#8217;t yet have or, alternatively, to have this seemingly perpetual, renewing action in an &#8216;ancient&#8217; agreement (~by some agreement I signed 10 years ago I hereby assign to you today&#8230;)</p>
<p>I think the conveyance of future IP probably should be done in the future.  So I might say &#8220;I assign and shall assign&#8221; and then backstop that with a further-assurances clause with a specific performance remedy.  That way the employee conveys what he has now and I have an enforceable obligation to cause the conveyance of those things that arise in the future.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ken Adams</title>
		<link>http://www.adamsdrafting.com/2007/10/01/ipventure/comment-page-1/#comment-9489</link>
		<dc:creator>Ken Adams</dc:creator>
		<pubDate>Tue, 02 Oct 2007 13:49:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2007/10/01/ipventure/#comment-9489</guid>
		<description>Mike: Thanks. Regarding why &lt;em&gt;hereby assigns&lt;/em&gt; is better than simply &lt;em&gt;assigns&lt;/em&gt;, I point you to &lt;em&gt;MSCD&lt;/em&gt; 3.7. And as a vehicle for assigning everything now, the usage &lt;em&gt;hereby assigns and agrees to assign&lt;/em&gt; is extremely dubious. Ken</description>
		<content:encoded><![CDATA[<p>Mike: Thanks. Regarding why <em>hereby assigns</em> is better than simply <em>assigns</em>, I point you to <em>MSCD</em> 3.7. And as a vehicle for assigning everything now, the usage <em>hereby assigns and agrees to assign</em> is extremely dubious. Ken</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mike</title>
		<link>http://www.adamsdrafting.com/2007/10/01/ipventure/comment-page-1/#comment-9488</link>
		<dc:creator>mike</dc:creator>
		<pubDate>Tue, 02 Oct 2007 13:41:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2007/10/01/ipventure/#comment-9488</guid>
		<description>Ok, I opened up my &quot;Drafting Patent License Agreements&quot; Fifth Edition by Brian G. Brunsvold and Dennis P. O&#039;Reilley. Their example clause for the &quot;Assignment of Future Inventions&quot; (which follows a discussion of the cases cited in IpVenture case) begins: &quot;The Employee hereby assigns and agrees to assign to the Company...&quot;

Whether that formulation or &quot;hereby assigns&quot; or merely &quot;assigns&quot; is the &quot;best language,&quot; I&#039;m not sure. I&#039;d say the fact that since the &quot;x hereby assigns&quot; formulation has been held up a couple of times now, I&#039;m going to stick with it in my template language.

There are reasons to have other obligations (like to execute a more formal assignment or other similar documents) since the assignee may want to take more unambiguous precautions: e.g. the assignee may want to record an actual assignment with the patent and trademark office.</description>
		<content:encoded><![CDATA[<p>Ok, I opened up my &#8220;Drafting Patent License Agreements&#8221; Fifth Edition by Brian G. Brunsvold and Dennis P. O&#8217;Reilley. Their example clause for the &#8220;Assignment of Future Inventions&#8221; (which follows a discussion of the cases cited in IpVenture case) begins: &#8220;The Employee hereby assigns and agrees to assign to the Company&#8230;&#8221;</p>
<p>Whether that formulation or &#8220;hereby assigns&#8221; or merely &#8220;assigns&#8221; is the &#8220;best language,&#8221; I&#8217;m not sure. I&#8217;d say the fact that since the &#8220;x hereby assigns&#8221; formulation has been held up a couple of times now, I&#8217;m going to stick with it in my template language.</p>
<p>There are reasons to have other obligations (like to execute a more formal assignment or other similar documents) since the assignee may want to take more unambiguous precautions: e.g. the assignee may want to record an actual assignment with the patent and trademark office.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ken Adams</title>
		<link>http://www.adamsdrafting.com/2007/10/01/ipventure/comment-page-1/#comment-9487</link>
		<dc:creator>Ken Adams</dc:creator>
		<pubDate>Tue, 02 Oct 2007 13:31:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2007/10/01/ipventure/#comment-9487</guid>
		<description>Anthony: &lt;em&gt;The Purchase agrees to purchase&lt;/em&gt; is just fine if you want to risk following IpVenture into court.

If the purchase is being made concurrently with the signing of the contract, it&#039;s language of performance, so use &lt;em&gt;The Purchaser hereby purchases&lt;/em&gt;. If instead the intention is that the Purchaser effect the purchase at some future time, then use language of obligation, namely &lt;em&gt;The Purchaser shall purchase&lt;/em&gt;.

You comment has helped bring home to me that confusion over &lt;em&gt;agrees to&lt;/em&gt; seems to be widespread.

Ken</description>
		<content:encoded><![CDATA[<p>Anthony: <em>The Purchase agrees to purchase</em> is just fine if you want to risk following IpVenture into court.</p>
<p>If the purchase is being made concurrently with the signing of the contract, it&#8217;s language of performance, so use <em>The Purchaser hereby purchases</em>. If instead the intention is that the Purchaser effect the purchase at some future time, then use language of obligation, namely <em>The Purchaser shall purchase</em>.</p>
<p>You comment has helped bring home to me that confusion over <em>agrees to</em> seems to be widespread.</p>
<p>Ken</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anthony</title>
		<link>http://www.adamsdrafting.com/2007/10/01/ipventure/comment-page-1/#comment-9486</link>
		<dc:creator>Anthony</dc:creator>
		<pubDate>Tue, 02 Oct 2007 13:20:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2007/10/01/ipventure/#comment-9486</guid>
		<description>Ken, in asset purchase agreements, I frequently come across the expression &quot;The Purchaser agrees to purchase...&quot; I&#039;ve always felt this was rather weak language and so I&#039;ve begun to use &quot;The Purchaser hereby purchases...&quot;. I think I&#039;m in the minority with this preference though and I&#039;m wondering if there is a generally preferred phrase?  Thanks.</description>
		<content:encoded><![CDATA[<p>Ken, in asset purchase agreements, I frequently come across the expression &#8220;The Purchaser agrees to purchase&#8230;&#8221; I&#8217;ve always felt this was rather weak language and so I&#8217;ve begun to use &#8220;The Purchaser hereby purchases&#8230;&#8221;. I think I&#8217;m in the minority with this preference though and I&#8217;m wondering if there is a generally preferred phrase?  Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ken Adams</title>
		<link>http://www.adamsdrafting.com/2007/10/01/ipventure/comment-page-1/#comment-9485</link>
		<dc:creator>Ken Adams</dc:creator>
		<pubDate>Tue, 02 Oct 2007 13:17:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.adamsdrafting.com/2007/10/01/ipventure/#comment-9485</guid>
		<description>Mike: I suggested that &quot;must assign&quot; would have been preferable if HP had wanted to express language of obligation. (Again, the only reason for using &quot;must&quot; rather than &quot;shall&quot; is that the contract in question refers to the employee as &quot;I.&quot;) If HP had wanted to express language of performance, then they should have used &quot;hereby assign.&quot;

I leave to guys like you the question of which would have been more appropriate, language of obligation or language of performance, or what, if any, is the standard practice in the industry. But in terms of language of performance, is &quot;hereby assign&quot; enough to transfer patent rights? And is that the best language for assigning now rights that currently don&#039;t exist?

Ken</description>
		<content:encoded><![CDATA[<p>Mike: I suggested that &#8220;must assign&#8221; would have been preferable if HP had wanted to express language of obligation. (Again, the only reason for using &#8220;must&#8221; rather than &#8220;shall&#8221; is that the contract in question refers to the employee as &#8220;I.&#8221;) If HP had wanted to express language of performance, then they should have used &#8220;hereby assign.&#8221;</p>
<p>I leave to guys like you the question of which would have been more appropriate, language of obligation or language of performance, or what, if any, is the standard practice in the industry. But in terms of language of performance, is &#8220;hereby assign&#8221; enough to transfer patent rights? And is that the best language for assigning now rights that currently don&#8217;t exist?</p>
<p>Ken</p>
]]></content:encoded>
	</item>
</channel>
</rss>
