<?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: CAFC Continues to Struggle with How Title to Subject Inventions Works under Bayh-Dole</title>
	<atom:link href="http://www.ipwatchdog.com/2009/10/27/cafc-continues-to-struggle-with-how-title-to-subject-inventions-works-under-bayh-dole/id=6911/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.ipwatchdog.com/2009/10/27/cafc-continues-to-struggle-with-how-title-to-subject-inventions-works-under-bayh-dole/id=6911/</link>
	<description>Patents, Software Patents, Patent Applications &#38; Patent Law</description>
	<lastBuildDate>Thu, 09 Feb 2012 07:58:49 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Some Heretical Thoughts on the Stanford Case &#124; IPWatchdog.com &#124; Patents &#38; Patent Law</title>
		<link>http://www.ipwatchdog.com/2009/10/27/cafc-continues-to-struggle-with-how-title-to-subject-inventions-works-under-bayh-dole/id=6911/#comment-22433</link>
		<dc:creator>Some Heretical Thoughts on the Stanford Case &#124; IPWatchdog.com &#124; Patents &#38; Patent Law</dc:creator>
		<pubDate>Thu, 14 Jul 2011 15:18:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.ipwatchdog.com/?p=6911#comment-22433</guid>
		<description>[...] “still doesn’t get it” on how title to “subject inventions” works under Bayh-Dole.  See CAFC Continues to Struggle with How Title to Subject Inventions Works under Bayh-Dole.  My original view was that the title to the “subject inventions” (i.e., those resulting from [...]</description>
		<content:encoded><![CDATA[<p>[...] “still doesn’t get it” on how title to “subject inventions” works under Bayh-Dole.  See CAFC Continues to Struggle with How Title to Subject Inventions Works under Bayh-Dole.  My original view was that the title to the “subject inventions” (i.e., those resulting from [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Research Enterprise » Pining for Fjords</title>
		<link>http://www.ipwatchdog.com/2009/10/27/cafc-continues-to-struggle-with-how-title-to-subject-inventions-works-under-bayh-dole/id=6911/#comment-9352</link>
		<dc:creator>Research Enterprise » Pining for Fjords</dc:creator>
		<pubDate>Wed, 18 Nov 2009 17:24:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.ipwatchdog.com/?p=6911#comment-9352</guid>
		<description>
[...] at IP Wachdog Eric W. Guttag has posted a detailed review of Stanford v. Roche, and provides an argument for the vesting of rights under [...]</description>
		<content:encoded><![CDATA[<p>[...] at IP Wachdog Eric W. Guttag has posted a detailed review of Stanford v. Roche, and provides an argument for the vesting of rights under [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: M. Slonecker</title>
		<link>http://www.ipwatchdog.com/2009/10/27/cafc-continues-to-struggle-with-how-title-to-subject-inventions-works-under-bayh-dole/id=6911/#comment-8875</link>
		<dc:creator>M. Slonecker</dc:creator>
		<pubDate>Wed, 28 Oct 2009 21:09:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.ipwatchdog.com/?p=6911#comment-8875</guid>
		<description>Eric,

Above you asked:

&quot;Also, how to do you respond to what was true prior to Bayh-Dole, that the policies/agreements of many federal agenices mandated that title to “subject inventions” resulting from federally sponsored research belonged to the agency/US?&quot;

Most having even a passing familiarity with the inner workings of the FAR Council quickly come to the realization that those persons who labor under its umbrella haven&#039;t a clue when it comes to patents, trademarks, copyrights, trade secrets, unfair competition, etc.  Regulatory proposals are routinely traversed by industry association groups, and their legal arguments are routinely ignored since it well understood that few companies that rely on government contracts are willing to stick their neck out and challenge misguided and plainly illegal regulations.

Perhaps someday if you are interested I will be able to regale you with the history underlying a former policy and former procurement clause that went by the name &quot;Recovery of Non-Recurring Costs&quot; (aka &quot;Recoupment&quot;).  

BTW, and Bayh-Dole notwithstanding, the DOE continues to labor under the belief that it somehow enjoys a position that allows it to act in a manner manifestly contrary to Bayh-Dole.  Last time I looked it still hewed to the line &quot;It&#039;s mine unless you ask me nicely and I deign to consent!&quot; .

In the final analysis most discussions on the topic of government contracts and IP tend to be of passing interest given that the statutes, policies and regulations are so hosed up that even a relative newcomer to the field of IP law can run rings around the government.  As a colleague used to say, and with whom I agree, dealing with the government in these matters is typically much like &quot;shooting fish in a barrel&quot;.</description>
		<content:encoded><![CDATA[<p>Eric,</p>
<p>Above you asked:</p>
<p>&#8220;Also, how to do you respond to what was true prior to Bayh-Dole, that the policies/agreements of many federal agenices mandated that title to “subject inventions” resulting from federally sponsored research belonged to the agency/US?&#8221;</p>
<p>Most having even a passing familiarity with the inner workings of the FAR Council quickly come to the realization that those persons who labor under its umbrella haven&#8217;t a clue when it comes to patents, trademarks, copyrights, trade secrets, unfair competition, etc.  Regulatory proposals are routinely traversed by industry association groups, and their legal arguments are routinely ignored since it well understood that few companies that rely on government contracts are willing to stick their neck out and challenge misguided and plainly illegal regulations.</p>
<p>Perhaps someday if you are interested I will be able to regale you with the history underlying a former policy and former procurement clause that went by the name &#8220;Recovery of Non-Recurring Costs&#8221; (aka &#8220;Recoupment&#8221;).  </p>
<p>BTW, and Bayh-Dole notwithstanding, the DOE continues to labor under the belief that it somehow enjoys a position that allows it to act in a manner manifestly contrary to Bayh-Dole.  Last time I looked it still hewed to the line &#8220;It&#8217;s mine unless you ask me nicely and I deign to consent!&#8221; .</p>
<p>In the final analysis most discussions on the topic of government contracts and IP tend to be of passing interest given that the statutes, policies and regulations are so hosed up that even a relative newcomer to the field of IP law can run rings around the government.  As a colleague used to say, and with whom I agree, dealing with the government in these matters is typically much like &#8220;shooting fish in a barrel&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: EG</title>
		<link>http://www.ipwatchdog.com/2009/10/27/cafc-continues-to-struggle-with-how-title-to-subject-inventions-works-under-bayh-dole/id=6911/#comment-8869</link>
		<dc:creator>EG</dc:creator>
		<pubDate>Wed, 28 Oct 2009 17:57:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.ipwatchdog.com/?p=6911#comment-8869</guid>
		<description>&quot;If there is a moral to the story in Roche then it is this: what faculty and student inventors sign is important. It’s too bad that neither the university nor the inventor got anything for their work here, but the inventor should have been more careful about what he signed!&quot;

Michael Martin,

Touche! (but how many faculty/students really do read the agreements they sign?)  Also, as you suggest, the university can write the assignment clause in the agreement with the faculty/student to avoid the result that happened here.  Again, thanks for the &quot;lively&quot; debate.</description>
		<content:encoded><![CDATA[<p>&#8220;If there is a moral to the story in Roche then it is this: what faculty and student inventors sign is important. It’s too bad that neither the university nor the inventor got anything for their work here, but the inventor should have been more careful about what he signed!&#8221;</p>
<p>Michael Martin,</p>
<p>Touche! (but how many faculty/students really do read the agreements they sign?)  Also, as you suggest, the university can write the assignment clause in the agreement with the faculty/student to avoid the result that happened here.  Again, thanks for the &#8220;lively&#8221; debate.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael F. Martin</title>
		<link>http://www.ipwatchdog.com/2009/10/27/cafc-continues-to-struggle-with-how-title-to-subject-inventions-works-under-bayh-dole/id=6911/#comment-8868</link>
		<dc:creator>Michael F. Martin</dc:creator>
		<pubDate>Wed, 28 Oct 2009 17:44:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.ipwatchdog.com/?p=6911#comment-8868</guid>
		<description>Eric,

I appreciate your point that there are reasonable people who agree with you.  But arguments from authority (even an authority as venerable as Howard Bremer) don&#039;t carry much weight with me.

As to the more substantive points you make, I have the following responses.  First, I understand the Bayh-Dole sought to simplify the rules of ownership for inventions that arise from federally funded research by permitting universities to take title rather than the agencies the provide the federal funding themselves.  But is that evidence that the origin of title was in the agencies rather than the inventors before Bayh-Dole?  Can you point to a case in which that was held?

Second, the language of the act that you refer to governs the obligations and duties of the contractor (e.g., a university) to the funding agency and vice versa.  Your argument, as I understand it, is that the verb &quot;retain&quot; implies that these obligations and duties run through the university to the inventors.  My argument is that this single verb is insufficient to overcome the presumption that title cannot skip over the inventors and vest directly in the contractor that has been created by hundreds of years of priority disputes decided under property and contract law.  Where is the evidence in the Bayh-Dole Act that inventors are party to these obligations and duties?

Can an inventor skirt his obligations to the university by signing a contract with a third-party that, in effect, violates university obligations under Bayh-Dole?  Apparently so.  That&#039;s what happened in &lt;i&gt;Roche&lt;/i&gt; and in cases cited therein.  Is this somehow absurd?  No.  Stanford has the right to change its agreement with inventors (as indeed it did in 1995) to make their obligations to assign inventions present rather than prospective.  Stanford also has the right to sue inventors who violate their contracts with the university, which from time to time they do.  But &lt;i&gt;Roche&lt;/i&gt; is an important decision because it clarifies for faculty and student inventors that taking federal funding does not tie their hands -- i.e., inventors still have a choice about who they work for and on what terms they will assign their inventions.  Far from being absurd, this seems to me to be the most reasonable rule that could be adopted.  What incentive would faculty and students have for disclosing inventions without this rule?  Is a sense of moral obligation enough when the university has no way of peering into the minds of its faculty and students to see whether, indeed, they have disclosed everything they believe to be an inveniton?

If there is a moral to the story in &lt;i&gt;Roche&lt;/i&gt; then it is this: what faculty and student inventors sign is important.  It&#039;s too bad that neither the university nor the inventor got anything for their work here, but the inventor should have been more careful about what he signed!</description>
		<content:encoded><![CDATA[<p>Eric,</p>
<p>I appreciate your point that there are reasonable people who agree with you.  But arguments from authority (even an authority as venerable as Howard Bremer) don&#8217;t carry much weight with me.</p>
<p>As to the more substantive points you make, I have the following responses.  First, I understand the Bayh-Dole sought to simplify the rules of ownership for inventions that arise from federally funded research by permitting universities to take title rather than the agencies the provide the federal funding themselves.  But is that evidence that the origin of title was in the agencies rather than the inventors before Bayh-Dole?  Can you point to a case in which that was held?</p>
<p>Second, the language of the act that you refer to governs the obligations and duties of the contractor (e.g., a university) to the funding agency and vice versa.  Your argument, as I understand it, is that the verb &#8220;retain&#8221; implies that these obligations and duties run through the university to the inventors.  My argument is that this single verb is insufficient to overcome the presumption that title cannot skip over the inventors and vest directly in the contractor that has been created by hundreds of years of priority disputes decided under property and contract law.  Where is the evidence in the Bayh-Dole Act that inventors are party to these obligations and duties?</p>
<p>Can an inventor skirt his obligations to the university by signing a contract with a third-party that, in effect, violates university obligations under Bayh-Dole?  Apparently so.  That&#8217;s what happened in <i>Roche</i> and in cases cited therein.  Is this somehow absurd?  No.  Stanford has the right to change its agreement with inventors (as indeed it did in 1995) to make their obligations to assign inventions present rather than prospective.  Stanford also has the right to sue inventors who violate their contracts with the university, which from time to time they do.  But <i>Roche</i> is an important decision because it clarifies for faculty and student inventors that taking federal funding does not tie their hands &#8212; i.e., inventors still have a choice about who they work for and on what terms they will assign their inventions.  Far from being absurd, this seems to me to be the most reasonable rule that could be adopted.  What incentive would faculty and students have for disclosing inventions without this rule?  Is a sense of moral obligation enough when the university has no way of peering into the minds of its faculty and students to see whether, indeed, they have disclosed everything they believe to be an inveniton?</p>
<p>If there is a moral to the story in <i>Roche</i> then it is this: what faculty and student inventors sign is important.  It&#8217;s too bad that neither the university nor the inventor got anything for their work here, but the inventor should have been more careful about what he signed!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: EG</title>
		<link>http://www.ipwatchdog.com/2009/10/27/cafc-continues-to-struggle-with-how-title-to-subject-inventions-works-under-bayh-dole/id=6911/#comment-8867</link>
		<dc:creator>EG</dc:creator>
		<pubDate>Wed, 28 Oct 2009 17:36:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.ipwatchdog.com/?p=6911#comment-8867</guid>
		<description>&quot;Thanks for posting this article on a decision I also found troubling. I have passed it on.&quot;

Paul,

Thanks for your supportive comment.  I don&#039;t know what you find &quot;troubling&quot; in this decision, but here are three that perplex me:

1.    Not considering the entire statutory scheme of how title to &quot;subject inventions&quot; works under Bayh-Dole and especially how this decision can be squared with the provisions of 35 USC 202(a), 202(d)(7) and 202(d), as well as the decision in Central Admixutre.

2.   Allowing an incidental &quot;boilerplate&quot; assignment clause in what, in essence, is primarily a confidentiality agreement to have the overrding effect it did.

3.   Giving such short shrift to the very valid argument by Stanford Uinversity about the &quot;lack of authority&quot; of the researcher to even sign Cetus&#039; VCA.

If there are other aspects of this decision that you find &quot;troubling&quot; I would be interested to hear what they are.</description>
		<content:encoded><![CDATA[<p>&#8220;Thanks for posting this article on a decision I also found troubling. I have passed it on.&#8221;</p>
<p>Paul,</p>
<p>Thanks for your supportive comment.  I don&#8217;t know what you find &#8220;troubling&#8221; in this decision, but here are three that perplex me:</p>
<p>1.    Not considering the entire statutory scheme of how title to &#8220;subject inventions&#8221; works under Bayh-Dole and especially how this decision can be squared with the provisions of 35 USC 202(a), 202(d)(7) and 202(d), as well as the decision in Central Admixutre.</p>
<p>2.   Allowing an incidental &#8220;boilerplate&#8221; assignment clause in what, in essence, is primarily a confidentiality agreement to have the overrding effect it did.</p>
<p>3.   Giving such short shrift to the very valid argument by Stanford Uinversity about the &#8220;lack of authority&#8221; of the researcher to even sign Cetus&#8217; VCA.</p>
<p>If there are other aspects of this decision that you find &#8220;troubling&#8221; I would be interested to hear what they are.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: EG</title>
		<link>http://www.ipwatchdog.com/2009/10/27/cafc-continues-to-struggle-with-how-title-to-subject-inventions-works-under-bayh-dole/id=6911/#comment-8866</link>
		<dc:creator>EG</dc:creator>
		<pubDate>Wed, 28 Oct 2009 17:01:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.ipwatchdog.com/?p=6911#comment-8866</guid>
		<description>&quot;If, as you appear to suggest, 35 USC 202 supplants the general rule of rights to inventions vesting initially in the inventor(s), then in my view there would be a most definite conflict with the provisions of Article 1, Section 8, Clause 8.&quot;

Mike,

Thanks for your comment.  I&#039;ve also seen before your argument about the potential conflict with the Patent Clause if Bayh-Dole is interpreted to put title to &quot;subject inventions&quot; initially in the contractor.  My response to that argument is that federally sponsored research comes with &quot;strings attached&quot; and one of those &quot;strings&quot; is that title to &quot;subject inventions&quot; must initially reside in the contractor.  Put differently, if you don&#039;t want the &quot;strings,&quot; don&#039;t accept the federal funding.

My other argument to the Patent Clause conflict is that it reads more into the Clause than is really there.  This is similar to the statement by SCOTUS in Graham that the Patent Clause creates some sort of constitutional &quot;standard&quot; for patentability beyond novelty.  I could also argue that an obligation of an inventor to assign by virtue of an employment agreement would create a similar conflict with the Patent Clause.  The Patent Clause simply provides Congress with the ability to allow inventors to secure the exclusive rights in their inventions, but does not address how ownership or title to such inventions might be altered by contract or by statute (such as Bayh-Dole).   Also, how to do you respond to what was true prior to Bayh-Dole, that the policies/agreements of many federal agenices mandated that title to &quot;subject inventions&quot; resulting from federally sponsored research belonged to the agency/US?

I would also be careful in relying upon what is set forth in the FARs as necessarily evidencing how title to &quot;subject inventions&quot; works under Bayh-Dole.  The FARs existed prior to Bayh-Dole and if I recall correctly, didn&#039;t discriminate as to the size or non-profit status of the contractor.  By contrast, Bayh-Dole originally applied only to those contractors who were small businesses, non-profits and individuals.  It was only by Executive Order under Reagan that the provisions of Bayh-Dole were applied to larger, for profit, entities, including those subject to the FARs.  Accordingly, what the FARs say about imposing obligations on contractors relative to their employees may reflect a &quot;historical artifiact&quot; of where the FARs came from, rather than what Bayh-Dole says about how title to &quot;subject inventions&quot; works.

Anyway, unless the Federal Circuit grants a request for rehearing in the Stanford University case (or changes it&#039;s mind later), we&#039;re all stuck with the result.  That means phrase your assignment clause to be a present transfer of future invention rights if you want to avoid what happened to Stanford University.  And thanks for the debate</description>
		<content:encoded><![CDATA[<p>&#8220;If, as you appear to suggest, 35 USC 202 supplants the general rule of rights to inventions vesting initially in the inventor(s), then in my view there would be a most definite conflict with the provisions of Article 1, Section 8, Clause 8.&#8221;</p>
<p>Mike,</p>
<p>Thanks for your comment.  I&#8217;ve also seen before your argument about the potential conflict with the Patent Clause if Bayh-Dole is interpreted to put title to &#8220;subject inventions&#8221; initially in the contractor.  My response to that argument is that federally sponsored research comes with &#8220;strings attached&#8221; and one of those &#8220;strings&#8221; is that title to &#8220;subject inventions&#8221; must initially reside in the contractor.  Put differently, if you don&#8217;t want the &#8220;strings,&#8221; don&#8217;t accept the federal funding.</p>
<p>My other argument to the Patent Clause conflict is that it reads more into the Clause than is really there.  This is similar to the statement by SCOTUS in Graham that the Patent Clause creates some sort of constitutional &#8220;standard&#8221; for patentability beyond novelty.  I could also argue that an obligation of an inventor to assign by virtue of an employment agreement would create a similar conflict with the Patent Clause.  The Patent Clause simply provides Congress with the ability to allow inventors to secure the exclusive rights in their inventions, but does not address how ownership or title to such inventions might be altered by contract or by statute (such as Bayh-Dole).   Also, how to do you respond to what was true prior to Bayh-Dole, that the policies/agreements of many federal agenices mandated that title to &#8220;subject inventions&#8221; resulting from federally sponsored research belonged to the agency/US?</p>
<p>I would also be careful in relying upon what is set forth in the FARs as necessarily evidencing how title to &#8220;subject inventions&#8221; works under Bayh-Dole.  The FARs existed prior to Bayh-Dole and if I recall correctly, didn&#8217;t discriminate as to the size or non-profit status of the contractor.  By contrast, Bayh-Dole originally applied only to those contractors who were small businesses, non-profits and individuals.  It was only by Executive Order under Reagan that the provisions of Bayh-Dole were applied to larger, for profit, entities, including those subject to the FARs.  Accordingly, what the FARs say about imposing obligations on contractors relative to their employees may reflect a &#8220;historical artifiact&#8221; of where the FARs came from, rather than what Bayh-Dole says about how title to &#8220;subject inventions&#8221; works.</p>
<p>Anyway, unless the Federal Circuit grants a request for rehearing in the Stanford University case (or changes it&#8217;s mind later), we&#8217;re all stuck with the result.  That means phrase your assignment clause to be a present transfer of future invention rights if you want to avoid what happened to Stanford University.  And thanks for the debate</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul F. Morgan</title>
		<link>http://www.ipwatchdog.com/2009/10/27/cafc-continues-to-struggle-with-how-title-to-subject-inventions-works-under-bayh-dole/id=6911/#comment-8865</link>
		<dc:creator>Paul F. Morgan</dc:creator>
		<pubDate>Wed, 28 Oct 2009 16:20:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.ipwatchdog.com/?p=6911#comment-8865</guid>
		<description>Thanks for posting this article on a decision I also found troubling.  I have passed it on.</description>
		<content:encoded><![CDATA[<p>Thanks for posting this article on a decision I also found troubling.  I have passed it on.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: M. Slonecker</title>
		<link>http://www.ipwatchdog.com/2009/10/27/cafc-continues-to-struggle-with-how-title-to-subject-inventions-works-under-bayh-dole/id=6911/#comment-8864</link>
		<dc:creator>M. Slonecker</dc:creator>
		<pubDate>Wed, 28 Oct 2009 15:49:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.ipwatchdog.com/?p=6911#comment-8864</guid>
		<description>Eric,

If, as you appear to suggest, 35 USC 202 supplants the general rule of rights to inventions vesting initially in the inventor(s), then in my view there would be a most definite conflict with the provisions of Article 1, Section 8, Clause 8 that speaks to inventors (I am placing the &quot;work for hire&quot; doctrine to the side because it is, quite frankly, a red herring.).

Just like 28 USC 1498, Title 35 provisions pertaining to inventions associated with federal assistance (be it in the form of grants, cooperative agreements, or contracts) serve as a reminder that the crafting of statutory language by persons other than practitiones steeped in the contents and structure of Title 35 is largely a fool&#039;s errand likely to raise more questions than provide answers.  Such is the unfortunate nature of our legislative process.

Rather than stop at the pertinent chapter to Title 35, which does present in my view a significant ambiguity that on its face is susceptible to an interpretation that may very well do violence to Article1, Section 8, Clause 8, I next proceed to how the federal agencies have interpreted the statute and embodied same in the Federal Acquition Regulation (the so-salled &quot;FAR&quot;).  

This interpretation is set forth in Chapter 52, and specifically at Sections 52.227-11 (contractor retains title) and 52.227-13 (USG retains title).  As you peruse these two sections you will note that one of the obligations imosed upon contractors (and subcontractors) is to have in place appropriate contractual arrangements with certain classes of its employees sufficient to permit the contractor/subcontractor to be able to meet its obligations under the aforemention clauses.

I submit that these regulatory provisions are substantive in nature, were promulgated with explicit statutory authority granted by Congress, and are thusly entitled to the full force and effect of law.  Consequently, I have a most difficult time veiwing the general language of Title 35 as supplanting the rule vesting title in the first instance with inventor(s) because to suggest otherwise raises a question of constitutional dimension, a question that only is presented if Title 35 is interpreted to read &quot;inventors&quot; more broadly such that it embraces government contractors, government subcontractors, and the government itself.

By the way, and perhaps more importantly on a practical level, the far more challenging aspect of dealing with federal agencies in matters such as these involves the treatment of technical data and computer software.  While I have always found patent law to be helpful in dealing with such agencies, and particularly when such agencies embark on second sourcing and/or international arrangements, the vast majority of legal &quot;battles&quot; are fought in this latter arena.  It is to the &quot;credit&quot; of the agency rulemakers, and to the distinct &quot;benefit&quot; of government contractors and subcontractors, that such rulemakers are woefully ignorant of the applicable statutory law.  For example, it is not at all uncommon for rulemakers to review a statute, form a belief that the statute does not go far enough, and to then extend the statutory boundaries unilaterally.  

Mike</description>
		<content:encoded><![CDATA[<p>Eric,</p>
<p>If, as you appear to suggest, 35 USC 202 supplants the general rule of rights to inventions vesting initially in the inventor(s), then in my view there would be a most definite conflict with the provisions of Article 1, Section 8, Clause 8 that speaks to inventors (I am placing the &#8220;work for hire&#8221; doctrine to the side because it is, quite frankly, a red herring.).</p>
<p>Just like 28 USC 1498, Title 35 provisions pertaining to inventions associated with federal assistance (be it in the form of grants, cooperative agreements, or contracts) serve as a reminder that the crafting of statutory language by persons other than practitiones steeped in the contents and structure of Title 35 is largely a fool&#8217;s errand likely to raise more questions than provide answers.  Such is the unfortunate nature of our legislative process.</p>
<p>Rather than stop at the pertinent chapter to Title 35, which does present in my view a significant ambiguity that on its face is susceptible to an interpretation that may very well do violence to Article1, Section 8, Clause 8, I next proceed to how the federal agencies have interpreted the statute and embodied same in the Federal Acquition Regulation (the so-salled &#8220;FAR&#8221;).  </p>
<p>This interpretation is set forth in Chapter 52, and specifically at Sections 52.227-11 (contractor retains title) and 52.227-13 (USG retains title).  As you peruse these two sections you will note that one of the obligations imosed upon contractors (and subcontractors) is to have in place appropriate contractual arrangements with certain classes of its employees sufficient to permit the contractor/subcontractor to be able to meet its obligations under the aforemention clauses.</p>
<p>I submit that these regulatory provisions are substantive in nature, were promulgated with explicit statutory authority granted by Congress, and are thusly entitled to the full force and effect of law.  Consequently, I have a most difficult time veiwing the general language of Title 35 as supplanting the rule vesting title in the first instance with inventor(s) because to suggest otherwise raises a question of constitutional dimension, a question that only is presented if Title 35 is interpreted to read &#8220;inventors&#8221; more broadly such that it embraces government contractors, government subcontractors, and the government itself.</p>
<p>By the way, and perhaps more importantly on a practical level, the far more challenging aspect of dealing with federal agencies in matters such as these involves the treatment of technical data and computer software.  While I have always found patent law to be helpful in dealing with such agencies, and particularly when such agencies embark on second sourcing and/or international arrangements, the vast majority of legal &#8220;battles&#8221; are fought in this latter arena.  It is to the &#8220;credit&#8221; of the agency rulemakers, and to the distinct &#8220;benefit&#8221; of government contractors and subcontractors, that such rulemakers are woefully ignorant of the applicable statutory law.  For example, it is not at all uncommon for rulemakers to review a statute, form a belief that the statute does not go far enough, and to then extend the statutory boundaries unilaterally.  </p>
<p>Mike</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: EG</title>
		<link>http://www.ipwatchdog.com/2009/10/27/cafc-continues-to-struggle-with-how-title-to-subject-inventions-works-under-bayh-dole/id=6911/#comment-8863</link>
		<dc:creator>EG</dc:creator>
		<pubDate>Wed, 28 Oct 2009 13:57:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.ipwatchdog.com/?p=6911#comment-8863</guid>
		<description>Michael Martin,

Thank you for your comments.  You&#039;re not the first to question my reasoning here.  I also understand the &quot;traditional path&quot; for determining title to inventions and that such title such inventions normally belongs to the inventor(s) initially until changed by contract.

But in the context of Bayh-Dole, and federally-funded research, that &quot;traditional path&quot; has been legislatively altered for &quot;subject inventions.&quot;  I&#039;m not alone in this view.  For example, Howard Bremer of WARF who was one of the principal architects in the university sector pushing for enactment of Bayh-Dole also takes the view Bayh-Dole mandates that title to &quot;subject inventions&quot; initially resides with the contractor.  So let me explain further why:

First, prior to Bayh-Dole, there was a hodge-podge of policies and regulations in the various federal agencies for who got title inventions created in whole or in part as a result of federally-funded research.  In fact, many of those policies and regulations mandated that the agency/US got title to those inventions.  Accordingly, in the context of federally-sponsored research, the &quot;traditional path&quot; was altered even before Bayh-Dole.

Second, Bayh-Dole was enacted to render uniformity to the policies and regulations around who got title to inventions resulting from federally-sponsored research.  And most significantly, the intent of Bayh-Dole was that the &quot;contractor&quot; who received the federal funding for the research was to be given the opportunity to &quot;retain&quot; title to &quot;subject inventions&quot; (i.e., those resulting from the federally-funderd) unless: (1) the contractorfailed to comply with certain obligations, such as failture to tell the federal agency about the &quot;subject inventions&quot; with a certain period of time; (2) the contractor decided not to &quot;retain&quot; title; or (3) the federal agency asserted its &quot;march in rights&quot; to take tile.  Also significantly, in situation (1), the federal agency had to specifically request that it get title; as the Federal Circuit held in Central Admixture, title to the &quot;subject inventions&quot; is &quot;voidable,&quot; not &quot;void,&quot; at the instance of the appropriate federal agency, and cannot be challenged by a prirvate &quot;third party.&quot;

Third, as Howard Bremer has correctly noted, the key operative word used consistently throughout Bayh-Dole, and particularly in the Disposition of Rights section of 35 USC § 202(a), is &quot;retain&quot; (not &quot;obtain,&quot; &quot;transfer&quot; or some other such word) with respect to title to &quot;subject inventions.&quot;  The word &quot;retain&quot; implies that  title already resides in the entity, and in the case of federally funded research under Bayh-Dole, that &quot;entity&quot; is the contractor.  In fact, as noted above, USC § 202(d) says that if the contractor elects not to retain title, the contractor may request that the appropriate federal agency allow the inventor to retain rights in the “subject invention.”  If 35 USC § 202(d) is to make sense, initial title to the “subject invention” must reside with the contractor.

Fourth, as also noted above, 35 USC §202(c)(7) expressly prohibits a nonprofit organization, such as a univery like Stanford, from assigning rights in federally sponsored research to third parties (like Cetus or Roche) without approval of the respective federal agency.  It&#039;s hard to believe that the prohibition of 35 USC § 202(c)(7) could be so easily skirted by a university researcher signing a confdentiality agreement that incidentally assign rights to “subject inventions” to third parties.

Fifth, and as you may surmise from my comments in the fourth point just above, Linn&#039;s opinion gives the incidental assignment clause in Cetus&#039; VCA (versus the assignment in Stanford&#039;s CPA) an effect that is hard to justify from the context in which the VCA was signed.  As one who once worked in the corporate world for many years, I&#039;ve seen similar assignment clauses  to those in the Cetus VCA, and they&#039;re all &quot;boilerplate&quot; much like what law governs the agreement.  More importantly, I suspect that the university researcher didn&#039;t read this incidental assignment clause and certainly didn&#039;t understand what it meant.  As one who also has worked in the corporate world, I question the authority of the university researcher to even sign something like the Cetus VCA without the permission and consent of the unversity that the researcher is employed by.  That Linn&#039;s opinion completely discounts Stanford&#039;s legitimate &quot;lack of authority&quot; argument would shock many in the corporate world.

Sixth and final, you have to view Bayh-Dole in its entirety, including the integrated statutory scheme for how title to &quot;subject inventions&quot; works.  That means, for example, considering the impact of an incidental assignment clause on prohibtions against assignment set forth in 35 USC §202(c)(7) .  Linn&#039;s opinion simply gives short shrift to this integrated statutory scheme.  And allowing that integrated statutory scheme to be undermined by a &quot;boilerplate&quot; incidental assignment clause in a confidentiality agreement just doesn&#039;t sit well with me.

I hope this further explanation is helpful to you understanding my view on this case as it relates to how title to &quot;subject inventions&quot; works under Bayh-Dole.  I realize that &quot;reasonable minds can differ,&quot; and your view is one that others have expressed to me as well.</description>
		<content:encoded><![CDATA[<p>Michael Martin,</p>
<p>Thank you for your comments.  You&#8217;re not the first to question my reasoning here.  I also understand the &#8220;traditional path&#8221; for determining title to inventions and that such title such inventions normally belongs to the inventor(s) initially until changed by contract.</p>
<p>But in the context of Bayh-Dole, and federally-funded research, that &#8220;traditional path&#8221; has been legislatively altered for &#8220;subject inventions.&#8221;  I&#8217;m not alone in this view.  For example, Howard Bremer of WARF who was one of the principal architects in the university sector pushing for enactment of Bayh-Dole also takes the view Bayh-Dole mandates that title to &#8220;subject inventions&#8221; initially resides with the contractor.  So let me explain further why:</p>
<p>First, prior to Bayh-Dole, there was a hodge-podge of policies and regulations in the various federal agencies for who got title inventions created in whole or in part as a result of federally-funded research.  In fact, many of those policies and regulations mandated that the agency/US got title to those inventions.  Accordingly, in the context of federally-sponsored research, the &#8220;traditional path&#8221; was altered even before Bayh-Dole.</p>
<p>Second, Bayh-Dole was enacted to render uniformity to the policies and regulations around who got title to inventions resulting from federally-sponsored research.  And most significantly, the intent of Bayh-Dole was that the &#8220;contractor&#8221; who received the federal funding for the research was to be given the opportunity to &#8220;retain&#8221; title to &#8220;subject inventions&#8221; (i.e., those resulting from the federally-funderd) unless: (1) the contractorfailed to comply with certain obligations, such as failture to tell the federal agency about the &#8220;subject inventions&#8221; with a certain period of time; (2) the contractor decided not to &#8220;retain&#8221; title; or (3) the federal agency asserted its &#8220;march in rights&#8221; to take tile.  Also significantly, in situation (1), the federal agency had to specifically request that it get title; as the Federal Circuit held in Central Admixture, title to the &#8220;subject inventions&#8221; is &#8220;voidable,&#8221; not &#8220;void,&#8221; at the instance of the appropriate federal agency, and cannot be challenged by a prirvate &#8220;third party.&#8221;</p>
<p>Third, as Howard Bremer has correctly noted, the key operative word used consistently throughout Bayh-Dole, and particularly in the Disposition of Rights section of 35 USC § 202(a), is &#8220;retain&#8221; (not &#8220;obtain,&#8221; &#8220;transfer&#8221; or some other such word) with respect to title to &#8220;subject inventions.&#8221;  The word &#8220;retain&#8221; implies that  title already resides in the entity, and in the case of federally funded research under Bayh-Dole, that &#8220;entity&#8221; is the contractor.  In fact, as noted above, USC § 202(d) says that if the contractor elects not to retain title, the contractor may request that the appropriate federal agency allow the inventor to retain rights in the “subject invention.”  If 35 USC § 202(d) is to make sense, initial title to the “subject invention” must reside with the contractor.</p>
<p>Fourth, as also noted above, 35 USC §202(c)(7) expressly prohibits a nonprofit organization, such as a univery like Stanford, from assigning rights in federally sponsored research to third parties (like Cetus or Roche) without approval of the respective federal agency.  It&#8217;s hard to believe that the prohibition of 35 USC § 202(c)(7) could be so easily skirted by a university researcher signing a confdentiality agreement that incidentally assign rights to “subject inventions” to third parties.</p>
<p>Fifth, and as you may surmise from my comments in the fourth point just above, Linn&#8217;s opinion gives the incidental assignment clause in Cetus&#8217; VCA (versus the assignment in Stanford&#8217;s CPA) an effect that is hard to justify from the context in which the VCA was signed.  As one who once worked in the corporate world for many years, I&#8217;ve seen similar assignment clauses  to those in the Cetus VCA, and they&#8217;re all &#8220;boilerplate&#8221; much like what law governs the agreement.  More importantly, I suspect that the university researcher didn&#8217;t read this incidental assignment clause and certainly didn&#8217;t understand what it meant.  As one who also has worked in the corporate world, I question the authority of the university researcher to even sign something like the Cetus VCA without the permission and consent of the unversity that the researcher is employed by.  That Linn&#8217;s opinion completely discounts Stanford&#8217;s legitimate &#8220;lack of authority&#8221; argument would shock many in the corporate world.</p>
<p>Sixth and final, you have to view Bayh-Dole in its entirety, including the integrated statutory scheme for how title to &#8220;subject inventions&#8221; works.  That means, for example, considering the impact of an incidental assignment clause on prohibtions against assignment set forth in 35 USC §202(c)(7) .  Linn&#8217;s opinion simply gives short shrift to this integrated statutory scheme.  And allowing that integrated statutory scheme to be undermined by a &#8220;boilerplate&#8221; incidental assignment clause in a confidentiality agreement just doesn&#8217;t sit well with me.</p>
<p>I hope this further explanation is helpful to you understanding my view on this case as it relates to how title to &#8220;subject inventions&#8221; works under Bayh-Dole.  I realize that &#8220;reasonable minds can differ,&#8221; and your view is one that others have expressed to me as well.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

