<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Patentably Defined &#187; Examples of Responses</title>
	<atom:link href="http://patentablydefined.com/category/practical-examples/feed/" rel="self" type="application/rss+xml" />
	<link>http://patentablydefined.com</link>
	<description>A practical patent prosecution blog published by Michael Kondoudis</description>
	<lastBuildDate>Thu, 02 Sep 2010 12:25:24 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Examples Of Responses To Enablement Rejections</title>
		<link>http://patentablydefined.com/2009/07/14/examples-of-responses-to-enablement-rejections/</link>
		<comments>http://patentablydefined.com/2009/07/14/examples-of-responses-to-enablement-rejections/#comments</comments>
		<pubDate>Tue, 14 Jul 2009 18:51:29 +0000</pubDate>
		<dc:creator>mike</dc:creator>
				<category><![CDATA[Examples of Responses]]></category>
		<category><![CDATA[Prosecution Strategy]]></category>
		<category><![CDATA[§112 Rejections]]></category>

		<guid isPermaLink="false">http://patentablydefined.com/?p=79</guid>
		<description><![CDATA[Based on the number of requests I have received since my first post on enablement, I know that many of you have been waiting for this follow up.  The following are a few examples employing the principles I discussed in my earlier post.  A word of caution, as is the case with most technical (non-art) [...]]]></description>
			<content:encoded><![CDATA[<p></p><p><span style="font-size: small;">Based on the number of requests I have received since my <a href="http://patentablydefined.com/?p=70" target="_blank">first post on enablement</a>, I know that many of you have been waiting for this follow up.  The following are a few examples employing the principles I discussed in my earlier post.  A word of caution, as is the case with most technical (non-art) rejections, enablement rejections are usually highly fact specific.  Consequently, there are almost an infinite number of ways to respond to any single enablement rejection.  The following are examples of two basic responses. </span></p>
<p><span style="font-size: small;"><span style="text-decoration: underline;"><strong>Examples Of Responses To Enablement Rejections</strong></span></span></p>
<p><span style="font-size: small;"><strong>Example 1 &#8211; Failure to Make Out A <em>Prima Facie</em> Case – No Analysis of Wands Factors.</strong></span></p>
<blockquote><p><span style="font-size: small;">The Office Action rejected claim 2 for allegedly failing to satisfy the enablement requirement of the first paragraph of 35 U.S.C. § 112.  This rejection is respectfully traversed.</span></p>
<p><span style="font-size: small;">Applicant respectfully submits that the Office has, by only providing a mere conclusion of nonenablement, failed to satisfy its burden to articulate a prima facie case.  And, without adequate notice of the basis of this rejection, the burden to rebut with evidence and/or argument has not yet shifted to Applicant.</span></p>
<p><span style="font-size: small;">The MPEP repeatedly warns that the Office bears <em>always</em> an initial burden of establishing a prima facie case when making an enablement rejection. (See, e.g., MPEP §§ 706.03, 2164.04).  A <em>prima facie</em> case of nonenablement is only satisfied when the Office establishes a <em>reasonable basis</em> as to why the scope of protection provided by a claim is not adequately enabled by the disclosure. (MPEP § 2164.04)(emphasis added).  This requires that the Office make specific findings of fact, supported by evidence, and then draw conclusions based on those findings of fact.  (MPEP § 2164.04).  This requires, at a minimum, discussion of those Wands factors, reasons, and evidence that lead the Examiner to conclude that the specification fails to teach how to make and use the claimed invention without undue experimentation, or that the scope of any enablement provided to one skilled in the art is not commensurate with the scope of protection sought by the claims.  (<em>Id.</em>).  Simply put, mere conclusory statements are insufficient to support an enablement rejection and must be based on evidence, not mere opinion.  (MPEP § 2164.05).</span></p>
<p><span style="font-size: small;">It is also well settled that the burden to respond only shifts to an Applicant after the Office has established a prima face case, which requires that the Office: (1) weigh all the evidence; and (2) establish a reasonable basis to question the enablement provided for the claimed invention.   (MPEP § 2164.05).</span></p>
<p><span style="font-size: small;">A review of the Office Action reveals only the mere conclusion that “there is no enabling disclosure of an incipient component”.  (Office Action, page 3).  Missing, for example, is any discussion of even a single Wands factor or any indication that any evidence has been weighed, as the MPEP expressly requires.  (MPEP § 2164.01(a)).  Indeed, the rejection is devoid of any evidence or technical reasons as to why the disclosure fails to enable the claimed invention.   Rather, the provided “reason” is a mere conclusion, which the MPEP expressly warns is insufficient to support this rejection. (MPEP §§ 706.03, 2164.05).</span></p>
<p><span style="font-size: small;">The Office’s failure to meet its burden to articulate a “reasonable basis” challenging the enablement of claim 2 alone is fatal to this rejection since Applicant is under no burden to rebut it. (MPEP §§ 706.03, 2164.05). For this reason, this rejection is traversed.</span></p>
<p><span style="font-size: small;">Accordingly, Applicant respectfully requests favorable reconsideration and withdrawal of the rejection of claim 2 under the first paragraph of 35 U.S.C. § 112.</span></p>
<p><span style="font-size: small;">In the event that the Office maintains this rejection, Applicant respectfully requests, in accordance with the principles of compact prosecution, that the Office fully develop the reasons for this rejection by articulating, on the record, those factors, reasons, and evidence that lead it to conclude that the specification fails to teach how to <em>make and use</em> the claimed invention <em>without undue experimentation</em>, or that the scope of any enablement provided to one skilled in the art is not commensurate with the scope of protection sought by the claims.  (See MPEP § 2164.04)(<em>emphasis in original</em>).</span></p></blockquote>
<p><span style="font-size: small;"><strong>Example 2 &#8211; A Substantive Response </strong></span></p>
<blockquote><p><span style="font-size: small;">Claim 1 stands rejected under the first paragraph of 35 U.S.C. § 112 as allegedly not being enabled.  Specifically, the Office Action rejected this claim because of the recitation of an outer terminal that restricts an upper movement of a movable portion of a support structure.  (Office Action, page 2).  This contention is respectfully traversed for at least the following reasons.</span></p>
<p><span style="font-size: small;">The enablement requirement of § 112 is satisfied when an application describes a claimed invention in a manner that permits one of ordinary skill to practice it, without undue experimentation. (MPEP § 2164.01).   Thus, the mere fact that experimentation <em>might</em> be required is insufficient to support an enablement rejection.  Further, even complex experimentation is not necessarily undue.  (MPEP § 2164.01).</span></p>
<p><span style="font-size: small;">Applicant respectfully submits that no experimentation is required to make and use the invention of claim 1.  Nonetheless, even if experimentation might be required, it would not be undue.  In this regard, it is important to be mindful that the question of enablement is one of predictability in view of what is known in the art.  Consequently, the amount of guidance or direction needed to satisfy the enablement requirement is inversely related to the amount of knowledge in the state of the art as well as the predictability in the art.  (MPEP § 2164.03).</span></p>
<p><span style="font-size: small;">The specific question of whether experimentation is &#8220;undue&#8221; is determined based on the following eight Wands factors:</span></p>
<p><span style="font-size: small;">1. Breadth of the claims;<br />
2. Nature of the invention;<br />
3. State of the prior art;<br />
4. Level of ordinary skill in the art;<br />
5. Predictability of the art;<br />
6. Amount of direction provided in the specification;<br />
7. Any working examples; and<br />
8. Quantity of experimentation needed relative to the disclosure.</span></p>
<p><span style="font-size: small;">(MPEP § 2164.01(a), citing In re Wands, 858 F.2d 731, 737, 8 USPQ2d 1400, 1404 (Fed. Cir. 1988)).  Further, a proper analysis of whether any experimentation is undue requires an analysis of all of the pertinent Wands factors.  (MPEP § 2164.01(a))(emphasis added).  It is improper to conclude that a disclosure is not enabling based on an analysis of only one of the above factors while ignoring one or more of the others.  (Id.).</span></p>
<p><span style="font-size: small;">Claim 1 is directed to a novel semiconductor substrate.  It is submitted that the level of ordinary skill in the relevant art, the scope of which is not addressed in the Office Action, is relatively high.  In addition, Applicant’s FIGS. 1-3 illustrate an example of the invention of claim 1.  Further, Applicant describes a method of manufacturing the substrate of claim 1, a fact evidenced by the Restriction Requirement imposed by the Office Action mailed on 02/15/2008.  As a result, at least the following Wands factors weigh in favor of enablement:</span></p>
<ul> <span style="font-size: small;"> </span></p>
<p><span style="font-size: small;"> </span></p>
<li>the state of the prior art;</li>
<li>the level of ordinary skill in the art; and</li>
<li>the presence of working examples.</li>
<p><span style="font-size: small;"> </span></ul>
<p><span style="font-size: small;">These are not the only Wands factors weighing in favor of enablement, however.</span></p>
<p><span style="font-size: small;">Attention is respectfully directed to page 12, lines 13-24 of the present application, which in conjunction with FIG. 1(B), explains:</span></p>
<blockquote><p><span style="font-size: small;">When it is not necessary to seal the movable structure 15 in a closed space, the first sealing portion 20 may be formed of a plurality of first sealing portions 20a arranged in a comb shape with gaps as shown in FIG. 2(B). In this case, each of the first sealing portions 20a has a mountain shape having slopes. Each of the first sealing portions 20a individually seals a set of the outer terminal 17, the wiring portion 17a connected to the outer terminal 17, and the electrode pad 18 connected to the wiring portion 17a. <em>As shown in FIG. 1(B), the outer terminal 17 has a height E such that the movable structure 15 is adjustable in the arrow direction A to measure specific acceleration upon mounting</em>.</span></p></blockquote>
<p><span style="font-size: small;">(<em>Emphasis added</em>).  Thus, Applicant explains that the height of the outer terminal permits vertical adjustment of the movable structure (the A direction in FIG. 1(B)).  This at least implies restricting movement.  Consequently, the following Wands factors also favor enablement:</span></p>
<ul> <span style="font-size: small;"> </span></p>
<p><span style="font-size: small;"> </span></p>
<li> such as quantity of experimentation needed relative to the disclosure; and</li>
<li> the amount of direction provided in the specification also favor enablement.</li>
<p><span style="font-size: small;"> </span></ul>
<p><span style="font-size: small;">In view of the foregoing, Applicant respectfully submits that ordinarily skilled artisans would be able to make and use the claimed invention, despite any experimentation that might be required.  Applicant further submits that this conclusion is buttressed by the amount of knowledge in the state of the art as well as the predictability of the art, as well as the majority of Wands factors that weigh in favor of enablement.  Therefore, the present application adequately enables the claimed invention.</span></p>
<p><span style="font-size: small;">Applicant thus respectfully requests favorable reconsideration and withdrawal of the rejection under 35 U.S.C. § 112.</span></p></blockquote>
<p><strong>If you like this post, why not </strong><a href="http://patentablydefined.com/feed" target="_self"><strong>grab the RSS feed</strong></a><strong> or </strong><a href="http://feedburner.google.com/fb/a/mailverify?uri=Patentablydefinedcom" target="_self"><strong>subscribe by email</strong></a><strong> and get the latest updates delivered straight to your news reader or inbox?</strong></p>
<p style="text-align: center;">© 2009, Michael E. Kondoudis</p>
<p style="text-align: center;"><strong>The Law Office of Michael E. Kondoudis<br />
</strong><a href="http://www.mekiplaw.com/" target="_blank"><strong>DC Patent Attorney</strong></a><strong><br />
www.mekiplaw.com</strong></p>
]]></content:encoded>
			<wfw:commentRss>http://patentablydefined.com/2009/07/14/examples-of-responses-to-enablement-rejections/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>How To Respond To Enablement Rejections &#8211; Part I</title>
		<link>http://patentablydefined.com/2009/03/11/how-to-respond-to-enablement-rejections-part-i/</link>
		<comments>http://patentablydefined.com/2009/03/11/how-to-respond-to-enablement-rejections-part-i/#comments</comments>
		<pubDate>Wed, 11 Mar 2009 20:08:33 +0000</pubDate>
		<dc:creator>mike</dc:creator>
				<category><![CDATA[Examples of Responses]]></category>
		<category><![CDATA[Prosecution Strategy]]></category>
		<category><![CDATA[§112 Rejections]]></category>

		<guid isPermaLink="false">http://patentablydefined.com/?p=70</guid>
		<description><![CDATA[This post is the first of a two-part series on the enablement requirement. This first installment discusses some of the fundamentals of the requirement, relevant law, and the standards for compliance. The second installment will provide examples of responses to enablement rejections. The Basis for the Enablement Requirement The enablement requirement arises from the first [...]]]></description>
			<content:encoded><![CDATA[<p></p><p><span style="font-size: small;">This post is the first of a two-part series on the enablement requirement. This first installment discusses some of the fundamentals of the requirement, relevant law, and the standards for compliance. The second installment will provide examples of responses to enablement rejections.</span></p>
<p><span style="font-size: small;"> </span></p>
<p><span style="font-size: small;"><strong><span style="text-decoration: underline;">The Basis for the Enablement Requirement</span></strong></span></p>
<p><span style="font-size: small;">The enablement requirement arises from the first paragraph of 35 U.S.C. § 112, which states in relevant part:</span></p>
<blockquote><p><span style="font-size: small;">[t]he specification shall contain a written description of the invention, and the manner and process of making and using it, in such full, clear, concise, and exact terms as to enable any person skilled in the art to which it pertains, or with which it is most nearly connected, to make and use the same . . .</span></p></blockquote>
<p><span style="font-size: small;">The purpose of the enablement requirement is to ensure that patented inventions are communicated to the public in a meaningful way.</span></p>
<p><span style="font-size: small;"> </span></p>
<p><span style="font-size: small;"><strong><span style="text-decoration: underline;">Fundamentals of the Enablement Requirement</span></strong></span></p>
<p><span style="font-size: small;">1.    The USPTO&#8217;s guidelines for examination of patent applications for compliance with the enablement requirement are found in <a href="http://www.uspto.gov/web/offices/pac/mpep/documents/2100_2164.htm" target="_blank">Section 2164 of the MPEP</a>. This should be an Applicant&#8217;s primary resource for authority when articulating responses to enablement rejections.</span></p>
<p><span style="font-size: small;">2.      All questions of enablement are evaluated against claimed subject matter. (MPEP 2164.08).</span></p>
<p><span style="font-size: small;">3.     The test for enablement is whether one of ordinary skill would need to engage in undue experimentation to practice the claimed invention. (MPEP 2164.01).</span></p>
<p><span style="font-size: small;">4.    Whether experimentation is &#8220;undue&#8221; is determined based on the following eight <em>Wands</em> factors:</span></p>
<blockquote><p><span style="font-size: small;">1. Breadth of the claims;<br />
2. Nature of the invention;<br />
3. State of the prior art;<br />
4. Level of ordinary skill in the art;<br />
5. Predictability of the art;<br />
6. Amount of direction provided in the specification;<br />
7. Any working examples; and<br />
8. Quantity of experimentation needed relative to the disclosure.</span></p></blockquote>
<p><span style="font-size: small;">(MPEP 2164.01(a), citing In re Wands, 858 F.2d 731, 737, 8 USPQ2d 1400, 1404 (Fed. Cir. 1988)).</span></p>
<p><span style="font-size: small;">5.  A proper analysis of whether any experimentation is undue requires an analysis of all of the Wands factors.  (MPEP 2164.01(a)).  It is improper to conclude that a disclosure is not enabling based on an analysis of only one of the above factors while ignoring one or more of the others.  (Id.).</span></p>
<p><span style="font-size: small;">6.  The amount of guidance or direction needed to satisfy the enablement requirement is inversely related to the amount of knowledge in the state of the art as well as the predictability in the art. (MPEP 2164.03).  Thus, the question of enablement is one of predictability in view of what is known in the art.</span></p>
<p><span style="font-size: small;"> </span></p>
<p><span style="font-size: small;"><strong><span style="text-decoration: underline;">Additional Points</span></strong></span></p>
<p><span style="font-size: small;">1.  The fact that experimentation may be complex does not necessarily make it undue, if the art typically engages in such experimentation.  (MPEP 2164.01).</span></p>
<p><span style="font-size: small;">2.   A patent need not teach, and preferably omits, what is well known in the art.  (MPEP 2164.01).  Further, an Applicant need not &#8220;enable one of ordinary skill in the art to make and use a perfected, commercially viable embodiment absent a claim limitation to that effect.&#8221; (MPEP 2164).</span></p>
<p><span style="font-size: small;">3.  Any part of the specification can support an enabling disclosure, even a background section that discusses, or even disparages, the subject matter disclosed therein. (MPEP 2164.01, citing Callicrate v. Wadsworth Mfg., Inc., 427 F.3d 1361, 77 USPQ2d 1041 (Fed. Cir. 2005)(discussion of problems with a prior art feature does not mean that one of ordinary skill in the art would not know how to make and use this feature)).</span></p>
<p><span style="font-size: small;">4.   The specification need not contain an example if the invention is otherwise disclosed in such manner that one skilled in the art will be able to practice it without undue experimentation.  (MPEP 2164.02).</span></p>
<p><span style="font-size: small;">5.  As long as the specification discloses at least one method for making and using the claimed invention that bears a reasonable correlation to the entire scope of the claim, then the enablement requirement of 35 U.S.C. 112 is satisfied.  (MPEP 2164.01(b)).</span></p>
<p><span style="font-size: small;">6.   Claims must be enabled as of their filing date.  (MPEP 2164.05(a)).</span></p>
<p><span style="font-size: small;">7.    Enablement is judged from the perspective of an ordinarily skilled artisan.  (MPEP 2164.05(b)).</span></p>
<p><span style="font-size: small;"> </span></p>
<p><span style="font-size: small;"><strong><span style="text-decoration: underline;">The Office&#8217;s Burden </span></strong></span></p>
<p><span style="font-size: small;">1. It is always incumbent on an Examiner to fully develop the reasons for a technical rejection (enablement, written description, etc.).</span></p>
<ul> <span style="font-size: x-small;"></p>
<li>Section 706.03 of the MPEP warns Examiners that &#8220;[w]here a major technical rejection is proper (e.g., lack of proper disclosure, undue breadth, utility, etc.) such rejection should be stated with a full development of the reasons rather than by a mere conclusion coupled with some stereotyped expression.&#8221; Thus, mere conclusory statements are insufficient to support a rejection under Section 112. Consequently, the Office must arguably provide a reasonable basis to reject a claim for failing to satisfy the enablement requirement, and this requires &#8220;a full development&#8221; of the reasons for the rejection.</li>
<p></span></ul>
<ul> <span style="font-size: x-small;"></p>
<li>This obligation to establish a <em>prima facie</em> case is affirmed by the MPEP in its discussions of each requirement of the first paragraph of 35 U.S.C. § 112. (See, e.g., MPEP § 2163 (III)(A) (written description); MPEP § 2164.04 (enablement)).  A <em>prima facie</em> case requires a reasonable basis to challenge the adequacy of the written description. (MPEP § 2164.04).</li>
<p></span></ul>
<ul> <span style="font-size: x-small;"></p>
<li>In accordance with the principles of compact prosecution, if an enablement rejection is appropriate, the first Office action on the merits should present the best case with all the relevant reasons, issues, and evidence so that all such rejections can be withdrawn if applicant provides appropriate convincing arguments and/or evidence in rebuttal. The principles of compact prosecution also dictate that if an enablement rejection is appropriate and the examiner recognizes limitations that would render the claims enabled, the examiner should note such limitations to applicant as early in the prosecution as possible.  (MPEP 2164.04).</li>
<p></span></ul>
<p><span style="font-size: small;">2.   An Examiner should always look for enabled, allowable subject matter and communicate to applicant what that subject matter is at the earliest point possible in the prosecution of the application.  (MPEP 2164.04).  Thus, if a rejection is made based on the view that the enablement is not commensurate in scope with the claim, the examiner should identify the subject matter that is considered to be enabled.  (MPEP 2164.08).</span></p>
<p><span style="font-size: small;">3.  The Examiner&#8217;s analysis must consider all the evidence related to each of these factors, and any conclusion of nonenablement must be based on the evidence as a whole.  (MPEP 2164.01(a)).</span></p>
<p><span style="font-size: small;">4.    Only after the Examiner has weighed all the evidence and established a reasonable basis to question the enablement provided for the claimed invention, does the burden fall on applicant to present persuasive arguments, supported by suitable proofs where necessary, that one skilled in the art would be able to make and use the claimed invention using the application as a guide.  (MPEP 2164.05).  The evidence provided by applicant need not be conclusive but merely convincing to one skilled in the art. (Id.).</span></p>
<p><span style="font-size: small;">5. The MPEP instructs Examiners that they must assume compliance with the enablement requirement when an application includes a teaching of how to make and use invention &#8220;in terms which correspond in scope to the claims.&#8221;  This mandate may be only ignored when there is a basis to doubt the objective truth of the teaching.   (MPEP 2164.04).</span></p>
<p><span style="font-size: small;">So, unless a rejection articulates &#8220;evidence or some technical reasoning&#8221; that either (i) an enabling teaching does not correspond to the claims or (ii) a reason to doubt the objective truth of such a teaching, the mere presence of a teaching requires that the Office assume that this requirement is satisfied.</span></p>
<p><span style="font-size: small;"><span style="color: orange;"><strong>Coming Soon in Part II &#8211; Examples of Responses to Enablement Rejections</strong></span><br />
</span></p>
<p><strong>If you like this post, why not </strong><a href="http://patentablydefined.com/feed" target="_self"><strong>grab the RSS feed</strong></a><strong> or </strong><a href="http://feedburner.google.com/fb/a/mailverify?uri=Patentablydefinedcom" target="_self"><strong>subscribe by email</strong></a><strong> and get the latest updates delivered straight to your news reader or inbox?</strong></p>
<p style="text-align: center;">© 2009, Michael E. Kondoudis</p>
<p style="text-align: center;"><strong>The Law Office of Michael E. Kondoudis<br />
</strong><a href="http://www.mekiplaw.com/" target="_blank"><strong>DC Patent Attorney</strong></a><strong><br />
www.mekiplaw.com</strong></p>
]]></content:encoded>
			<wfw:commentRss>http://patentablydefined.com/2009/03/11/how-to-respond-to-enablement-rejections-part-i/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Requesting Withdrawal Of The Finality Of An Office Action</title>
		<link>http://patentablydefined.com/2009/01/25/requesting-withdrawal-of-the-finality-of-an-office-action/</link>
		<comments>http://patentablydefined.com/2009/01/25/requesting-withdrawal-of-the-finality-of-an-office-action/#comments</comments>
		<pubDate>Sun, 25 Jan 2009 23:48:25 +0000</pubDate>
		<dc:creator>mike</dc:creator>
				<category><![CDATA[After Final Practice]]></category>
		<category><![CDATA[Examples of Responses]]></category>
		<category><![CDATA[Practice Suggestions]]></category>
		<category><![CDATA[Prosecution Strategy]]></category>
		<category><![CDATA[The MPEP]]></category>
		<category><![CDATA[Useful Information]]></category>

		<guid isPermaLink="false">http://patentablydefined.com/?p=69</guid>
		<description><![CDATA[This post discusses requests to withdraw finality.  Under the USPTO’s policy of compact prosecution discussed here, a second office action may properly be made final under most circumstances.  The circumstances are set forth in §706.07(a) of the Manual of Patent Examining Procedure (MPEP), entitled Final Rejection, When Proper on Second Action, which states: Under present [...]]]></description>
			<content:encoded><![CDATA[<p></p><p>This post discusses requests to withdraw finality.  Under the USPTO’s policy of compact prosecution discussed <a href="http://patentablydefined.com/?p=18" target="_blank">here</a>, a second office action may properly be made final under most circumstances.  The circumstances are set forth in <a href="http://www.uspto.gov/web/offices/pac/mpep/documents/0700_706_07_a.htm" target="_blank">§706.07(a)</a> of the Manual of Patent Examining Procedure (MPEP), entitled Final Rejection, When Proper on Second Action, which states:</p>
<blockquote><p>Under present practice, second or any subsequent actions on the merits shall be final, except where the examiner introduces a new ground of rejection that is neither necessitated by applicant&#8217;s amendment of the claims, nor based on information submitted in an information disclosure statement filed during the period set forth in 37 CFR 1.97(c) with the fee set forth in 37 CFR 1.17(p).</p></blockquote>
<p>The MPEP, in <a href="http://www.uspto.gov/web/offices/pac/mpep/documents/0700_706_07_d.htm" target="_blank">§706.07(d)</a>, also provides a remedy when a final Office Action is issued and the conditions of §706.07(a) have not been satisfied.  That section, entitled Final Rejection, Withdrawal of, Premature, provides:</p>
<blockquote><p>If, on request by applicant for reconsideration, the primary examiner finds the final rejection to have been premature, he or she should withdraw the finality of the rejection. The finality of the Office action must be withdrawn while the application is still pending. The examiner cannot withdraw the final rejection once the application is abandoned.</p></blockquote>
<p>The following are a few examples of successful Requests to Withdraw Finality.</p>
<p><strong><span style="text-decoration: underline;">&#8212;- EXAMPLES &#8212;-</span></strong></p>
<p>This first example was submitted in response to a final Office action that mischaracterized a claim.</p>
<blockquote><p><span style="text-decoration: underline;"><strong>REQUEST FOR WITHDRAWAL OF FINALITY<br />
</strong></span></p>
<p>Applicants are in receipt of a final Office Action mailed March 13, 2007, in this application. Applicants respectfully request that the finality of the subject Office Action should be withdrawn because the Office has expressly and erroneously misinterpreted claims and, as a result, has failed to consider the patentability arguments presented in the most recently filed Amendment. Further, the Office&#8217;s express, incorrect claim characterization precludes the Office Action from addressing the merits of the argument presented concerning one of the presented independent claims.</p>
<p>In support of this request, Applicants state the following:</p>
<p>1. On December 20, 2006, Applicants filed an Amendment that presented independent claim 15 with the following claim recitation:</p>
<blockquote><p>a disk protector disposed at an outer edge of the disk damper&#8230;.</p></blockquote>
<p>2. In response to the Amendment filed December 20, 2006, the Office mailed a final Office Action on March 13, 2007, which explained that all rejections were maintained because:</p>
<blockquote><p>Applicant argues the limitations which are not in the claim language&#8221; because Applicants only claim &#8220;&#8230;arranged/disposed along an outer edge of the disk damper&#8230;Applicant does not claim &#8220;&#8230; at an outer edge of the disk damper.&#8221;</p></blockquote>
<p>(Office Action, page 3).</p>
<p>3. The aforementioned statement of paragraph 2 is manifestly incorrect and without basis in fact. Indeed, Applicants&#8217; independent claim 15 expressly recites &#8220;at.&#8221;</p>
<p>4. Section 707.07(f) of the Manual of Patent Examining Procedure (MPEP) instructs that:</p>
<blockquote><p>Where the applicant traverses any rejection, the examiner should, if he or she repeats the rejection, take note of the applicant&#8217;s argument and answer the substance of it.</p></blockquote>
<p>5. The Office repeated the rejections of all of the claims. The Office, however, neither &#8220;took note&#8221; of Applicants&#8217; argument nor &#8220;answered the substance&#8221; of Applicants&#8217; argument. Thus, the final Office Action is deficient because the Office failed to satisfy the requirements of MPEP § 707.07(f).</p>
<p>6. Also, it is submitted that the outstanding Office Action has taken an improper and unreasonable interpretation of claim terms. And, for this additional reason, Applicants respectfully submit that the outstanding Office Action is improper.</p>
<p>In view of the foregoing, Applicants respectfully request withdrawal of the finality of the outstanding Office Action and further request a new non-final Office Action that addresses the merits of claim 15.</p></blockquote>
<p>This second example was submitted in response to a final Office action that first rejected features that were previously presented for examination.</p>
<blockquote><p><strong>REQUEST FOR WITHDRAWAL OF FINALITY </strong></p>
<p>Applicant is in receipt of a final Office Action mailed December 25, 2007, in this application.  Applicant respectfully submits that the finality of the subject Office Action is premature and therefore requests withdrawal of that finality, pursuant to Section 706.07(d) of the Manual of Patent Examining Procedure (MPEP).</p>
<p><strong>Grounds</strong><br />
As grounds for this Request, Applicant states as follows:</p>
<p>1.  The final Office Action rejects independent claim 1 on new grounds.  As the Office itself states, “Applicant&#8217;s amendment necessitated the new ground(s) of rejection presented in this Office action.”  (Final Office Action, page 6).</p>
<p>2.  The sole amendment to independent claim 1 was made in an Amendment filed October 25, 2008.  In that Amendment, Applicant cancelled original claim 2 and amended independent claim 1 to recite the features of cancelled claim 2.</p>
<p>3.  The features of claim 2 that were added to independent claim 1 were previously presented for examination.  Thus, the added features could have been rejected in an earlier Office action but were not.</p>
<p>4.  Section 706.07(a) of the MPEP specifies the conditions under which the finality of a second or subsequent Office action is proper, providing that:<br />
Under present practice, second or any subsequent actions on the merits shall be final, except where the examiner introduces a new ground of rejection that is neither necessitated by applicant&#8217;s amendment of the claims nor based on information submitted in an information disclosure statement….</p>
<p>5.  Applicant submits that because the features added to independent claim 1 were presented for examination in the preceding Office Action, the new ground of rejection of claim 1 made in the final Office Action cannot reasonably be said to be either necessitated by a claim amendment or an Information Disclosure Statement.</p>
<p><strong>Conclusion</strong><br />
The conditions set forth in § 706.07(a) of the MPEP have not been satisfied.  Accordingly, for that reason alone, as well as the interests of fairness, the finality of the final Office Action should be withdrawn.</p></blockquote>
<p>This final example was submitted in response to a final Office action that rejected a claim for the first time.</p>
<blockquote><p><strong>REQUEST FOR WITHDRAWAL OF FINALITY </strong>&lt;</p>
<p>Applicant is in receipt of a final Office Action mailed December 25, 2007, in this application.  Applicant respectfully submits that the finality of the subject Office Action is premature and therefore requests withdrawal of that finality, pursuant to Section 706.07(d) of the Manual of Patent Examining Procedure (MPEP).</p>
<p><strong>Grounds For Request</strong><br />
As grounds for this Request, Applicant states as follows:</p>
<p>1.  The final Office Action rejected independent claim 20.</p>
<p>2.  The non-final Office Action that immediately preceded the final Office Action did not reject independent claim 20.</p>
<p>3.  Section 706.07(a) of the MPEP specifies the conditions under which the finality of a second or subsequent Office action is proper, providing that:</p>
<blockquote><p>Under present practice, second or any subsequent actions on the merits shall be final, except where the examiner introduces a new ground of rejection that is neither necessitated by applicant&#8217;s amendment of the claims nor based on information submitted in an information disclosure statement….</p></blockquote>
<p>4.  Applicant submits that the rejection of independent claim 20 is a new ground of rejection.  Also, because Applicant neither amended claim 20 nor filed an IDS between the subject non-final and final Office actions, the conditions required by MPEP § 706.07(a) cannot yet be satisfied.</p>
<p><strong>Conclusion</strong><br />
The conditions set forth in § 706.07(a) of the MPEP have not been satisfied.  Accordingly, for that reason alone, as well as the Office’s policy of compact prosecution, the finality of the final Office Action should be withdrawn.</p></blockquote>
<p>Two last comments.  First, I prefer to file these Requests as separate, stand alone documents.  Second, each of the examples in this post is based on <span style="text-decoration: underline;">successful</span> Request.  They are by no means appropriate for every final Office action.  But, when finality is premature, this type of Request can be an effective remedy.</p>
<p><strong>If you like this post, why not </strong><a href="http://patentablydefined.com/feed" target="_self"><strong>grab the RSS feed</strong></a><strong> or </strong><a href="http://feedburner.google.com/fb/a/mailverify?uri=Patentablydefinedcom" target="_self"><strong>subscribe by email</strong></a><strong> and get the latest updates delivered straight to your news reader or inbox?</strong></p>
<p style="text-align: center;">© 2009, Michael E. Kondoudis</p>
<p style="text-align: center;"><strong>The Law Office of Michael E. Kondoudis<br />
</strong><a href="http://www.mekiplaw.com/" target="_blank"><strong>DC Patent Attorney</strong></a><strong><br />
www.mekiplaw.com</strong></p>
]]></content:encoded>
			<wfw:commentRss>http://patentablydefined.com/2009/01/25/requesting-withdrawal-of-the-finality-of-an-office-action/feed/</wfw:commentRss>
		<slash:comments>16</slash:comments>
		</item>
		<item>
		<title>Examples Of How To Respond To Takings Of Official Notice &#8211; Part II</title>
		<link>http://patentablydefined.com/2008/12/23/examples-of-how-to-respond-to-takings-of-official-notice-part-ii/</link>
		<comments>http://patentablydefined.com/2008/12/23/examples-of-how-to-respond-to-takings-of-official-notice-part-ii/#comments</comments>
		<pubDate>Tue, 23 Dec 2008 17:30:09 +0000</pubDate>
		<dc:creator>mike</dc:creator>
				<category><![CDATA[Examples of Responses]]></category>
		<category><![CDATA[Practice Suggestions]]></category>
		<category><![CDATA[Prosecution Strategy]]></category>
		<category><![CDATA[The MPEP]]></category>

		<guid isPermaLink="false">http://patentablydefined.com/?p=66</guid>
		<description><![CDATA[This is the second in a two-part series on Official Notice and strategies for responding to rejections based on Official Notice.  In part one of this series, I discussed basic principles of Official Notice.  What follow are a few examples of responses to rejections based on the principles discussed in my earlier post. Example 1 [...]]]></description>
			<content:encoded><![CDATA[<p></p><p>This is the second in a two-part series on Official Notice and strategies for responding to rejections based on Official Notice.  In <a href="http://patentablydefined.com/?p=65" target="_blank">part one of this series</a>, I discussed basic principles of Official Notice.  What follow are a few examples of responses to rejections based on the principles discussed in my earlier post.</p>
<p><span style="text-decoration: underline;"><strong>Example 1 &#8211; An Improper Taking of Official Notice</strong></span></p>
<blockquote><p>Applicant respectfully traverses the rejection of independent claim 1 at least because the Office has failed to establish a <em>prima facie</em> case of obviousness.</p>
<p>In rejecting independent claim 1 under 35 U.S.C § 103, the Office Action contends:</p>
<blockquote><p>It would have been obvious to one having ordinary skill in the art at the time the invention was made to replace the printer of Smith with the plotter of <em>Jones</em> since the Examiner takes Official Notice of the equivalent use in the art and the selection of any of these known equivalents to write information on a plastic card would be within the level of ordinary skill in the art.</p></blockquote>
<p>Applicant respectfully traverses this attempted use of Official Notice as improper.  Consequently, a necessary element of a <em>prima facie</em> case is absent.</p>
<p>Firstly, it is to be appreciated that the Office Action attempts to officially notice legal conclusions, &#8211;namely “the equivalent use in the art and the selection of any of these known equivalents to write information on a plastic card would be within the level of ordinary skill in the art.”  Official Notice, however, is only proper for facts.  (<a href="http://www.uspto.gov/web/offices/pac/mpep/documents/2100_2144_03.htm" target="_blank"><em>MPEP § 2144.03</em></a>).  Indeed, Official Notice is only permissible for those few facts that are of a “notorious character” and that are “capable of instant and unquestionable demonstration”.  (<em>MPEP § 2144.03(A)</em>).  It is improper to use Official Notice for conclusions of law.</p>
<p>Secondly, the Office Action relies on Official Notice as the &#8220;principal evidence&#8221; upon which the rejection of claim 1 is based.  Official Notice cannot be used in this manner.  As Section 2144.03(A) of the <em>MPEP</em> expressly warns, it is never appropriate to rely solely on Official Notice as the principal evidence upon which a rejection was based.  Instead, Official Notice is only appropriate for facts and that serve to “fill in the gaps” in a rejection.  (<em>MPEP § 2144.03(A)</em>).  This is why official notice is to be judicially applied.  (<em>MPEP §  2144.03</em>).  It is unreasonable to conclude that the Office has used Official Notice to “fill in” a gap in this rejection.</p>
<p>Thirdly, the Office attempts to take Official Notice of matter that is not “capable of instant and unquestionable demonstration”, as expressly required by section 2144.03(A) of the <em>MPEP</em>.  Indeed, even assuming <em>arguendo</em> that the equivalence of the subject printer and plotter is a fact, this fact would be neither of notorious character nor instantly and unquestionably demonstrable.  Moreover, courts have long rejected the notion that official notice can be taken on the state of the art.  (<em>See <a href="http://www.uspto.gov/web/offices/pac/dapp/opla/documents/offnotice.pdf" target="_blank">Memorandum to Patent Examining Corps from the Deputy Commissioner for Patent Examining Policy regarding Procedures for Relying on Facts Which are Not of Record as Common Sense or for Taking Official Notice</a></em>, n.6, <em>citing In re Eynde</em>, 480 F.2d 1364, 1370, 178 USPQ 470, 474 (CCPA 1973)).   Thus, the Office’s attempt to officially notice the level of ordinary skill in the art is improper as a matter of law.</p>
<p>In sum, the Office’s attempts at Official Notice are improper and traversed.  Consequently, there are evidentiary gaps in the rejection of independent claim 1 that are fatal to a <em>prima facie</em> case of obviousness.</p></blockquote>
<p><span style="text-decoration: underline;"><strong>Example 2 &#8211; An Ambiguous Taking of Official Notice </strong></span></p>
<blockquote><p>Lastly, Applicant notes, at page 4 of the Office Action, an apparent attempt to officially notice a fact.  If the Office has intended to take Official Notice, such an attempt is traversed, at least because it is not in compliance with the Office’s own procedures.</p>
<p>Proper use of Official Notice requires compliance with several obligations expressly set forth in the <em>Manual of Patent Examining Procedure</em>.   The Office has failed to meet these obligations.  Specifically, the Office has failed to satisfy its obligations under <a href="http://www.uspto.gov/web/offices/pac/mpep/documents/2100_2144_03.htm" target="_blank"><em>MPEP</em> § 2144.03</a>.  <em>MPEP § 2144.03 (B)</em>, for example, expressly requires the Office to provide specific factual findings predicated on sound technical and scientific reasoning to support taking Official Notice. The <em>MPEP</em> goes on to explain that this means that the Office should present an Applicant with the explicit basis on which Official Notice is based so that the Applicant is able to challenge the assertion in the next reply after the Office action. (<em>MPEP §2144.03(B)</em>).  Naked assertions about what is allegedly known in the art, like those made at page 4 of the Office Action, cannot satisfy these requirements.<br />
In the event that the Office is not attempting to take Official Notice, Applicant respectfully requests confirmation of this fact.</p></blockquote>
<p>Finally, I recommend reviewing the cited <em><a href="http://www.uspto.gov/web/offices/pac/dapp/opla/documents/offnotice.pdf" target="_blank">Memorandum to Patent Examining Corps from the Deputy Commissioner for Patent Examining Policy</a></em> from the first example.  It is a useful summary of the USPTO&#8217;s policies and instructions to its Examiners.</p>
<p style="text-align: left;"><strong>If you like this post, why not </strong><a href="http://patentablydefined.com/feed" target="_self"><strong>grab the RSS feed</strong></a><strong> or </strong><a href="http://feedburner.google.com/fb/a/mailverify?uri=Patentablydefinedcom" target="_self"><strong>subscribe by email</strong></a><strong> and get the latest updates delivered straight to your news reader or inbox?</strong></p>
<p style="text-align: center;">© 2008, Michael E. Kondoudis</p>
<p style="text-align: center;"><strong>The Law Office of Michael E. Kondoudis<br />
</strong><a href="http://www.mekiplaw.com/" target="_blank"><strong>DC Patent Attorney</strong></a><strong><br />
www.mekiplaw.com</strong></p>
]]></content:encoded>
			<wfw:commentRss>http://patentablydefined.com/2008/12/23/examples-of-how-to-respond-to-takings-of-official-notice-part-ii/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Official Notice And Tips For Responding To Rejections Based On Official Notice</title>
		<link>http://patentablydefined.com/2008/11/19/official-notice-and-tips-for-responding-to-rejections-based-on-official-notice/</link>
		<comments>http://patentablydefined.com/2008/11/19/official-notice-and-tips-for-responding-to-rejections-based-on-official-notice/#comments</comments>
		<pubDate>Wed, 19 Nov 2008 09:51:45 +0000</pubDate>
		<dc:creator>mike</dc:creator>
				<category><![CDATA[Examples of Responses]]></category>
		<category><![CDATA[Prosecution Strategy]]></category>

		<guid isPermaLink="false">http://patentablydefined.com/?p=65</guid>
		<description><![CDATA[Official Notice is a principle in U.S. patent prosecution that authorizes an Examiner to depart from the general requirement to present evidence on the record to support a claim rejection.  By “taking official notice”, an Examiner may rely on facts beyond the record to reject claims.  Official Notice is intended for facts that are common [...]]]></description>
			<content:encoded><![CDATA[<p></p><p>Official Notice is a principle in U.S. patent prosecution that authorizes an Examiner to depart from the general requirement to present evidence on the record to support a claim rejection.  By “taking official notice”, an Examiner may rely on facts beyond the record to reject claims.  Official Notice is intended for facts that are common knowledge or capable of unquestionable demonstration.</p>
<p><strong><span style="text-decoration: underline;">Background</span></strong></p>
<p>Federal Courts, pursuant to the Administrative Procedure Act, review USPTO findings of fact under “the substantial evidence” standard, as a result of the Supreme Court’s decision in <span style="text-decoration: underline;">Dickinson v. Zurko</span>.  This standard obligates the USPTO to provide a record that includes sufficient documentary evidence to enable judicial review.  This obligation, in turn, constrains the USPTO’s reliance on Official Notice to only facts that are “capable of such instant and unquestionable demonstration as to defy dispute.”</p>
<p>Additionally, there is a due process argument that an Applicant is entitled to appropriate notice as to why claims are rejected and why submitted patentability arguments are deemed unpersuasive.</p>
<p>A Memorandum from the Deputy Commissioner for Patent Examination Policy on the Procedures for Taking Official Notice is available <a href="http://www.uspto.gov/web/offices/pac/dapp/opla/documents/offnotice.pdf" target="_blank">here</a>.</p>
<p>A leading decision concerning Official Notice is <span style="text-decoration: underline;">In re Ahlert</span>, 424 F.2d 1088, 1091, 165 USPQ 418, 420-421, (CCPA 1970) (stating that assertions of technical facts in areas of esoteric technology must always be supported by citation of some reference work and allegations concerning specific knowledge of the prior art, which might be peculiar to a particular art, should also be supported).</p>
<p><strong><span style="text-decoration: underline;">General Principles</span></strong></p>
<p>1.    <a href="http://www.uspto.gov/web/offices/pac/mpep/documents/2100_2144_03.htm" target="_blank">Section 2144.03 of the Manual of Patent Examining Procedure</a> (MPEP) provides guidelines for relying on Official Notice and personal knowledge.  This should be an Applicant’s primary resource for responding to a use of Official Notice.</p>
<p>2.    Official Notice is permissible only in limited circumstances. For example, use of Official Notice should be rare when an application is under final rejection or action under 37 CFR 1.113. (MPEP § 2144.03(A)).</p>
<p>3.    Official Notice is permissible only for certain types of facts; those that are capable of instant and unquestionable demonstration as being well-known.  Examples of such facts include those that are of common knowledge in the art. (MPEP § 2144.03(A)).</p>
<p>4.    It is never appropriate to rely solely on Official Notice as the principal evidence upon which a rejection was based. Instead, Official Notice is only appropriate for facts that are of “notorious character” and that serve to “fill in the gaps” that might exist in the evidentiary showing to support a particular ground of rejection. (MPEP § 2144.03(A)).</p>
<p>5.  The proper time for taking Official Notice is the first Office Action or as early as possible after a claim feature is presented for examination.  <span style="text-decoration: underline;">Ex parte Gambogi</span>, 62 USPQ2d 1209 (BPAI, 2001)(unpublished).</p>
<p>6.    An Applicant must timely traverse an assertion of Official Notice or the noticed facts will be deemed to be admitted prior art. (MPEP § 2144.03(C)).  A timely traversal is one presented in the reply to the Office action.</p>
<p>7.    To traverse Official Notice, an Applicant must specifically point out the supposed error(s) in the Examiner’s action, which would include stating why the noticed fact is not considered to be common knowledge or well-known in the art.  So, a general allegation that the claims define a patentable invention without any reference to the examiner’s assertion of official notice would be inadequate.  (MPEP § 2144.03(C)).</p>
<p><strong><span style="text-decoration: underline;">The USPTO’s Burden</span></strong></p>
<p>1.    The Office must provide specific factual findings predicated on sound technical and scientific reasoning to support taking Official Notice. (MPEP §2144.03(B)).</p>
<p>2.    The Office should present an Applicant with the explicit basis on which Official Notice is based so that the Applicant is able to challenge the assertion in the next reply after the Office action. (MPEP §2144.03(B)).</p>
<p>3.    An Examiner may rely on facts within his or her own knowledge to support a rejection.  When relying on personal knowledge, however, the Examiner must provide an affidavit or declaration setting forth specific factual statements and an explanation to support the finding.  (MPEP §2144.03(C)).  Such an affidavit is subject to contradiction or explanation by the affidavits of the Applicant and/or other persons. (See 37 CFR §1.104(d)(2)).</p>
<p>4.    When an Applicant challenges a factual assertion as not properly officially noticed or not properly based upon common knowledge, the Office must support the finding with adequate documentary evidence in the next Office action if the rejection is to be maintained.  (MPEP §2144.03(C)).</p>
<p><span style="font-size: small;"><strong><span style="text-decoration: underline;">Proper Finality After Traversal</span></strong></span></p>
<p>If an Examiner adds a document in the next Office action after an Applicant&#8217;s rebuttal, and that document is added only as evidence to support the maintenance of a rejection, the addition of a new document does not result in a new ground of rejection.  Accordingly, the Office action may properly be made final. If, however, the Examiner relies on the newly cited document in any other way, and no amendments are made to the claims, the finality of an Office action should be questioned.  See MPEP §2144.03(D).  Remember, a second or any subsequent action on the merits may properly be made final, unless an examiner introduces a new ground of rejection that is not necessitated by a claim amendment or an IDS.  (MPEP §706.07(a)).</p>
<p style="text-align: left;"><strong>If you like this post, why not </strong><a href="http://patentablydefined.com/feed" target="_self"><strong>grab the RSS feed</strong></a><strong> or </strong><a href="http://feedburner.google.com/fb/a/mailverify?uri=Patentablydefinedcom" target="_self"><strong>subscribe by email</strong></a><strong> and get the latest updates delivered straight to your news reader or inbox?</strong></p>
<p style="text-align: center;">© 2008, Michael E. Kondoudis</p>
<p style="text-align: center;"><strong>The Law Office of Michael E. Kondoudis<br />
</strong><a href="http://www.mekiplaw.com/" target="_blank"><strong>DC Patent Attorney</strong></a><strong><br />
www.mekiplaw.com</strong></p>
]]></content:encoded>
			<wfw:commentRss>http://patentablydefined.com/2008/11/19/official-notice-and-tips-for-responding-to-rejections-based-on-official-notice/feed/</wfw:commentRss>
		<slash:comments>10</slash:comments>
		</item>
		<item>
		<title>Some Strategies For Responding To Rejections Based On Inherency</title>
		<link>http://patentablydefined.com/2008/09/17/some-strategies-for-responding-to-rejections-based-on-inherency/</link>
		<comments>http://patentablydefined.com/2008/09/17/some-strategies-for-responding-to-rejections-based-on-inherency/#comments</comments>
		<pubDate>Wed, 17 Sep 2008 13:58:00 +0000</pubDate>
		<dc:creator>mike</dc:creator>
				<category><![CDATA[Examples of Responses]]></category>
		<category><![CDATA[Practice Suggestions]]></category>
		<category><![CDATA[Prosecution Strategy]]></category>
		<category><![CDATA[The MPEP]]></category>

		<guid isPermaLink="false">http://patentablydefined.com/?p=59</guid>
		<description><![CDATA[Inherency is a doctrine in U.S. patent prosecution by which unstated or unillustrated aspects of cited art are treated as if they are expressly disclosed.  The basis for this doctrine is that some things that will, as a matter of scientific fact, always flow from what is disclosed in art. This doctrine permits the USPTO [...]]]></description>
			<content:encoded><![CDATA[<p></p><p><span style="font-size: small;">Inherency is a doctrine in U.S. patent prosecution by which unstated or unillustrated aspects of cited art are treated as if they are expressly disclosed.  The basis for this doctrine is that some things that will, as a matter of scientific fact, always flow from what is disclosed in art. </span></p>
<p><span style="font-size: small;">This doctrine permits the USPTO to rely on more than just the mere express disclosures of applied art to reject claims under 35 U.S.C. §§102 and 103.</span></p>
<p><span style="font-size: small;">The doctrine of inherency is generally appropriate only in limited circumstances.</span></p>
<p><span style="font-size: small;"><strong><span style="text-decoration: underline;">General Principles </span></strong></span></p>
<p><span style="font-size: small;">1.    Subject matter is only inherent when extrinsic evidence makes it clear that the subject matter is necessarily present in (i.e., necessarily flows from) the disclosure of cited art, and that ordinarily skilled artisans would recognize it.  (<a href="http://www.uspto.gov/web/offices/pac/mpep/documents/2100_2112.htm" target="_blank">MPEP 2112</a>).<br />
</span></p>
<p><span style="font-size: small;">2.    Ordinarily skilled artisans, however, need not recognize this presence at the time of invention.   (<a href="http://www.uspto.gov/web/offices/pac/mpep/documents/2100_2112.htm" target="_blank">MPEP 2112 (II)</a>).<br />
</span></p>
<p><span style="font-size: small;">3.    Inherency cannot be established by mere possibilities or even probabilities.  The fact that a certain result or characteristic may occur or may be present in cited art is not sufficient to establish the inherency of that result or characteristic.  (<a href="http://www.uspto.gov/web/offices/pac/mpep/documents/2100_2112.htm" target="_blank">MPEP 2112 (IV)</a>), citing In re Rijckaert, 9 F.3d 1531, 1534, 28 USPQ2d 1955, 1957 (Fed. Cir. 1993) (reversing a rejection based on inherency because result due to optimization of conditions was not necessarily present in the prior art).<br />
</span></p>
<p><span style="font-size: small;">4.    The Patent Office’s guidelines for using inherency are found in Sections <a href="http://www.uspto.gov/web/offices/pac/mpep/documents/2100_2112.htm" target="_blank">2112</a> – <a href="http://www.uspto.gov/web/offices/pac/mpep/documents/2100_2112_02.htm#sect2112.02" target="_blank">2112.02</a> of the MPEP.  This should be an Applicant’s primary resource for authority when responding to rejections based on inherency.</span></p>
<p><span style="font-size: small;"><strong><span style="text-decoration: underline;">The Patent Office Always Bears an Initial Burden to Establish Proper Reliance on Inherency </span></strong></span></p>
<p><span style="font-size: small;">It is always incumbent on an Examiner to develop reasons supporting a reliance on inherency.   (MPEP 2112 (IV)).</span></p>
<p><span style="font-size: small;">To fully develop reasons, the Office must provide reasonable support for invoking inherency.  This reasonable support requires “a basis in fact” (evidence) and/or reasoning tending to show that an allegedly inherent feature necessarily flows from the teachings of the applied art.  (MPEP 2112 (IV), citing Ex parte Levy, 17 USPQ2d 1461, 1464 (Bd. Pat. App. &amp; Inter. 1990) (emphasis in original)).  Only after providing this reasonable support does the burden to rebut a claim rejection based on inherency shift to an Applicant.  (MPEP 2112 (V), 2112.01(I))).<br />
</span></p>
<p><span style="font-size: small;">The Office enjoys a few logical presumptions to help it provide reasonable support.  For example, reasonable support is presumed to be present when:<br />
</span></p>
<ol>
<li><span style="font-size: small;"> a claimed structure is substantially identical to that of applied art;</span></li>
<li><span style="font-size: small;"> a claimed product is produced by a process substantially identical to that of applied art (identical processes produce identical products);</span></li>
<li><span style="font-size: small;"> a claimed composition is physically identical to that of applied art (identical compositions must have the same properties).</span></li>
</ol>
<p><span style="font-size: small;"> When these circumstances are established, a <em>prima facie</em> case of anticipation or obviousness is made.  (MPEP 2112.01 (I)).</span></p>
<p><span style="font-size: small;"><strong><span style="text-decoration: underline;">An Approach for Responding to Rejections Based on Inherency</span></strong><br />
</span></p>
<p><span style="font-size: small;">An Applicant should always first consider whether the Office has met its burden under MPEP 2112 (IV) to provide a reasonable basis justifying a reliance on inherency.  Only after the Office has met this burden is it absolutely necessary to address the ultimate question of whether the evidence or reasoning is correct.  Nonetheless, as a practical matter, it is often advantageous to explain why allegedly inherent subject matter does not necessarily flow from cited art, even when the Office fails to justify its reliance on inherency.</span></p>
<p><span style="font-size: small;"><strong>Illustrative Examples</strong></span></p>
<p><span style="font-size: small;"><br />
1.  A Failure to Articulate a <em>Prima Facie</em> Case<br />
</span></p>
<blockquote><p><span style="font-size: small;"> In rejecting claim 1 under 35 U.S.C § 102, the Office Action concedes that the <em>Smith</em> patent does not expressly or impliedly teach the aforementioned claim feature of a widget.  (<em>Office Action</em>, page 3).  Nonetheless, the Office rejects claim 1, contending that the feature of a widget is inherently taught by <em>Smith</em>.  Applicant respectfully traverses this rejection at least because the Office has not met its burden to fully develop reasons supporting its reliance on the doctrine of inherency.</span></p>
<p><span style="font-size: small;">The Office always bears the initial burden to develop reasons supporting a reliance on inherency.   (<em>MPEP</em> 2112 (IV)).  To satisfy this burden, the Office must identify some basis in fact or articulate some reasoning at least tending to show that allegedly inherent subject matter necessarily (i.e., inevitability) flows from cited art.  Indeed, the MPEP expressly instructs that:</span></p>
<p><span style="font-size: small;"> &#8220;In relying upon the theory of inherency, the examiner must provide a basis in fact and/or technical reasoning to reasonably support the determination that the allegedly inherent characteristic necessarily flows from the teachings of the applied prior art.&#8221;  Further, since a basis in fact and technical reasoning is required when inherency is invoked, a failure to provide such evidence or rationale is fatal to the reliance on this doctrine.  This is only logical since evidence “must make clear” that the allegedly inherent subject matter is necessarily present in (i.e., necessarily flows from) the disclosure of cited art.  (<em>MPEP</em> 2112).</span></p>
<p><span style="font-size: small;"> A review of page 3 of the Office Action reveals the absence of the required rationale or evidence at least tending to show that the feature of a widget inevitably flows from the disclosures of <em>Smith</em> patent.  Indeed, the Office Action merely asserts that a red widget is inherently present in the <em>Smith</em> patent.  (<em>Office Action</em>, page 3).  This naked assertion, a mere conclusory statement, cannot reasonably be said to be a development of any reason supporting the Office’s reliance on inherency.  Consequently, the Office Action’s reliance on inherency is unsupported and thus improper.</span></p>
<p><span style="font-size: small;"> In sum, the Office Action concedes that the <em>Smith</em> patent does not teach the feature of claim 1 of a widget and any reliance on the doctrine of inherency to provide this necessary teaching is improper.</span></p></blockquote>
<p><span style="font-size: small;">2.  A Substantive Response<br />
</span></p>
<blockquote><p><span style="font-size: small;"> In rejecting claim 1, the Office Action concedes that the <em>Smith</em> patent does not expressly or impliedly teach the aforementioned claim feature of a red widget.  (<em>Office Action</em>, page 3).  Nonetheless, the Office rejects claim 1 under 35 U.S.C. § 102, contending that a red widget is inherent from the disclosures of the Smith patent.  This contention is respectfully traversed, at least because express teachings of the Smith patent preclude reliance on the doctrine of inherency, as a matter of law.</span></p>
<p><span style="font-size: small;">It is well settled that subject matter is inherent only when extrinsic evidence makes it clear that the subject matter necessarily (i.e., inevitably) flows from a disclosure of cited art.  (<em>MPEP</em> 2112).  This requirement is a prerequisite to invoking the doctrine of inherency and cannot be avoided.  Consequently, inherency may never be established by mere probabilities or even possibilities and the mere fact that a certain thing may be present (or may result) is always insufficient.  (<em>MPEP</em> 2112).</span></p>
<p><span style="font-size: small;">A review of the <em>Smith</em> patent reveals no less than three separate teachings that the Smith widget cannot be red.  Applicant respectfully submits that these express teachings so heavily weigh against the inevitable presence of a red widget that they preclude reliance on the doctrine of inherency as a matter of law.  Stated another way, the presence of these express teachings means that the subject matter alleged by the Office Action to be inherent can never reasonably be said to necessarily flow from the <em>Smith</em> patent.  Thus, the Office’s current reliance on inherency can never satisfy the standard set forth in MPEP § 2112 for proper reliance on inherency.</span></p></blockquote>
<p style="text-align: left;"><strong>If you like this post, why not </strong><a href="http://patentablydefined.com/feed" target="_self"><strong>grab the RSS feed</strong></a><strong> or </strong><a href="http://feedburner.google.com/fb/a/mailverify?uri=Patentablydefinedcom" target="_self"><strong>subscribe by email</strong></a><strong> and get the latest updates delivered straight to your news reader or inbox?</strong></p>
<p style="text-align: center;">© 2008, Michael E. Kondoudis</p>
<p style="text-align: center;"><strong>The Law Office of Michael E. Kondoudis<br />
</strong><a href="http://www.mekiplaw.com/" target="_blank"><strong>DC Patent Attorney</strong></a><strong><br />
www.mekiplaw.com</strong></p>
]]></content:encoded>
			<wfw:commentRss>http://patentablydefined.com/2008/09/17/some-strategies-for-responding-to-rejections-based-on-inherency/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>A Few Reasons To Consider Including A Listing Of Claims In Every Response To An Office Action</title>
		<link>http://patentablydefined.com/2008/08/08/a-few-reasons-to-consider-including-a-listing-of-claims-in-every-response-to-an-office-action/</link>
		<comments>http://patentablydefined.com/2008/08/08/a-few-reasons-to-consider-including-a-listing-of-claims-in-every-response-to-an-office-action/#comments</comments>
		<pubDate>Fri, 08 Aug 2008 01:26:22 +0000</pubDate>
		<dc:creator>mike</dc:creator>
				<category><![CDATA[Examples of Responses]]></category>
		<category><![CDATA[Practice Suggestions]]></category>
		<category><![CDATA[Prosecution Strategy]]></category>
		<category><![CDATA[The MPEP]]></category>
		<category><![CDATA[Useful Information]]></category>

		<guid isPermaLink="false">http://patentablydefined.com/?p=55</guid>
		<description><![CDATA[Listings of claims are required in most, but not all responses to Office actions.  This post discusses when they are required and why it may be prudent to include them even when they are not. The Rules The manner of making amendments in a patent application is governed by 37 CFR. 1.121 entitled “Manner of [...]]]></description>
			<content:encoded><![CDATA[<p></p><p><span style="font-size: x-small;">Listings of claims are required in most, but not all responses to Office actions.  This post discusses when they are required and why it may be prudent to include them even when they are not.</span></p>
<p><span style="font-size: x-small;"><strong><span style="text-decoration: underline;">The Rules</span></strong><br />
The manner of making amendments in a patent application is governed by <a href="http://www.uspto.gov/web/offices/pac/mpep/documents/appxr_1_121.htm" target="_blank">37 CFR. 1.121</a> entitled “Manner of Making Amendments in Applications”.  Sections (C) and (C) (1) of that rule addresses claim listings, and state:</span></p>
<p><span style="font-size: x-small;"> </span></p>
<p><span style="font-size: x-small;"> </span></p>
<ul><span style="font-size: x-small;">(c) Claims. … Each amendment document that includes a change to an existing claim, cancellation of an existing claim or addition of a new claim, must include a complete listing of all claims ever presented, including the text of all pending and withdrawn claims, in the application.</span></ul>
<ul><span style="font-size: x-small;">(1) Claim listing. All of the claims presented in a claim listing shall be presented in ascending numerical order. Consecutive claims having the same status of &#8220;canceled&#8221; or &#8220;not entered&#8221; may be aggregated into one statement (e.g., Claims 1-5 (canceled)). The claim listing shall commence on a separate sheet of the amendment document and the sheet(s) that contain the text of any part of the claims shall not contain any other part of the amendment.</span></ul>
<p><span style="font-size: x-small;">Thus, every filing that includes a change to a claim, a cancellation of an existing claim, or an addition of a new claim, must include a complete listing of all claims ever presented in that application.</span></p>
<p><span style="font-size: x-small;">A failure to include a listing of the claims when required renders a filing non-compliant.</span></p>
<p><span style="font-size: x-small;">What about filings in response to an Office action in which no claim changes are made and a listing of the claims is not required (e.g., a Response to a Restriction Requirement of a Request for Reconsideration)?  I have seen such filings prepared both ways; with and without a listing of the claims and I suppose that a case could be made for either approach.  I suggest, however, that it may be a better practice to include a listing of the claims in every response, regardless of whether or not it is required.  Here are a few reasons why.</span></p>
<p><span style="font-size: x-small;"><strong><span style="text-decoration: underline;">1. Including a Listing of Claims Makes Examination Easier.</span></strong></span><span style="font-size: x-small;"> When a response does not include a listing of the claims, anyone reviewing the arguments presented will have to refer to at least one other document (e.g., a previous amendment or the original application) to find a listing of the claims.  In other words, omitting a listing requires the reader to sift through the file wrapper to find a listing of the claims.  At a minimum, this is inefficient and inconvenient.  I prefer not putting an Examiner through this trouble.  The Office’s current production quotas are difficult enough for an Examiner to meet.<br />
The bottom line: making the Examiner’s job easier is in everyone’s best interests and can only help improve the quality of examination.  Besides, every Applicant can benefit from some Examiner goodwill.</span></p>
<p><span style="font-size: x-small;"><strong><span style="text-decoration: underline;">2.  The USPTO Encourages Inclusion of a Claim Listing In Every Response.</span></strong><br />
The following is from <a href="http://www.uspto.gov/web/offices/pac/dapp/revised121qnas.htm" target="_blank">a frequently asked questions page</a> on the USPTO Website about current amendment practice:</span></p>
<ul><span style="font-size: x-small;"> (A10)Q:   May I submit a complete claim listing in a reply when I am not making any changes to the claims, such as responding to a restriction requirement or merely arguing a rejection?</span><span style="font-size: x-small;">A:  Yes. Although a complete claim listing is only required whenever changes are made to any claims, one may be submitted in a reply to an Office action where no changes are being made. It is beneficial to the examiner (and all viewers of the electronic file) to have the most up-to-date set of claims in the most recent paper submitted by the applicant. Note that the claim listing in this situation would not include any claims with markings or any claims with the status identifiers of (new) or (currently amended).<br />
</span></ul>
<p><span style="font-size: x-small;"><strong><span style="text-decoration: underline;">3.  Including a Listing of Claims Promotes Accuracy.</span></strong><br />
The inclusion of a listing of the claims in every filing makes identifying the most current version of the claims easier for everyone who may pick up the file.   This, in turn, tends to reduce: errors in drafts prepared by support staff; the time needed to review such drafts; and non-compliant amendments.</span></p>
<p><span style="font-size: x-small;"><strong><span style="text-decoration: underline;">4.  Including a Listing of Claims Promotes Faster (and Smoother) Review of Work Product.</span></strong><br />
Including a listing of the claims in every response makes review easier.  And, an easier review tends to be a shorter review.  Shortening the time required for review lessens the overall expense for preparing a filing, especially when the reviewer has a higher billing rate than the practitioner who prepared the filing. Besides, making review easier on the reviewer seems to make that review go a little smoother for the practitioner.</span></p>
<p><strong>If you  like this post, why not </strong><a href="http://patentablydefined.com/feed" target="_self"><strong>grab the  RSS feed</strong></a><strong> or </strong><a href="http://feedburner.google.com/fb/a/mailverify?uri=Patentablydefinedcom" target="_self"><strong>subscribe by email</strong></a><strong> and get the latest  updates delivered straight to your news reader or inbox?</strong></p>
<p style="text-align: center;">© 2008,  Michael E. Kondoudis</p>
<p style="text-align: center;"><strong>The  Law Office of Michael E. Kondoudis<br />
</strong><a href="http://www.mekiplaw.com/" target="_blank"><strong>DC Patent  Attorney</strong></a><strong><br />
www.mekiplaw.com</strong></p>
]]></content:encoded>
			<wfw:commentRss>http://patentablydefined.com/2008/08/08/a-few-reasons-to-consider-including-a-listing-of-claims-in-every-response-to-an-office-action/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Some Comments On RCEs, Submissions, And RCE Strategy</title>
		<link>http://patentablydefined.com/2008/07/23/rces-submissions-and-rce-strategy/</link>
		<comments>http://patentablydefined.com/2008/07/23/rces-submissions-and-rce-strategy/#comments</comments>
		<pubDate>Wed, 23 Jul 2008 20:41:56 +0000</pubDate>
		<dc:creator>mike</dc:creator>
				<category><![CDATA[Examples of Responses]]></category>
		<category><![CDATA[Prosecution Strategy]]></category>

		<guid isPermaLink="false">http://patentablydefined.com/?p=53</guid>
		<description><![CDATA[RCE Basics A Request for Continued Examination (RCE) is a request to continue prosecution of an application.  Essentially, RCE practice can be thought of as a mechanism to buy another full examination of an application without having to refile it. An application in which an RCE is filed stays with the same Examiner and keeps [...]]]></description>
			<content:encoded><![CDATA[<p></p><p><span style="font-size: x-small;"> </span><span style="font-size: small;"><span style="text-decoration: underline;"><strong>RCE Basics</strong></span></span></p>
<p><span style="font-size: x-small;"> A Request for Continued Examination (RCE) is a request to continue prosecution of an application.  Essentially, RCE practice </span><span style="font-size: x-small;">can be thought of as a mechanism to buy another full examination of an application without having to refile it.</span><span style="font-size: x-small;"> </span><span style="font-size: x-small;"> An application in which an RCE is filed stays with the same Examiner and keeps the same serial number. </span><span style="font-size: x-small;"> RCEs are available for utility and plant applications, but not for design or provisional applications. </span><span style="font-size: x-small;">RCE practice is governed by <a href="http://www.uspto.gov/web/offices/pac/mpep/documents/appxr_1_114.htm" target="_blank">37 CFR 1.114</a>.<br />
</span></p>
<p><span style="font-size: small;"><span style="text-decoration: underline;"><strong>The Rules Concerning RCE Practice</strong></span></span></p>
<p><span style="font-size: x-small;"> 37 CFR 1.114 sets forth three requirements/conditions for a proper RCE. </span></p>
<ol>
<li><span style="font-size: x-small;"> Prosecution of the application must be closed.  The prosecution of an application is closed when: a final Office action; a Notice of Allowance; or a Quayle Action has been issued.</span></li>
<li><span style="font-size: x-small;">A “submission” must accompany the RCE.<br />
</span></li>
<li><span style="font-size: x-small;">The requisite government fee(s) must accompany the RCE.</span></li>
</ol>
<p><span style="font-size: x-small;"> A “<strong>submission</strong>” as used in 37 CFR 1.114 includes:<br />
</span></p>
<ol>
<li><span style="font-size: x-small;"> an information disclosure statement (IDS);</span></li>
<li><span style="font-size: x-small;"> an amendment to a disclosure (i.e., the specification, claims, or drawings);</span></li>
<li><span style="font-size: x-small;"> new patentability arguments; or</span></li>
<li><span style="font-size: x-small;"> new evidence in support of patentability.</span></li>
</ol>
<p><span style="font-size: x-small;"><a href="http://www.uspto.gov/web/offices/pac/mpep/documents/0700_706_07_h.htm" target="_blank">See MPEP 706.07(h)(II)</a>.<br />
</span></p>
<p><span style="font-size: small;"><span style="text-decoration: underline;"><strong>Some Important Points About RCE Submissions</strong></span><br />
</span></p>
<p><span style="font-size: x-small;">1.    <strong>When any reply to an Office action is outstanding, a submission must meet the requirements of <a href="http://www.uspto.gov/web/offices/pac/mpep/documents/appxr_1_111.htm" target="_blank">37 CFR 1.111</a></strong>.  That is, the reply must be “fully responsive” to the last outstanding Office action.  A submission that is not fully responsive renders an RCE deficient and thus improper.<br />
</span></p>
<p><span style="font-size: x-small;">2.    <strong>Not every one of the examples set forth in 37 CFR 1.114 will constitute a submission in every circumstance</strong>.   Rather, the adequacy of any submission depends on the circumstances in which the RCE is filed.</span></p>
<blockquote><p><span style="font-size: x-small;"><span style="text-decoration: underline;"><strong>Example</strong></span></span><br />
<span style="font-size: x-small;">An IDS filed with an RCE in an application that has been allowed satisfies the submission requirement, since there is no requirement to be fully responsive to any Office action.  That same IDS, however, when filed with an RCE after a final Office action, will not satisfy the submission requirement since it cannot be fully responsive to any Office action.</span></p></blockquote>
<p><span style="font-size: x-small;">3.    <strong>There is a Pseudo Safe Harbor for Some Submissions that are Not Fully Responsive.</strong><br />
RCEs filed with submissions that are not fully responsive to a last outstanding Office action may sometimes be salvaged, depending on whether the submission was a <em>bona fide</em> attempt to respond to the Office action.<br />
</span></p>
<ul>
<li><span style="font-size: x-small;"> If the submission is deemed a <em>bona fide</em> attempt to provide a complete reply, the Applicant will be advised of the deficiency and given a new shortened statutory period of one month or thirty days (whichever is longer) to complete the reply.</span></li>
<li><span style="font-size: x-small;"> If the submission is not deemed a <em>bona fide</em> attempt to provide a complete reply, the RCE will not toll the period for reply and the application will go abandoned after the expiration of the statutory period for reply.</span></li>
</ul>
<p><span style="font-size: x-small;"><a href="http://www.uspto.gov/web/offices/pac/mpep/documents/0700_706_07_h.htm" target="_blank">See MPEP 706.07(h)(VI)</a>.<br />
</span></p>
<p><span style="font-size: x-small;">4.    <strong>A Reply/Request for Reconsideration after a final Office action may satisfy the submission requirement</strong>, even when the Reply/Request has been entered and an advisory action indicates that the arguments are not found persuasive.  The fact that the previously submitted arguments were not found persuasive does not preclude them as a submission under 37 CFR 1.114, provided that such arguments are fully responsive.  Consideration of whether any submission is fully responsive to the last outstanding Office action is done without factoring in the &#8220;final&#8221; status of such outstanding Office action. An Applicant risks a final first Office action, however, so further action would only be prudent.<br />
</span></p>
<p><span style="font-size: x-small;">5.    <strong>An appeal brief or reply brief never satisfies the submission requirement</strong>.  An RCE that contains a statement that incorporates by reference the arguments in a previously filed appeal brief or reply brief may constitute a submission, however. See <a href="http://www.uspto.gov/web/offices/pac/mpep/documents/0700_706_07_h.htm" target="_blank">MPEP  706.07(h)</a>.<br />
</span></p>
<p><span style="font-size: small;">6.    <em><strong><span style="text-decoration: underline;">An improper RCE in an application under appeal may result in an abandonment or an unwanted allowance</span></strong></em>.</span><span style="font-size: x-small;"> The USPTO treats the filing of an RCE in a case under appeal as a withdrawal of the appeal by the applicant, regardless of whether the RCE includes the appropriate fee or a submission.  Consequently, when an RCE is filed without the appropriate fee or a submission, the application will either be allowed or abandoned, depending on the status of the claims.  If there is at least one allowed claim, the application will pass to issue with the allowed claim(s).  Conversely, if there are no allowed claims, the application will be considered abandoned.   See <a href="http://www.uspto.gov/web/offices/pac/mpep/documents/1200_1215_01.htm" target="_blank">MPEP  1215.01</a>.</span></p>
<p><span style="font-size: x-small;">Coming soon &#8211; strategic uses of RCEs and submissions </span></p>
<p><strong>If you  like this post, why not </strong><a href="http://patentablydefined.com/feed" target="_self"><strong>grab the  RSS feed</strong></a><strong> or </strong><a href="http://feedburner.google.com/fb/a/mailverify?uri=Patentablydefinedcom" target="_self"><strong>subscribe by email</strong></a><strong> and get the latest  updates delivered straight to your news reader or inbox?</strong></p>
<p style="text-align: center;">© 2008,  Michael E. Kondoudis</p>
<p style="text-align: center;"><strong>The  Law Office of Michael E. Kondoudis<br />
</strong><a href="http://www.mekiplaw.com/" target="_blank"><strong>DC Patent  Attorney</strong></a><strong><br />
www.mekiplaw.com</strong></p>
<p><a href="http://www.mekiplaw.com" target="_blank"><br />
</a></p>
]]></content:encoded>
			<wfw:commentRss>http://patentablydefined.com/2008/07/23/rces-submissions-and-rce-strategy/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How To Identify Support For A Claim Amendment And When To Do So</title>
		<link>http://patentablydefined.com/2008/06/03/how-to-identify-support-for-a-claim-amendment-and-when-to-do-so/</link>
		<comments>http://patentablydefined.com/2008/06/03/how-to-identify-support-for-a-claim-amendment-and-when-to-do-so/#comments</comments>
		<pubDate>Tue, 03 Jun 2008 19:35:17 +0000</pubDate>
		<dc:creator>mike</dc:creator>
				<category><![CDATA[Examples of Responses]]></category>
		<category><![CDATA[Prosecution Strategy]]></category>

		<guid isPermaLink="false">http://patentablydefined.com/?p=49</guid>
		<description><![CDATA[This post discusses strategic considerations concerning identifications of support for claim amendments. New Matter is Prohibited Section 706.03(o) of the Manual of Patent Examining Procedure (MPEP) addresses rejections based on new matter (matter not supported by the disclosure at the time of filing). This section of the MPEP, citing 35 U.S.C. § 132, articulates the [...]]]></description>
			<content:encoded><![CDATA[<p></p><p>This post discusses strategic considerations concerning identifications of support for claim amendments.</p>
<p><span style="text-decoration: underline;"><strong>New Matter is Prohibited </strong></span></p>
<p><a href="http://www.uspto.gov/web/offices/pac/mpep/documents/0700_706_03_o.htm" target="_blank">Section 706.03(o) of the Manual of Patent Examining Procedure (MPEP)</a> addresses rejections based on new matter (matter not supported by the disclosure at the time of filing).  This section of the MPEP, citing 35 U.S.C. § 132, articulates the  rule that no amendment may introduce new matter into the disclosure of an invention.</p>
<p>The question of what constitutes new matter may sometimes be difficult to resolve.  After all, an Applicant may rely on every part of the application as originally filed for support for a claim amendment. Additionally, an Applicant is entitled to rely on any inherent or implied teachings of the specification, drawing(s), and claims, in addition to the express teachings.  Still further, because there is no <em>in haec verba</em> requirement, an Applicant is not constrained to the terminology used in the application as filed.</p>
<p>In view of the occasional difficulty in resolving new matter issues, and the objection/rejection an Examiner is instructed to make if there is a question of whether a claim amendment might introduce new matter, it may be prudent to consider including identifications of support for claim amendments to help avoid good faith, but ultimately incorrect, new matter rejections.</p>
<p><strong><span style="text-decoration: underline;">Identifying Support For a Claim Amendment May Have Risk</span></strong></p>
<p>A cautious prosecutor, however, will recognize that every identification of support carries with it some risk.  For example, there is a possible risk of error.  This is of particular concern since an Applicant is correlating claim features to portions of the disclosure. Also, unless all support is identified, an Applicant risks an implication that only the identified portion(s) of a disclosure support an amendment.  Both the argument estoppel of the former example and the implication of the latter can be problematic in litigation.</p>
<p>Because of the issues, it may be worth considering reserving identifications of specific support for situations when doing so will be advantageous to the Applicant.<br />
<strong><br />
</strong></p>
<p><strong><span style="text-decoration: underline;">A Risk/Reward Analysis Is Useful to Minimize Unnecessary Identifications of Support</span></strong></p>
<p>A prosecutor can provide value to a client by engaging in a risk/reward analysis and, when the analysis weighs in favor of identifying support, doing so strategically.  Here, the analysis might be whether the likelihood of an objection/rejection outweighs the risk of potential litigation issues, in view of factors such as whether: an Examiner has a history of questioning support for claim amendments; claim terminology deviates from what was used in the application as filed; and support will be difficult to locate in the originally filed disclosure.</p>
<p><strong><span style="text-decoration: underline;">Strategic Examples</span></strong></p>
<p><strong>1.  A Generic Identification</strong><br />
When a risk/reward analysis does not weigh in favor of identifying support, the following paragraph might be used:</p>
<blockquote><p>Applicant submits that support for these amendments can be found in the disclosure as originally filed, and therefore no new matter has been added.</p></blockquote>
<p><strong>2.  A Specific, Non-Limiting Identification of Support</strong><br />
When a risk/reward analysis weighs in favor of identifying support for a claim amendment, the question becomes “how to do it?” An adequate way might be to state:</p>
<blockquote><p>Applicant has amended claim 1. Paragraph [0025] of the Specification supports this amendment. Thus, no new matter has been added.</p></blockquote>
<p>This identification is acceptable; it is efficient and direct. I submit, however, that this statement does little to address some of the risks inherent to identifications of support.  Thus, there is room for improvement. Consider the following example:</p>
<blockquote><p>Applicant has amended claim 1. Support for this amendment may be found at least at, for example, paragraph [0025] of the Specification as originally filed. Thus, no new matter has been added.</p></blockquote>
<p>I submit that the latter paragraph is an improvement over the former because it is non-limiting.  Consequently, it at least arguably avoids the potential litigation issues discussed above.  First, the latter paragraph uses the word &#8220;may&#8221; instead of “is” or &#8220;can.&#8221; The word “is” conveys certainty.  The word &#8220;can&#8221; expresses the ability to do something.  In contrast, according to many authorities, the word &#8220;may&#8221; indicates only a measure of likelihood or possibility. Thus, &#8220;may” is arguably more appropriate, since the specified location is &#8220;an example.&#8221;  Second, the latter paragraph is crafted to state only that paragraph [0025] provides an <em>example</em> of support, which can be beneficial if other, better, or more advantageous support is identified later in prosecution or litigation.</p>
<p>In the end, the way an applicant identifies support is not as important as understanding when it is necessary and the risks involved.   These considerations will dictate how and when to identify support for a claim amendment.</p>
<p><strong>If you  like this post, why not </strong><a href="http://patentablydefined.com/feed" target="_self"><strong>grab the  RSS feed</strong></a><strong> or </strong><a href="http://feedburner.google.com/fb/a/mailverify?uri=Patentablydefinedcom" target="_self"><strong>subscribe by email</strong></a><strong> and get the latest  updates delivered straight to your news reader or inbox?</strong></p>
<p style="text-align: center;">© 2008,  Michael E. Kondoudis</p>
<p style="text-align: center;"><strong>The  Law Office of Michael E. Kondoudis<br />
</strong><a href="http://www.mekiplaw.com/" target="_blank"><strong>DC Patent  Attorney</strong></a><strong><br />
www.mekiplaw.com</strong></p>
]]></content:encoded>
			<wfw:commentRss>http://patentablydefined.com/2008/06/03/how-to-identify-support-for-a-claim-amendment-and-when-to-do-so/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
		<item>
		<title>How To Respond To § 103 Obviousness Rejections Using The “All Elements Test” In View Of Recent Revisions To Section 2143.03 Of The Manual Of Patent Examining Procedure &#8211; Part II</title>
		<link>http://patentablydefined.com/2008/05/27/how-to-respond-to-%c2%a7-103-obviousness-rejections-using-the-%e2%80%9call-elements-test%e2%80%9d-in-view-of-recent-revisions-to-section-214303-of-the-manual-of-patent-examining-procedure-part-ii/</link>
		<comments>http://patentablydefined.com/2008/05/27/how-to-respond-to-%c2%a7-103-obviousness-rejections-using-the-%e2%80%9call-elements-test%e2%80%9d-in-view-of-recent-revisions-to-section-214303-of-the-manual-of-patent-examining-procedure-part-ii/#comments</comments>
		<pubDate>Tue, 27 May 2008 18:12:45 +0000</pubDate>
		<dc:creator>mike</dc:creator>
				<category><![CDATA[Examples of Responses]]></category>
		<category><![CDATA[Practice Suggestions]]></category>
		<category><![CDATA[Prosecution Strategy]]></category>
		<category><![CDATA[§§102 and 103 Rejections]]></category>

		<guid isPermaLink="false">http://patentablydefined.com/?p=48</guid>
		<description><![CDATA[In an earlier post, I discussed reasons why it is preferable to rely on the MPEP for authority during prosecution. An exception to this guideline is when the MPEP is either incorrect or incomplete, which I suggest is the case with newly revised Section 2143.03. So what is an Applicant to do when the MPEP [...]]]></description>
			<content:encoded><![CDATA[<p></p><p>In <a href="http://patentablydefined.com/?p=45" target="_blank">an earlier post</a>, I discussed reasons why it is  preferable to rely on the MPEP for authority during prosecution.  An  exception to this guideline is when the MPEP is either incorrect or incomplete, which I suggest is the case with newly revised <a href="http://www.uspto.gov/web/offices/pac/mpep/documents/2100_2143_03.htm" target="_blank">Section 2143.03</a>.</p>
<p>So what is an Applicant to do when the MPEP is incomplete?  My suggestion, anecdotally seconded by many readers of this blog, is to cite decisions of the Board of Patent Appeals and Interferences (BPAI).  Fortunately, the BPAI still enforces the all elements test.</p>
<p>For example, a January 2008 BPAI decision entitled <a href="http://des.uspto.gov/Foia/ReterivePdf?system=BPAI&amp;flNm=fd20073733-01-14-2008-1" target="_blank">In re Wada and Murphy</a> (pdf) reversed a § 103 rejection because the Examiner did not explain where or how cited art taught or suggested all of the features of a claimed invention (thank you <a href="http://www.troutmansanders.com/hunter_yancey/">Yancey Hunter</a>!).  Of particular interest is the following BPAI articulation of applicable law:</p>
<blockquote><p>When determining whether a claim is obvious, an examiner must make “a searching comparison of the claimed invention – <em>including all its limitations</em> – with the teaching of the prior art.”  <em>In re Ochiai</em>, 71 F.3d 1565, 1572 (Fed. Cir. 1995) (emphasis added).  Thus, “obviousness requires a suggestion of all limitations in a claim.”  <em>CFMT, Inc. v. Yieldup Intern. Corp.</em>, 349 F.3d 1333, 1342 (Fed. Cir. 2003) (<em>citing In re Royka</em>, 490 F.2d 981, 985 (CCPA 1974)).  Moreover, as the Supreme Court recently stated, “<em>there must be some articulated reasoning</em> with some rational underpinning to support the legal conclusion of obviousness.”  <em>KSR Int&#8217;l v. Teleflex Inc.</em>, 127 S. Ct. 1727, 1741 (2007) (quoting In re Kahn, 441 F.3d 977, 988 (Fed. Cir. 2006) (emphasis added)).</p></blockquote>
<p>Authority such as this is difficult for an Examiner to dismiss.</p>
<p><strong><span style="text-decoration: underline;">Example of a Brief Legal Summary</span></strong></p>
<p>The following is an example of a brief discussion of the current state of the “all elements test” that might be usable to advise an Examiner that the Office cannot simply ignore a claim feature in an obviousness determination.  Presume that independent claim 1 has been rejected under § 103 as unpatentable over an asserted combination of two patents to Smith and Jones but that a specified feature has not been specifically addressed by the Office.</p>
<blockquote><p>For any of these reasons, the aforementioned feature of independent claim 1 cannot reasonable be said to be present in the asserted combination.</p>
<p>The failure of an asserted combination to teach or suggest each and every feature of a claim remains fatal to an obviousness rejection under 35 U.S.C. § 103, despite any recent revision to the Manual of Patent Examining Procedure (MPEP).</p>
<p>Section 2143.03 of the MPEP requires the “consideration” of every claim feature in an obviousness determination.  To render claim 1 unpatentable, however, the Office must do more than merely “consider” each and every feature for this claim.  Instead, the asserted combination of the patents to Smith and Jones must also teach or suggest <em>each and every claim feature</em>.  <em>See In re Royka</em>, 490 F.2d 981, 180 USPQ 580 (CCPA 1974) (emphasis added) (to establish <em>prima facie </em>obviousness of a claimed invention, all the claim features must be taught or suggested by the prior art).  Indeed, as the Board of Patent Appeal and Interferences has recently confirmed, a proper obviousness determination requires that an Examiner make “a searching comparison of the claimed invention – <em>including all its limitations</em> – with the teaching of the prior art.”  <em>See In re Wada and Murph</em>y, Appeal 2007-3733, <em>citing In re Ochiai</em>, 71 F.3d 1565, 1572 (Fed. Cir. 1995) (emphasis in original).   Further, the necessary presence of all claim features is axiomatic, since the Supreme Court has long held that obviousness is a question of law based on underlying factual inquiries, including … ascertaining the differences between <em>the claimed invention</em> and the prior art. <em>Graham v. John Deere Co.</em>, 383 U.S. 1, 148 USPQ 459 (1966) (emphasis added).  Indeed, Applicant submits that this is why <a href="http://www.uspto.gov/web/offices/pac/mpep/documents/0900_904.htm" target="_blank">Section 904 of the MPEP</a> instructs Examiners to conduct an art search that covers “the invention <em>as described and claimed</em>.”  (emphasis added).  Lastly, Applicant respectfully directs attention to MPEP § 2143, the instructions of which buttress the conclusion that obviousness requires at least a suggestion of all of the features of a claim, since the Supreme Court in <em>KSR Int&#8217;l v. Teleflex Inc.</em> stated that “there must be some articulated reasoning with some rational underpinning to support the legal conclusion of obviousness.”  <em>KSR Int&#8217;l v. Teleflex Inc.</em>, 127 S. Ct. 1727, 1741 (2007) (<em>quoting In re Kahn</em>, 441 F.3d 977, 988 (Fed. Cir. 2006).</p>
<p>In sum, it remains well-settled law that obviousness requires at least a suggestion of all of the features in a claim.  <em>See In re Wada and Murphy</em>, <em>citing CFMT, Inc. v. Yieldup Intern. Corp.</em>, 349 F.3d 1333, 1342 (Fed. Cir. 2003) and <em>In re Royka</em>, 490 F.2d 981, 985 (CCPA 1974)).</p></blockquote>
<p><strong>If you  like this post, why not </strong><a href="http://patentablydefined.com/feed" target="_self"><strong>grab the  RSS feed</strong></a><strong> or </strong><a href="http://feedburner.google.com/fb/a/mailverify?uri=Patentablydefinedcom" target="_self"><strong>subscribe by email</strong></a><strong> and get the latest  updates delivered straight to your news reader or inbox?</strong></p>
<p style="text-align: center;">© 2008,  Michael E. Kondoudis</p>
<p style="text-align: center;"><strong>The  Law Office of Michael E. Kondoudis<br />
</strong><a href="http://www.mekiplaw.com/" target="_blank"><strong>DC Patent  Attorney</strong></a><strong><br />
www.mekiplaw.com</strong></p>
]]></content:encoded>
			<wfw:commentRss>http://patentablydefined.com/2008/05/27/how-to-respond-to-%c2%a7-103-obviousness-rejections-using-the-%e2%80%9call-elements-test%e2%80%9d-in-view-of-recent-revisions-to-section-214303-of-the-manual-of-patent-examining-procedure-part-ii/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>How To Respond To § 103 Obviousness Rejections Using The “All Elements Test” In View Of Recent Revisions To Section 2143.03 Of The Manual Of Patent Examining Procedure</title>
		<link>http://patentablydefined.com/2008/05/05/how-to-respond-to-%c2%a7-103-obviousness-rejections-using-the-%e2%80%9call-elements-test%e2%80%9d-in-view-of-recent-revisions-to-section-214303-of-the-manual-of-patent-examining-procedure/</link>
		<comments>http://patentablydefined.com/2008/05/05/how-to-respond-to-%c2%a7-103-obviousness-rejections-using-the-%e2%80%9call-elements-test%e2%80%9d-in-view-of-recent-revisions-to-section-214303-of-the-manual-of-patent-examining-procedure/#comments</comments>
		<pubDate>Mon, 05 May 2008 14:23:54 +0000</pubDate>
		<dc:creator>mike</dc:creator>
				<category><![CDATA[Examples of Responses]]></category>
		<category><![CDATA[Prosecution Strategy]]></category>

		<guid isPermaLink="false">http://patentablydefined.com/?p=45</guid>
		<description><![CDATA[A while back, in response to my post on citing to the Manual of Patent Examining Procedure, reader Michael Hull of Miller, Matthias &#38; Hull asked an astute question (thank you!) about whether section 2143 of the Manual of Patent Examining Procedure (MPEP) would be rewritten in response to KSR. Well, for those who may [...]]]></description>
			<content:encoded><![CDATA[<p></p><p>A while back, in response to my post on citing to the Manual of Patent Examining Procedure, reader Michael Hull of <a href="http://www.millermatthiashull.com/" target="_blank">Miller, Matthias &amp; Hull</a> asked an astute question (thank you!) about whether section 2143 of the Manual of Patent Examining Procedure (MPEP) would be rewritten in response to KSR.  Well, for those who may not be aware, this section has indeed been rewritten.  One of the more noteworthy revisions is the removal of the so-called “all elements test” from section 2143.03, which requires the teaching or suggestion of every claim feature by an asserted combination/modification.</p>
<p>The specific changes to <a href="http://www.uspto.gov/web/offices/pac/mpep/documents/2100_2143_03.htm" target="_blank">section 2143.03</a> are indicated below:</p>
<blockquote><p>2143.03 All Claim Limitations Must Be <span style="text-decoration: line-through;">Taught or Suggested</span><span style="text-decoration: underline;">Considered</span></p>
<p><span style="text-decoration: line-through;">To establish prima facie obviousness of a claimed invention, all the claim features must be taught or suggested by the prior art.  In re Royka, 490 F.2d 981, 180 USPQ 580 (CCPA 1974). </span>All words in a claim must be considered in judging the patentability of that claim against the prior art.&#8221; <em>In re Wilson</em>, 424 F.2d 1382, 1385, 165 USPQ 494, 496 (CCPA 1970). If an independent claim is nonobvious under 35 U.S.C. 103, then any claim depending therefrom is nonobvious. <em>In re Fine</em>, 837 F.2d 1071, 5 USPQ2d 1596 (Fed. Cir. 1988).</p></blockquote>
<p>It remains to be seen if this particular modification will have any significant effect on prosecution (except to lengthen it and possibly result in more appeals).  Based on the following, however, I submit that the all elements test is still good law and should remain in a prosecutor’s arsenal.  Consider the following:</p>
<ol>
<li>The MPEP is not law.  The Federal Circuit has repeatedly affirmed that the MPEP does not have the force of law.  Rather, it is evidence the USPTO’s interpretation of statutes and regulations.  <em>Molins PLC v. Textron, Inc.</em>, 48 F.3d 1172, 1180 (Fed. Cir. 1995).</li>
<li>The USPTO is bound by Federal Circuit precedent.  This is blackletter law.   <a href="http://www.uspto.gov/web/offices/pac/mpep/documents/appxl_35_U_S_C_2.htm" target="_blank">35 U.S.C. § 2(b)</a> authorizes the Commissioner of the USPTO to establish regulations not inconsistent with law for the conduct of proceedings before the USPTO.  Also, it is for this reason that the Federal Circuit has jurisdiction over appeals from decisions by the Board.  See <a href="http://www.uspto.gov/web/offices/pac/mpep/documents/appxl_35_U_S_C_141.htm" target="_blank">35 U.S.C. § 141</a>.</li>
<li>KSR did not overrule <em>In re Royka</em>, 490 F.2d 981, 180 USPQ 580 (CCPA 1974).  The KSR decision did not address the issue of the all elements test because all of the elements were present in the asserted combination.  Instead, it was the propriety of the asserted combination that was at issue.  I addressed KSR and some of its effects in an earlier post <a href="http://patentablydefined.com/?p=16" target="_blank">here</a>.  Thus, <em>In re Royka</em> is still good law.</li>
<li>New, revised section 2143.03 is not incorrect, just incomplete. Section 2143.03 instructs Examiners to consider each claim feature.  This is not an incorrect statement of the law regarding 35 U.S.C. § 103.  However, it is also correct that, in addition to consideration, <em>In re Royka</em> still requires that each claim feature must be present (i.e., taught or suggested) by an asserted combination.</li>
</ol>
<p>Coming up – Examples of ways to assert the all elements test in view of the revision to section 2143.03.</p>
<p><strong>If you  like this post, why not </strong><a href="http://patentablydefined.com/feed" target="_self"><strong>grab the  RSS feed</strong></a><strong> or </strong><a href="http://feedburner.google.com/fb/a/mailverify?uri=Patentablydefinedcom" target="_self"><strong>subscribe by email</strong></a><strong> and get the latest  updates delivered straight to your news reader or inbox?</strong></p>
<p style="text-align: center;">© 2008,  Michael E. Kondoudis</p>
<p style="text-align: center;"><strong>The  Law Office of Michael E. Kondoudis<br />
</strong><a href="http://www.mekiplaw.com/" target="_blank"><strong>DC Patent  Attorney</strong></a><strong><br />
www.mekiplaw.com</strong></p>
]]></content:encoded>
			<wfw:commentRss>http://patentablydefined.com/2008/05/05/how-to-respond-to-%c2%a7-103-obviousness-rejections-using-the-%e2%80%9call-elements-test%e2%80%9d-in-view-of-recent-revisions-to-section-214303-of-the-manual-of-patent-examining-procedure/feed/</wfw:commentRss>
		<slash:comments>9</slash:comments>
		</item>
		<item>
		<title>Examples Of How To Respond To Written Description Rejections &#8211; The Fundamentals Of The Written Description Requirement And Strategies For Responding To Written Description Rejections – Part II</title>
		<link>http://patentablydefined.com/2008/02/27/examples-of-how-to-respond-to-written-description-rejections-the-fundamentals-of-the-written-description-requirement-and-strategies-for-responding-to-written-description-rejections-%e2%80%93-part-ii/</link>
		<comments>http://patentablydefined.com/2008/02/27/examples-of-how-to-respond-to-written-description-rejections-the-fundamentals-of-the-written-description-requirement-and-strategies-for-responding-to-written-description-rejections-%e2%80%93-part-ii/#comments</comments>
		<pubDate>Wed, 27 Feb 2008 20:58:50 +0000</pubDate>
		<dc:creator>mike</dc:creator>
				<category><![CDATA[Examples of Responses]]></category>
		<category><![CDATA[Practice Suggestions]]></category>
		<category><![CDATA[Prosecution Strategy]]></category>
		<category><![CDATA[§112 Rejections]]></category>

		<guid isPermaLink="false">http://patentablydefined.com/?p=40</guid>
		<description><![CDATA[This post is the second in a series addressing written description rejections. The following are basic examples of responses to written description rejections that apply some of the principles I discussed in my earlier post on the fundamentals of the written description requirement. Examples 1. The Office Action Fails to Establish a Prima Facie Case [...]]]></description>
			<content:encoded><![CDATA[<p></p><p>This post is the second in a series addressing written description rejections.  The following are basic examples of responses to written description rejections that apply some of the principles I discussed in  <a href="http://patentablydefined.com/?p=37" target="_blank">my earlier post on the fundamentals of the written description requirement</a>.</p>
<p><strong><span style="text-decoration: underline;">Examples</span></strong></p>
<p><strong>1. The Office Action Fails to Establish a <span style="text-decoration: underline;">Prima</span> <span style="text-decoration: underline;">Facie</span> Case</strong></p>
<blockquote><p>The Office Action rejected claim 2 for allegedly failing to comply with the written description requirement of the first paragraph of 35 U.S.C. § 112. Applicant respectfully submits that the Office has, by only providing mere conclusory statements, failed to satisfy its burden to articulate a <span style="text-decoration: underline;">prima</span> <span style="text-decoration: underline;">facie</span> case. Without adequate notice of the basis of this rejection, the burden to rebut this rejection with evidence and/or argument has not yet shifted to Applicant.</p>
<p>The <span style="text-decoration: underline;">MPEP</span> repeatedly warns that the Office bears an initial burden of establishing a <span style="text-decoration: underline;">prima</span> <span style="text-decoration: underline;">facie</span> case when making a written description rejection. (<span style="text-decoration: underline;">MPEP</span> §§ 706.07, 2163 (III)(A)). A <span style="text-decoration: underline;">prima</span> <span style="text-decoration: underline;">facie</span> case requires a reasonable basis to challenge the adequacy of the written description.  (<span style="text-decoration: underline;">MPEP</span> § 2163.04).  The <span style="text-decoration: underline;">MPEP</span> equates this reasonable basis with “a preponderance of evidence why a person skilled in the art would not recognize in an applicant&#8217;s disclosure a description of the invention defined by the claims.”   (<span style="text-decoration: underline;">MPEP</span> § 2163(III)(A)).  Consequently, the Office must provide a reasonable basis to reject a claim for failing to satisfy the written description requirement, and this requires “a full development” of the reasons showing that, by a preponderance of the evidence, a person of ordinary skill in the art would not recognize a description of the claimed invention in the disclosure.  In this regard, the <span style="text-decoration: underline;">MPEP</span>; expressly instructs that merely conclusory statements are insufficient.  Rather, every written description rejection “should be stated with a full development of the reasons rather than by a mere conclusion….” (<span style="text-decoration: underline;">MPEP</span> § 706.03).  Stated another way, the Office must adequately explain the perceived shortcomings of the application so that Applicant is properly notified and able to respond.  Finally, until the Office establishes a <span style="text-decoration: underline;">prima</span> <span style="text-decoration: underline;">facie</span> case, an Applicant is not under an obligation to rebut the rejection.  (<span style="text-decoration: underline;">MPEP</span> § 2163.04).  Applicant respectfully submits that such is the case here.</p>
<p>The written description rejection is set forth in its entirety at page 4 of the Office Action, and merely states that the radiator of claim 2 is not supported by the specification.  Absent from this rejection, for example, are any “reasoned or supported statements” supporting this rejection, as the <span style="text-decoration: underline;">MPEP</span> expressly requires.  Indeed, the rejection is devoid of “evidence or reasons” as to why the disclosure fails to reasonably convey to one of ordinary skill in the art that Applicant possessed the claimed invention. Thus, the Office has failed to set forth express findings of fact that support the lack of written description conclusion as its own procedures require.  (<span style="text-decoration: underline;">MPEP</span> §2163.04).  Rather, the provided “reason” is a mere conclusion, which the MPEP expressly warns is insufficient to support this rejection. (<span style="text-decoration: underline;">MPEP</span> § 706.03).</p>
<p>The Office’s failure to meet its burden to articulate a “reasonable basis challenging the adequacy of the written description” with “findings of fact” is fatal to this rejection since Applicant is under no burden to rebut it.  (<span style="text-decoration: underline;">MPEP</span> §§ 706.07, 2163, 2163.04).  For this reason, this rejection is traversed.</p>
<p>Accordingly, Applicant respectfully requests favorable reconsideration and withdrawal of the rejection of claim 2 under the first paragraph of 35 U.S.C. § 112.</p>
<p>In the event that the Office maintains this rejection, Applicant respectfully requests, in accordance with the principles of compact prosecution, that the Office fully develop the reasons for this rejection by articulating, on the record, “properly reasoned and supported statements” that sufficiently explain what, in the Examiner’s view, is missing from the written description.</p></blockquote>
<p><strong>2. A  Substantive Response</strong></p>
<blockquote><p>Claims 1-14 stand rejected under the first paragraph of 35 U.S.C. § 112 for allegedly failing to comply with the written description requirement. Specifically, the Office Action contends that Applicant&#8217;s disclosure does not sufficiently describe the steam valve controller features of amended claims 1, 6, and 10. This contention is respectfully traversed.</p>
<p>When a disclosure describes a claimed invention in a manner that permits one skilled in the art to reasonably conclude that the inventor possessed the claimed invention the written description requirement is satisfied. (<span style="text-decoration: underline;">MPEP</span> §2163 (emphasis added)). This possession may be shown in any number of ways and an Applicant need not describe every claim feature exactly because there is no <span style="text-decoration: underline;">in haec verba</span> requirement. (<span style="text-decoration: underline;">MPEP</span> § 2163).  Rather, to satisfy the written description requirement, all that is required is “reasonable clarity.” (<span style="text-decoration: underline;">MPEP</span> § 2163.02).  Also, an adequate description may be made in any way through express, implicit, or even inherent disclosures in the application, including words, structures, figures, diagrams, and/or formulae.  (<span style="text-decoration: underline;">MPEP</span> §§ 2163(I), 2163.02).  Finally, it is important to be mindful of the generally inverse correlation between the level of skill and knowledge in the art and the specificity of disclosure necessary to satisfy the written description requirement.  (<span style="text-decoration: underline;">MPEP</span> § 2163(II)(A)(2)) (inventions in &#8220;predictable&#8221; or “mature” require a lesser showing of possession than inventions in more “unpredictable” arts).</p>
<p>As the Office Action notes, independent claims 1, 6, and 10 now recite a controller that operates steam valves to control the feeding of steam into feed pipes. Applicant submits that one of ordinary skill in the art would reasonably conclude that Applicant’s disclosure adequately described the claimed invention at the time of filing at least because:</p>
<p>(1)    the feature of the controller is at least impliedly taught by the present application as it was originally filed; and</p>
<p>(2)    art to which the claimed invention belongs is mature and the predictable nature of the art mandates a generally lower showing of possession.</p>
<p>A review of the present application reveals that Applicant describes using steam valves to control operations of steam feed pipes. (See application, e.g., paragraphs [0031], [0032], and [0036]-[0038]). Those of ordinary skill in the art would understand that such a disclosure at least implies the presence of some construct to control the steam valves, especially in view of the maturity and predictability of the subject art.</p>
<p>Applicant also described and illustrated a controller 13 that manages baking operations, including baking operations that include steam. (See application, e.g., paragraph [0039]; FIGS. 2 and 3). Those of ordinary skill in the art would understand that such a disclosure at least implies (and arguably expressly describes) that the controller controls the delivery of steam to the steam pipes.  Further, it is respectfully submitted that one of ordinary skill in the art would have understood that such a controller could be used to control various operations of a steam oven through valve control.</p>
<p>In view of the foregoing, Applicant respectfully submits that ordinarily skilled artisans would reasonably conclude that Applicant possessed the claimed controller on the basis of the aforementioned at least implicit descriptions.  Applicant further submits that this conclusion is buttressed by the maturity and predictability of the art and because an adequate disclosure need not be express or even implied. Thus, the present application adequately describes the claimed invention.</p>
<p>Applicant thus respectfully requests favorable reconsideration and withdrawal of the rejection under 35 U.S.C. § 112.</p>
<p>In the event that the Office maintains this rejection, Applicant respectfully requests, in the interest of its policy of compact prosecution, that the Office explain how the aforementioned portions of the present application fail to communicate to a skilled artisan that Applicant possessed the claimed invention.</p></blockquote>
<p><strong>3.  Original Subject Matter is Rejected</strong></p>
<blockquote><p>Claim 5 stands rejected under the first paragraph of 35 U.S.C. § 112.  Specifically, the Office Action contends that the claim recitation “a widget” is not adequately supported by the specification.  (Office Action, page 5).  This contention is respectfully traversed.</p>
<p>To satisfy the written description requirement of the first paragraph of 35 U.S.C. § 112,  a disclosure need only describe a claimed invention in a manner sufficient to reasonably convey to those skilled in the relevant art that Applicant possessed the claimed invention.  This possession may be shown in any number of ways and an Applicant need not describe every claim feature exactly.  (<span style="text-decoration: underline;">MPEP</span> §2163 (emphasis added)).  Rather, all that is required is “reasonable clarity.” Also, original subject matter enjoys a “strong presumption” of compliance with the written description requirement. (<span style="text-decoration: underline;">MPEP</span> §§ 2163 (I)(A), 2163(II)(A), 2163(II)(A)(3)(a)).</p>
<p>The <span style="text-decoration: underline;">MPEP</span>, in section 2163 (I)(A), identifies several factors that are to be considered in a proper analysis of whether original subject matter complies with the written description requirement, including:</p>
<p>1) the level of skill and knowledge in the art;<br />
2) any disclosure of partial structure;<br />
3) any disclosure of physical/chemical properties;<br />
4) any functional characteristics/correlation between structure and function; and</p>
<p>Initially, it is important to recognize that the rejected subject matter is original to this application.  Thus, the Office must overcome a strong presumption that the rejected claims with the written description requirement. This is because a description as originally filed is presumed to be adequate, unless or until evidence or reasoning to the contrary has been presented by the examiner sufficient to rebut the presumption.  (<span style="text-decoration: underline;">MPEP</span> § 2163.04).</p>
<p>Applying these aforementioned factors to the present application reveals that the claimed feature of “a widget” is adequately described.  [Application of factors regarding original subject matter].</p></blockquote>
<p><strong>If you  like this post, why not </strong><a href="http://patentablydefined.com/feed" target="_self"><strong>grab the  RSS feed</strong></a><strong> or </strong><a href="http://feedburner.google.com/fb/a/mailverify?uri=Patentablydefinedcom" target="_self"><strong>subscribe by email</strong></a><strong> and get the latest  updates delivered straight to your news reader or inbox?</strong></p>
<p style="text-align: center;">© 2008,  Michael E. Kondoudis</p>
<p style="text-align: center;"><strong>The  Law Office of Michael E. Kondoudis<br />
</strong><a href="http://www.mekiplaw.com/" target="_blank"><strong>DC Patent  Attorney</strong></a><strong><br />
www.mekiplaw.com</strong></p>
]]></content:encoded>
			<wfw:commentRss>http://patentablydefined.com/2008/02/27/examples-of-how-to-respond-to-written-description-rejections-the-fundamentals-of-the-written-description-requirement-and-strategies-for-responding-to-written-description-rejections-%e2%80%93-part-ii/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Improper Final Rejections And Suggestions For Avoiding Them (And Hopefully The Expense Of Having To Request Their Withdrawal)</title>
		<link>http://patentablydefined.com/2008/02/12/improper-final-rejections-and-suggestions-for-avoiding-them-and-hopefully-the-expense-of-having-to-request-their-withdrawal/</link>
		<comments>http://patentablydefined.com/2008/02/12/improper-final-rejections-and-suggestions-for-avoiding-them-and-hopefully-the-expense-of-having-to-request-their-withdrawal/#comments</comments>
		<pubDate>Tue, 12 Feb 2008 04:57:45 +0000</pubDate>
		<dc:creator>mike</dc:creator>
				<category><![CDATA[Examples of Responses]]></category>
		<category><![CDATA[Practice Suggestions]]></category>
		<category><![CDATA[Prosecution Strategy]]></category>

		<guid isPermaLink="false">http://patentablydefined.com/?p=39</guid>
		<description><![CDATA[Patent examination in the U.S. Patent Office is guided by the principles of compact prosecution, which I discussed in some detail in an earlier post here. Under the principles of compact prosecution, second Office actions are typically final. The finality of second Office actions is addressed in section 706.07(a) the Manual of Patent Examining Procedure [...]]]></description>
			<content:encoded><![CDATA[<p></p><p>Patent examination in the U.S. Patent Office is guided by the principles of compact prosecution, which I discussed in some detail in an earlier post <a href="http://patentablydefined.com/?p=18" target="_blank">here</a>.  Under the principles of compact prosecution, second Office actions are typically final.</p>
<p>The finality of second Office actions is addressed in section <a href="http://www.uspto.gov/web/offices/pac/mpep/documents/0700_706_07_a.htm" target="_blank">706.07(a)</a> the Manual of Patent Examining Procedure (MPEP), which provides that &#8220;Under present practice, second or any subsequent actions on the merits shall be final, except where the examiner introduces a  new ground of rejection that is neither necessitated by applicant&#8217;s amendment of the claims nor based on information submitted in an information disclosure statement during the period set forth in 37 C.F.R. §1.97(c) with [the appropriate fee].&#8221;</p>
<p><a href="http://www.uspto.gov/web/offices/pac/mpep/documents/appxr_1_97.htm" target="_blank">37 C.F.R. §1.97(c)</a> provides that [upon satisfying certain prerequisites] an information disclosure statement shall be considered by the Office if it is filed after a first or non-final Office action but before the mailing date of a final Office action, a notice of allowance, or an action that otherwise closes prosecution.</p>
<p>Thus, when the Office has to introduce a new ground of rejection and that new ground of rejection is not necessitated by either:</p>
<p>(1) a claim amendment; or</p>
<p>(2)    information submitted by the applicant between the immediately preceding action and a current Office action</p>
<p>then the next Office action cannot properly be made final.</p>
<p>So, for example, when a non-final Office action wholly fails to address a claim or fails to explain the basis for a rejection and the basis is not already of record, the finality of a next Office action rejecting that claim may be precluded. In the latter scenario, there are two arguments for this preclusion. First, any detailed rejection of the subject claim(s) in a next Office action may constitute a new ground rejection that was not necessitated by a claim amendment or an IDS.  Second, the failure to adequately articulate the basis for rejecting a claim is a failure to provide the adequate notice that shifts the burden of rebuttal to the applicant.  This is especially important when technical (non-art) rejections (e.g., §101 (patentable subject matter) are at issue because of the specific instructions of sections of the MPEP such as <a href="http://www.uspto.gov/web/offices/pac/mpep/documents/0700_706_03.htm#sect706.03" target="_blank">§ 706.03</a> (major technical rejections (e.g., lack of proper disclosure, undue breadth, utility, etc.) should be stated with a full development of the reasons rather than by a mere conclusion coupled with some stereotyped expression).</p>
<p>Also, when an applicant successfully traverses a rejection by argument alone (e.g., presents a persuasive patentability argument or disqualifies cited art), the finality of next Office action may be suspect.  For example, it is not uncommon for an Office action to reject some claims based on art (e.g., 35 U.S.C. §102 (anticipation) and/or 35 U.S.C. §103 (obviousness)) and to reject other claims based on technical (non-art) grounds.  When the technical rejection of a claim is traversed by argument alone and no other grounds for rejection of that claim are presented, the finality of a next Office action rejecting that claim is precluded.</p>
<p>These limited circumstances precluding finality are not common and other issues sometimes camouflage them.  Nevertheless, when they are present, a well-informed applicant can help himself or herself avoid an improper final Office action (along with the cost and inconvenience of having to prepare a paper asking for the withdrawal of that finality).</p>
<p>The following are some examples of ways to advise the Office, in a response to a non-final Office action, that a subsequent Office action cannot properly be made final.</p>
<p><strong><span style="text-decoration: underline;">1.   Example – The Office Action Wholly Fails to Acknowledge a Claim</span></strong></p>
<p>In this circumstance, a response might include a section such as:</p>
<blockquote><p><span style="text-decoration: underline;">Finality of the Next Action Is Precluded</span></p>
<p>Lastly, Applicant respectfully requests that the Office confirm the status of independent claim 19, which was not addressed by the Office Action.  Applicant respectfully submits that the Office’s failure to acknowledge claim 19 precludes the finality of a next Office action rejecting that claim, because such a rejection will not have been necessitated by either a claim amendment or based on information from an information disclosure statement. (See MPEP § 706.07(a)).</p></blockquote>
<p><strong><span style="text-decoration: underline;">2.   Example &#8211; The Office Action Fails to Specifically Reject a Claim in the Detailed Action – An Arguable Absence of a Prima Facie Case</span></strong></p>
<p>In this situation, a response might include a statement like the following:</p>
<blockquote><p><span style="text-decoration: underline;">Finality of the Next Action Is Precluded</span></p>
<p>Applicant notes the Office Action does not specifically reject independent claim 19.  Indeed, although the Summary of the Office Action indicates that claim 19 stands rejected, the Detailed Action omits any explanation of how any cited art anticipates [or renders obvious] this claim.  Applicant respectfully submits that this omission amounts to a failure to articulate a <span style="text-decoration: underline;">prima</span> <span style="text-decoration: underline;">facie</span> case of unpatentablity and the burden to rebut this “rejection” has not yet shifted to the Applicant. Consequently, a next Office action rejecting claim 19 cannot properly be made final since only then would the Applicant be obligated to rebut the rejection, presuming that such an Office action sets forth a <span style="text-decoration: underline;">prima</span> <span style="text-decoration: underline;">facie</span> case.  (See MPEP § 706.07(a)).</p></blockquote>
<p><strong><span style="text-decoration: underline;">3.  Example &#8211; The Office Action Makes Only a Rebutted Technical (Non-Art) Rejection Against a Claim</span></strong></p>
<p>Here, an appropriate response might include a section like the following:</p>
<blockquote><p>Accordingly, Applicant respectfully requests favorable reconsideration and withdrawal of the rejection under 35 U.S.C. § 101.</p>
<p><span style="text-decoration: underline;">Finality of the Next Action Is Precluded</span></p>
<p>Applicant notes the absence of an art rejection against independent claim 19 and respectfully submits that a next Office Action rejecting this claim under any section of Title 35 of the United States Code other than 35 U.S.C. § 101 cannot properly be made final because such a rejection will not have been necessitated by a claim amendment or based on information from an information disclosure statement.  (See Section 706.07(a) of The Manual of Patent Examining Procedure).</p></blockquote>
<p><strong><span style="text-decoration: underline;">Conclusion</span></strong></p>
<p>U.S. Patent Office rules preclude the finality of an Office action in certain limited circumstances.  Keeping these circumstances in mind when responding to non-final Office actions, and using techniques like those discussed above, may help an applicant avoid improper final rejections, without having to incur the expense and inconvenience of having to request the withdrawal of improper finality.  So, when appropriate circumstances are present, consider memorializing, in responses to non-final Office actions, reasons why finality of a next Office action would be improper.</p>
<p><strong>If you  like this post, why not </strong><a href="http://patentablydefined.com/feed" target="_self"><strong>grab the  RSS feed</strong></a><strong> or </strong><a href="http://feedburner.google.com/fb/a/mailverify?uri=Patentablydefinedcom" target="_self"><strong>subscribe by email</strong></a><strong> and get the latest  updates delivered straight to your news reader or inbox?</strong></p>
<p style="text-align: center;">© 2008,  Michael E. Kondoudis</p>
<p style="text-align: center;"><strong>The  Law Office of Michael E. Kondoudis<br />
</strong><a href="http://www.mekiplaw.com/" target="_blank"><strong>DC Patent  Attorney</strong></a><strong><br />
www.mekiplaw.com</strong></p>
]]></content:encoded>
			<wfw:commentRss>http://patentablydefined.com/2008/02/12/improper-final-rejections-and-suggestions-for-avoiding-them-and-hopefully-the-expense-of-having-to-request-their-withdrawal/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
		<item>
		<title>The Fundamentals Of The Written Description Requirement And Strategies For Responding To Written Description Rejections – Part I</title>
		<link>http://patentablydefined.com/2008/01/18/the-fundamentals-of-the-written-description-requirement-and-strategies-for-responding-to-written-description-rejections-%e2%80%93-part-i/</link>
		<comments>http://patentablydefined.com/2008/01/18/the-fundamentals-of-the-written-description-requirement-and-strategies-for-responding-to-written-description-rejections-%e2%80%93-part-i/#comments</comments>
		<pubDate>Fri, 18 Jan 2008 17:44:18 +0000</pubDate>
		<dc:creator>mike</dc:creator>
				<category><![CDATA[Examples of Responses]]></category>
		<category><![CDATA[Practice Suggestions]]></category>
		<category><![CDATA[Prosecution Strategy]]></category>
		<category><![CDATA[§112 Rejections]]></category>

		<guid isPermaLink="false">http://patentablydefined.com/?p=37</guid>
		<description><![CDATA[This post is the first of a two-part series on the written description requirement. This first installment discusses the fundamentals of the requirement, relevant law, and the proper standards for compliance. The second installment will provide examples of how to more effectively respond to rejections based on the written description requirement. The Basis for the [...]]]></description>
			<content:encoded><![CDATA[<p></p><p>This post is the first of a two-part series on the written description requirement.  This first installment discusses the fundamentals of the requirement, relevant law, and the proper standards for compliance.  The second installment will provide examples of how to more effectively respond to rejections based on the written description requirement.</p>
<p><strong><span style="text-decoration: underline;">The Basis for the Written Description Requirement</span></strong></p>
<p>The written description requirement arises from the first paragraph of 35 U.S.C. § 112 states:</p>
<blockquote><p><strong> The specification shall contain a written description of the invention</strong>, and of the manner and process of making and     using it, in such full, clear, concise, and exact terms as to enable any person skilled in the art to which it pertains, or with             which it is most nearly connected, to make and use the same, and shall set forth the best mode contemplated by the inventor     of carrying out his invention.</p></blockquote>
<p>In <em>ex parte</em> prosecution, the written description requirement is most often applied against newly presented or amended claims. This requirement can also be applied against original claims and claims copied to provoke an interference, however.</p>
<p><strong><span style="text-decoration: underline;">Fundamentals of the Written Description Requirement</span></strong></p>
<ol> 1.    The written description requirement (WDR) requires an Applicant to demonstrate possession of each feature of a claimed invention.  The Federal Circuit has described the function of the WDR as &#8220;[ensuring] that, as of the filing date, the inventor conveyed with reasonable clarity to those of skill in the art that he was in possession of the subject matter of the claims. <a href="http://www.ll.georgetown.edu/Federal/judicial/fed/opinions/99opinions/99-1066.html" target="_blank"><em>Union Oil Co. of Calif. v. Atlantic Richfield Co.</em>, 208 F.3d 989 (Fed. Cir. 2000)</a>.</ol>
<ol>2.    The Patent Office’s guidelines for examination of patent applications under the written description requirement are found in <a href="http://www.uspto.gov/web/offices/pac/mpep/documents/2100_2163.htm" target="_blank">Section 2163 of the <em>MPEP</em></a>.  This should be an Applicant’s primary resource for authority when articulating  responses to WDR rejections.</ol>
<ol>3.    An Applicant satisfies the WDR by describing all of the features of a claim in a manner that “reasonably conveys” to one of ordinary skill in the art that the Applicant possessed the claimed invention as a whole.  (<em>MPEP</em> § 2163(I)).  To do so, an Applicant may rely on words, structures, figures, diagrams, and formulae of the disclosure.  <em>(MPEP</em> §§ 2163(I), <a href="http://www.uspto.gov/web/offices/pac/mpep/documents/2100_2163_02.htm" target="_blank">2163.02</a>).  A patent specification satisfies the WDR when it discloses a claimed invention in sufficient detail so that one skilled in the art can “reasonably conclude” that the inventor had possession of the claimed invention at the time of filing.  (<em>MPEP</em> § 2163(I).</ol>
<ol>4.    There is no one way to show possession of a claimed invention.  (<em>MPEP</em> § 2163(I)).  Rather, possession may be shown by any description of sufficient, relevant, identifying characteristics that would cause a person ordinarily skilled in the art to recognize that the inventor had possession.  (<em>MPEP</em> § 2163(II)(A)(3)(a)).</ol>
<ol> 5.    Although originally filed subject matter does not ipso facto satisfy the WDR, originally filed subject matter enjoys a “strong presumption” of compliance with the WDR. (<em>MPEP</em> §§ 2163 (I)(A), 2163(II)(A), 2163(II)(A)(3)(a)).  This is because a description as originally filed is presumed to be adequate, unless or until evidence or reasoning to the contrary has been presented by the examiner sufficient to rebut the presumption.  (<a href="http://www.uspto.gov/web/offices/pac/mpep/documents/2100_2163_04.htm" target="_blank"><em>MPEP</em> § 2163.04</a>). The MPEP identifies some factors that are to be considered in a proper WDR analysis of original claims.  These factors include:the level of skill and knowledge in the art;<br />
the disclosure of partial structure or physical/chemical properties; and<br />
any functional characteristics/correlation between structure and function.<em>MPEP</em> §2163 (I)(A).  <strong>Note</strong>:  This presumption is most often implicated in rejections contained in first Office Actions, but this presumption is something to keep in mind anytime originally presented subject matter is rejected for failure to satisfy the WDR.</ol>
<ol> 6.  Three more points.A.  The first paragraph of 35 U.S.C. § 112 does not require that an Applicant to describe claim limitations exactly.  (MPEP § 2163.02).  Instead, an Applicant need only do so with “reasonable clarity” (MPEP § 2163.02) so that a skilled artisan can “reasonably conclude” the Applicant’s possession.B. Generally, there is an inverse correlation between the level of skill and knowledge in the art and the specificity of disclosure necessary to satisfy the written description requirement. (<em>MPEP</em> 2163(II)(A)(2)). Thus, inventions in &#8220;predictable&#8221; or “mature” arts are theoretically subject to less scrutiny under the written description requirement, and should require a lesser showing of possession than more “unpredictable” arts.C.  An Applicant need not disclose in detail, and preferably omits, that which is conventional or well known in the art.  (<em>MPEP</em> § 2163(II)(A)(2)).</ol>
<p><strong><span style="text-decoration: underline;">The Office Always Bears An Initial Burden When Making a Written Description Rejection</span></strong><em><strong><span style="text-decoration: underline;"> </span></strong></em></p>
<ol> 1.      It is always incumbent on an Examiner to fully develop the reasons for a WDR rejection.  Firstly, <a href="http://www.uspto.gov/web/offices/pac/mpep/documents/0700_706_03.htm#sect706.03" target="_blank">section 706.03 of the MPEP</a> warns Examiners that “[w]here a major technical rejection is proper (e.g., lack of proper disclosure, undue breadth, utility, etc.) such rejection should be stated with a full development of the reasons rather than by a mere conclusion coupled with some stereotyped expression.”  Thus, mere conclusory statements are insufficient to support a rejection under Section 112.  Secondly, this obligation to establish a prima facie case is affirmed by the MPEP in its discussions of each requirement of the first paragraph of 35 U.S.C. § 112.  (See, e.g.,  <a href="http://www.uspto.gov/web/offices/pac/mpep/documents/2100_2163.htm" target="_blank"><em>MPEP</em> § 2163</a> (III)(A) (written description); <a href="http://www.uspto.gov/web/offices/pac/mpep/documents/2100_2164_04.htm" target="_blank"><em>MPEP</em> § 2164.04</a> (enablement))</ol>
<ol>2.      A <em>prima facie</em> case requires a reasonable basis to challenge the adequacy of the written description.  (<em>MPEP</em> § 2163.04).  The <em>MPEP</em> equates this reasonable basis with “a preponderance of evidence why a person skilled in the art would not recognize in an applicant&#8217;s disclosure a description of the invention defined by the claims.”   (MPEP § 2163(III)(A)).  Consequently, the Office must arguably provide a reasonable basis to reject a claim for failing to satisfy the WDR, and this requires “a full development” of the reasons showing that, by a preponderance of the evidence, a person of ordinary skill in the art would not recognize a description of the claimed invention in the disclosure.</ol>
<p><strong><span style="text-decoration: underline;">An Approach for Responding to Written Description Rejections</span></strong></p>
<ol> An Applicant should first consider whether the Office has met its burden to establish a <em>prima facie</em> case. The burden on an Examiner to establish a prima facie case cannot be overemphasized.  In the absence of a <em>prima facie</em> case, an Applicant is under no obligation to present a rebuttal.  So, until the Office has met this initial burden to “fully develop reasons for the rejection by providing “properly reasoned and supported statements,” the obligation to rebut a written description rejection does not shift to the Applicant.  Generally then, when an Office Action provides merely conclusory statements, the rejection should be traversed on this ground alone so as to avoid argument estoppel and minimize expense.</ol>
<ol>Next, an Applicant should analyze every specific reason for its particular basis and reasoning.  Flaws and inconsistencies in the reasoning can be used to traverse the rejection since faulty and/or incomplete reasoning likely does not rise to the level of a preponderance of the evidence.</ol>
<p><strong><span style="text-decoration: underline;">A Basic Template For A Response To A Written Description Rejection</span></strong></p>
<ol> When traversing a WDR, it is usually useful to consider including the following five–point “roadmap”:</ol>
<blockquote><p>1. A “when / then” statement articulating the appropriate legal standard (e.g., when Applicant does this, then the requirement of 35 U.S.C. § 112 is satisfied);</p>
<p>2. Reminding the Office that it has the burden of establishing a <em>prima facie</em> case;</p>
<p>3. Advising the Office relevant examination guidelines including presumptions or instructions;</p>
<p>4. Explaining how the Office has not met burden; and/or explaining how the Applicant has satisfied the WDR.</p></blockquote>
<p><strong><span style="text-decoration: underline;">The Patent Office’s Training Materials</span></strong></p>
<ol> The Patent Office has provided Examiners with several decision trees that are useful to measure the sufficiency of a WDR rejection as well as a quick reference to help understand what an Examiner might be trying to convey. These materials can be found <a href="http://www.uspto.gov/web/offices/pac/writtendesc.pdf" target="_blank">here</a>.</ol>
<p>Coming up – Examples of responses to written description rejections that apply the fundamentals of the WDR and the basic template.</p>
<p style="text-align: left;"><strong>If you  like this post, why not </strong><a href="http://patentablydefined.com/feed" target="_self"><strong>grab the  RSS feed</strong></a><strong> or </strong><a href="http://feedburner.google.com/fb/a/mailverify?uri=Patentablydefinedcom" target="_self"><strong>subscribe by email</strong></a><strong> and get the latest  updates delivered straight to your news reader or inbox?</strong></p>
<p style="text-align: center;">© 2008,  Michael E. Kondoudis</p>
<p style="text-align: center;"><strong>The  Law Office of Michael E. Kondoudis<br />
</strong><a href="http://www.mekiplaw.com/" target="_blank"><strong>DC Patent  Attorney</strong></a><strong><br />
www.mekiplaw.com</strong></p>
]]></content:encoded>
			<wfw:commentRss>http://patentablydefined.com/2008/01/18/the-fundamentals-of-the-written-description-requirement-and-strategies-for-responding-to-written-description-rejections-%e2%80%93-part-i/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>The Benefits Of Efficient Responses And Approaches For Efficiently Responding To Rejections Under 35 U.S.C. §103</title>
		<link>http://patentablydefined.com/2007/11/20/the-benefits-of-efficient-responses-and-approaches-for-efficiently-responding-to-rejections-under-35-usc-%c2%a7103/</link>
		<comments>http://patentablydefined.com/2007/11/20/the-benefits-of-efficient-responses-and-approaches-for-efficiently-responding-to-rejections-under-35-usc-%c2%a7103/#comments</comments>
		<pubDate>Tue, 20 Nov 2007 20:59:13 +0000</pubDate>
		<dc:creator>mike</dc:creator>
				<category><![CDATA[Avoiding Estoppel]]></category>
		<category><![CDATA[Examples of Responses]]></category>
		<category><![CDATA[Prosecution Strategy]]></category>
		<category><![CDATA[§§102 and 103 Rejections]]></category>

		<guid isPermaLink="false">http://patentablydefined.com/?p=31</guid>
		<description><![CDATA[There is an old saying that “sometimes, less is more.” This advice has particular applicability to patent prosecution where, with each word written, an Applicant risks generating argument estoppel. Additionally, each written word presents with it an inherent risk of introducing error. Further, extended arguments are generally more expensive since they require additional time to [...]]]></description>
			<content:encoded><![CDATA[<p></p><p>There is an old saying that “sometimes, less is more.” This advice has particular applicability to patent prosecution where, with each word written, an Applicant risks generating argument estoppel. Additionally, each written word presents with it an inherent risk of introducing error. Further, extended arguments are generally more expensive since they require additional time to draft and edit. Moreover, extended arguments tend to be less persuasive than shorter arguments, perhaps because the argument gets “watered down” or perhaps because it is harder to keep a reader’s attention. In the end, in a risk/benefit analysis, the risks associated with unnecessarily extending a patentability argument generally outweigh any potential benefits. For this reason, I submit that not only is it a generally better practice to present  the shortest, most efficient patentability arguments possible, but that it is also worth the time to develop and continually refine approaches that promote this objective.</p>
<p>For instance, a rejection under 35 U.S.C. §103 on the basis that the asserted combination is deficient may be efficiently traversed using the following approach:</p>
<blockquote><p>1. expressly identifying the claim language on which the patentability argument is based;</p>
<p>2. expressly summarizing the patentability argument being presented;</p>
<p>3. identifying the Office’s concession/admission that one of the cited documents does not disclose all of the claim features (hence the need for the combination);</p>
<p>4. identifying the Office’s contention that the missing claim feature(s) is/are in another cited document and expressly stating that it is this specific contention that is being traversed; and</p>
<p>5. explaining why the Office&#8217;s contention is incorrect.</p></blockquote>
<p>This approach focuses on the claim feature(s) at issue, articulates the specific point of contention, and explains the specific deficiency in the asserted combination.  This approach, advantageously, avoids unnecessary characterizations of the claims and the cited art along with the dangers of potential argument estoppel resulting from such unnecessary characterizations.</p>
<p><em><strong><span style="text-decoration: underline;">Examples</span></strong></em></p>
<p>Consider the following hypothetical response to a rejection under 35 U.S.C. §103 based on a combination of a primary citation to a patent to <span style="text-decoration: underline;">Smith</span> and a secondary citation to a patent to <span style="text-decoration: underline;">Jones</span>.</p>
<blockquote><p>Independent claim 1 recites, <span style="text-decoration: underline;">inter</span> <span style="text-decoration: underline;">alia</span>, a widget on a frame.</p>
<p>Applicant submits that neither <span style="text-decoration: underline;">Smith</span> nor <span style="text-decoration: underline;">Jones</span> discloses at least the aforementioned feature of independent claim 1.  In particular, it is submitted that secondary citation to <span style="text-decoration: underline;">Jones</span> does not remedy the conceded deficiency in the primary citation to <span style="text-decoration: underline;">Smith</span>.  Accordingly, without conceding the propriety of the asserted combination, the asserted combination of <span style="text-decoration: underline;">Smith</span> and <span style="text-decoration: underline;">Jones</span> is likewise deficient, even in view of the knowledge of one of ordinary skill in the art.</p>
<p>The Office Action concedes that the primary citation to <span style="text-decoration: underline;">Smith</span> does not disclose a widget on a frame. (<span style="text-decoration: underline;">Office</span> <span style="text-decoration: underline;">Action</span>, page 2). Nonetheless, the Office Action rejects independent claim 1, contending that the secondary citation to <span style="text-decoration: underline;">Jones</span> provides this necessary disclosure. (<span style="text-decoration: underline;">Office</span> <span style="text-decoration: underline;">Action</span>, page 3). This contention is respectfully traversed.</p>
<p><span style="text-decoration: underline;">Jones</span> relates to a perpetual motion machine and discusses an arrangement including a main board 10, a frame holding the main board 20, and a widget 30. (<span style="text-decoration: underline;">Jones</span>, Col. 3, lines 3-13; Fig. 2). <span style="text-decoration: underline;">Jones</span>, however, expressly teaches that widget 30 cannot be located on frame 20. (<span style="text-decoration: underline;">Jones</span>, Col. 3, lines 25-35). Thus, <span style="text-decoration: underline;">Jones</span> does not provide a disclosure that remedies the aforementioned, conceded deficiency in the primary citation to <span style="text-decoration: underline;">Smith</span>.</p></blockquote>
<p>Of course, this technique works equally as well when there is a deficiency in the primary document. In this case, an efficient response might be:</p>
<blockquote><p>Independent claim 1 recites, <span style="text-decoration: underline;">inter</span> <span style="text-decoration: underline;">alia</span>, a widget on a frame.</p>
<p>Applicant submits that neither <span style="text-decoration: underline;">Smith</span> nor <span style="text-decoration: underline;">Jones</span> discloses at least the aforementioned feature of independent claim 1. In particular, it is submitted that the primary citation to <span style="text-decoration: underline;">Smith</span> does not disclose the claimed widget.  Accordingly, without conceding the propriety of the asserted combination, the asserted combination of <span style="text-decoration: underline;">Smith</span> and Jones is likewise deficient, even in view of the knowledge of one of ordinary skill in the art.</p>
<p>The primary citation to <span style="text-decoration: underline;">Smith</span> relates to a method of perpetual motion and discusses a process including energizing a moving unit and employing a widget on a substrate to conserve energy. (<span style="text-decoration: underline;">Smith</span>, FIG. 3).</p>
<p>The Office Action contends that the widget described as being used to conserve energy meets the aforementioned feature of independent claim 1. (<span style="text-decoration: underline;">Office</span> <span style="text-decoration: underline;">Action</span>, page 3). This contention is respectfully traversed.</p>
<p><span style="text-decoration: underline;">Smith</span>, at column 4, lines 1-18, expressly teaches that the widget must be disposed at a central location on a printed circuit board. Thus, <span style="text-decoration: underline;">Smith</span> cannot reasonably be interpreted to disclose the aforementioned feature of independent claim 1.</p>
<p>The secondary citation to <span style="text-decoration: underline;">Jones</span> relates to a perpetual motion machine and is cited for its alleged disclosure of a frame holding a main board. (<span style="text-decoration: underline;">Office</span> <span style="text-decoration: underline;">Action</span>, page 3). Applicant submits that <span style="text-decoration: underline;">Jones</span> does not add anything that would remedy the aforementioned deficiency in <span style="text-decoration: underline;">Smith</span>. Accordingly, favorable reconsideration and withdrawal of the rejection of independent claim 1 under 35 U.S.C. §103 are respectfully requested.</p></blockquote>
<p>Approaches like these can promote the parallel goals of efficiency and accuracy, which also tends to enhance persuasiveness. Firstly, they minimize argument estoppel by expressly identifying: the claim language relied upon; the specific argument being traversed; and the patentability argument being presented. Thus, ambiguity later usable as alleged argument estoppel is minimized. Secondly, these approaches avoid the temptation to summarize or characterize the claim features at issue by identifying the express claim language once, and thereafter referring to the feature as “the aforementioned feature of claim X.”  Lastly, these approaches minimize the length of the argument so as to yield efficiencies and promote a generally more focused and persuasive argument.</p>
<p style="text-align: left;"><strong>If you  like this post, why not </strong><a href="http://patentablydefined.com/feed" target="_self"><strong>grab the  RSS feed</strong></a><strong> or </strong><a href="http://feedburner.google.com/fb/a/mailverify?uri=Patentablydefinedcom" target="_self"><strong>subscribe by email</strong></a><strong> and get the latest  updates delivered straight to your news reader or inbox?</strong></p>
<p style="text-align: center;">© 2007,  Michael E. Kondoudis</p>
<p style="text-align: center;"><strong>The  Law Office of Michael E. Kondoudis<br />
</strong><a href="http://www.mekiplaw.com/" target="_blank"><strong>DC Patent  Attorney</strong></a><strong><br />
www.mekiplaw.com</strong></p>
]]></content:encoded>
			<wfw:commentRss>http://patentablydefined.com/2007/11/20/the-benefits-of-efficient-responses-and-approaches-for-efficiently-responding-to-rejections-under-35-usc-%c2%a7103/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>A Technique To Assert The Patentable Weight Of A Claim Preamble</title>
		<link>http://patentablydefined.com/2007/10/05/a-technique-to-assert-the-patentable-weight-of-a-claim-preamble/</link>
		<comments>http://patentablydefined.com/2007/10/05/a-technique-to-assert-the-patentable-weight-of-a-claim-preamble/#comments</comments>
		<pubDate>Fri, 05 Oct 2007 15:46:57 +0000</pubDate>
		<dc:creator>mike</dc:creator>
				<category><![CDATA[Examples of Responses]]></category>
		<category><![CDATA[Practice Suggestions]]></category>
		<category><![CDATA[Prosecution Strategy]]></category>

		<guid isPermaLink="false">http://patentablydefined.com/?p=28</guid>
		<description><![CDATA[Generally, during the examination of an application, an Examiner attempts to rebut the novelty and non-obviousness of a claim by identifying, in the prior art, teachings or suggestions of each feature of that claim. Some claim features, however, may be ignored in this analysis. These features are said not to be entitled to any “patentable [...]]]></description>
			<content:encoded><![CDATA[<p></p><p>Generally, during the examination of an application, an Examiner attempts to rebut the novelty and non-obviousness of a claim by identifying, in the prior art, teachings or suggestions of each feature of that claim.  Some claim features, however, may be ignored in this analysis.  These features are said not to be entitled to any “patentable weight.”</p>
<p>One of the claim components that frequently gives rise to disputes about patentable weight is a claim&#8217;s preamble (e.g., a device for) which, along with a transitional phrase (e.g., comprising) and a body (e.g., a wheel), constitutes a claim.  Examiners generally decline to consider the novelty and non-obviousness of a claim’s preamble because preambles tend to only provide a context or a purpose for a claimed invention.Similarly, Examiners often dismiss as unpersuasive patentability arguments based on features recited in a preamble.This is, however, by no means a <span style="text-decoration: underline;">per</span> <span style="text-decoration: underline;">se</span> rule.  Indeed, there are circumstances when features in a claim&#8217;s preamble must be given patentable weight.Consequently, when an Applicant relies on features in a preamble to traverse a claim rejection, it often becomes necessary to explain to the Examiner why those features are entitled to patentable weight.</p>
<p><strong><span style="text-decoration: underline;">The Test and the Law</span></strong><br />
There is no litmus test for determining whether a preamble should be given patentable weight. Basically, a claim preamble is said to be as important as the claim as a whole suggests.  Rather, A preamble is entitled to patentable weight when it is “necessary to give life, meaning, and vitality” to the claim.<a href="http://www.ll.georgetown.edu/Federal/judicial/fed/opinions/98opinions/98-1298.pdf" target="_blank"><span style="text-decoration: underline;">Pitney Bowes, Inc. v. Hewlett-Packard Co.</span></a>, 182 F.3d 1298, 1305 (Fed. Cir. 1999).  The Federal Circuit has held that a preamble may give “life, meaning and vitality” to a claim either: (1) explicitly (the claim expressly uses the preamble and the body of the claim to define the claimed invention); or (2) implicitly (proper construction of the claim requires reference to the preamble).So, when an Applicant uses the body of a claim <span style="text-decoration: underline;">and the preamble</span> to define the claimed subject matter, the preamble should be accorded patentable weight.   Conversely, when the body of the claim &#8220;fully and intrinsically&#8221; sets forth the claimed invention, the preamble may not be entitled to patentable weight.  As the <span style="text-decoration: underline;">Pitney Bowes</span> court instructed, when a<span> preamble “offers no distinct definition of any of the claimed invention’s limitations, but rather merely states . . . the purpose or intended use of the invention,” then the preamble cannot be read as a limitation on a claim. The MPEP addresses the patentable weight of preambles in <a href="http://www.uspto.gov/web/offices/pac/mpep/documents/2100_2111_02.htm" target="_blank">section 2111.02</a>, which provides the following limited, specific guidance:</span></p>
<blockquote><p>1.Preambles that limit structure must be given patentable weight (MPEP 2111.02(I)); and<br />
2.Preambles reciting a purpose or an intended use may be given patentable weight (MPEP 2111.02(II).  Specifically, features in the preamble reciting the purpose or intended use of the claimed invention must be evaluated to determine whether the recited purpose or intended use results in a structural difference (or, in the case of process claims, manipulative difference) between the claimed invention and the cited art. If so, the recitation serves to limit the claim.</p></blockquote>
<p><strong><span style="text-decoration: underline;">An Example of an Argument that a Claim Preamble Should Be Given Patentable Weight</span></strong><br />
Presume that claim 1 recites the following:<br />
A method of transmitting a packet over a system including a client and a source device, the packet including a source address and a destination address, the method comprising:<br />
assigning, by the source device, one of plural trees to broadcast the packet to the destination address; &#8230;<br />
associating with the packet an identifier indicative of one of the trees.</p>
<p>An appropriate response to an Office Action that dismisses a patentability argument based on features recited in the preamble (that the cited art does not teach or suggest a packet that includes a destination address), may be the following:</p>
<blockquote><p>Applicant notes, at page 4 of the Office Action, the Office&#8217;s contention that features recited in the preamble of claim 1, and in particular a packet “including &#8230; a destination address” need not be accorded any patentable weight.  This contention is respectfully traversed as being incorrect as a matter of law.</p>
<p>It is established law that when a preamble of a claim provides more than just context for the claimed invention, that preamble should be given patentable weight.  Indeed, when , as is the case here, the body of the claim expressly refers to features in a preamble and uses those referenced features to define the claimed invention, it is legal error not to give that preamble patentable weight.</p>
<p>Claim 1 recites “assigning &#8230; [one tree] to broadcast a packet to a destination address.”  And, this packet is expressly defined by the claim preamble to include that destination address.  Thus, the body of claim 1 expressly incorporates by reference the preamble feature of a packet that includes a destination address.  In this way, the body of the claim depends on the preamble for completeness and gives life, meaning, and vitality to this claim.  For this reason alone, the preamble of claim 1 should be afforded patentable weight. See <span style="text-decoration: underline;">MPEP</span> 2112.02(II).</p>
<p>The preamble of claim 1, however, should be afforded patentable weight for another reason.The MPEP instructs that preambles that limit structure must be given patentable weight.(<span style="text-decoration: underline;">See</span> <span style="text-decoration: underline;">MPEP</span> 2112.02(I)).The incorporation by reference of the preamble feature of a packet “including &#8230; a destination address” defines a packet that has a data structure not found in the applied art.Thus, the preamble of claim 1 must be given patentable weight.</p></blockquote>
<p style="text-align: left;"><strong>If you like this post, why not </strong><a href="http://patentablydefined.com/feed" target="_self"><strong>grab the RSS feed</strong></a><strong> or </strong><a href="http://feedburner.google.com/fb/a/mailverify?uri=Patentablydefinedcom" target="_self"><strong>subscribe by email</strong></a><strong> and get the latest updates delivered straight to your news reader or inbox?</strong></p>
<p style="text-align: center;">© 2007, Michael E. Kondoudis</p>
<p style="text-align: center;"><strong>The Law Office of Michael E. Kondoudis<br />
</strong><a href="http://www.mekiplaw.com/" target="_blank"><strong>DC Patent Attorney</strong></a><strong><br />
www.mekiplaw.com</strong></p>
]]></content:encoded>
			<wfw:commentRss>http://patentablydefined.com/2007/10/05/a-technique-to-assert-the-patentable-weight-of-a-claim-preamble/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Comments On And Practical Suggestions For Improved After Final Practice</title>
		<link>http://patentablydefined.com/2007/09/04/comments-on-and-practical-suggestions-for-improved-after-final-practice/</link>
		<comments>http://patentablydefined.com/2007/09/04/comments-on-and-practical-suggestions-for-improved-after-final-practice/#comments</comments>
		<pubDate>Tue, 04 Sep 2007 14:07:08 +0000</pubDate>
		<dc:creator>mike</dc:creator>
				<category><![CDATA[After Final Practice]]></category>
		<category><![CDATA[Examples of Responses]]></category>
		<category><![CDATA[Practice Suggestions]]></category>
		<category><![CDATA[Prosecution Strategy]]></category>

		<guid isPermaLink="false">http://patentablydefined.com/?p=25</guid>
		<description><![CDATA[This post concerns &#8220;after final practice,&#8221; that is, practice after a final Office Action has been issued in an application. A brief survey of some basics of after final practice follows, along with some suggestions, sample paragraphs, and practice tips for after final practice. Prosecution After Final Rejection is Restricted The most significant aspect of [...]]]></description>
			<content:encoded><![CDATA[<p></p><p>This post concerns &#8220;after final practice,&#8221; that is, practice after a final Office Action has been issued in an application. A brief survey of some basics of after final practice follows, along with some suggestions, sample paragraphs, and practice tips for after final practice.</p>
<p><strong><span style="text-decoration: underline;">Prosecution After Final Rejection is Restricted</span></strong></p>
<p>The most significant aspect of after final practice is that it is restricted. Once a final Office Action has issued, an Applicant is no longer entitled to further unrestricted prosecution on the merits, as a matter of right. This is the result of the Office&#8217;s policy of compact prosecution, which is discussed <a href="http://patentablydefined.com/?p=18" target="_blank">here</a>.</p>
<p>The restricted nature of after final practice has some not insignificant ramifications. For example, the amendments in an Amendment After Final are actually proposed changes to that application, except in limited circumstances. And, entry of those proposed changes is generally at the Examiner&#8217;s discretion, with direction from Patent Office regulations and guidance from the Manual of Patent Examining Procedure (MPEP).</p>
<p><strong><span style="text-decoration: underline;">The Regulations and the MPEP</span></strong></p>
<p>The regulations and the MPEP establish a conceptual hierarchy for the entry of after final responses. <a href="http://www.uspto.gov/web/offices/pac/mpep/documents/0700_714_13.htm" target="_blank">Section 714.13 of the MPEP</a>, entitled &#8220;Amendments and Other Replies After Final Rejection or Action,&#8221; provides that</p>
<blockquote><p>[e]xcept where an amendment merely cancels claims, adopts examiner suggestions, removes issues for appeal, or in some other way requires only a cursory review by the examiner, compliance with the requirement of a showing under 37 CFR §1.116(b)(3) is expected in all amendments after final rejection.</p></blockquote>
<p>And, <a href="http://www.uspto.gov/web/offices/pac/mpep/documents/appxr_1_116.htm#cfr37s1.116" target="_blank">37 CFR §1.116(b)(3)</a> requires a showing of &#8220;good and sufficient reasons&#8221; why the amendment after final rejection is (1) necessary and (2) was not earlier presented. In this regard, the MPEP instructs that a &#8220;refusal to enter the proposed amendment should not be arbitrary&#8221; and that it should be given &#8220;sufficient consideration to determine whether the claims are in condition for allowance and/or whether the issues on appeal are simplified.&#8221; <a href="http://www.uspto.gov/web/offices/pac/mpep/documents/0700_714_13.htm" target="_blank">MPEP 714.13(II)</a>.</p>
<p>Part (b) of <a href="http://www.uspto.gov/web/offices/pac/mpep/documents/appxr_1_116.htm#cfr37s1.116" target="_blank">37 CFR §</a><a href="http://www.uspto.gov/web/offices/pac/mpep/documents/appxr_1_116.htm#cfr37s1.116" target="_blank">1.116</a>, entitled &#8220;Amendments and affidavits or other evidence after final action and prior to appeal&#8221; provides that</p>
<blockquote><p>(b) After a final rejection or other final action &#8230; in an application &#8230; :</p>
<p>(1) An amendment may be made canceling claims or complying with any requirement of form expressly set forth in a previous Office action;</p>
<p>(2) An amendment presenting rejected claims in better form for consideration on appeal may be admitted; or</p>
<p>(3) An amendment touching the merits of the application or patent under reexamination may be admitted upon a showing of good and sufficient reasons why the amendment is necessary and was not earlier presented.</p></blockquote>
<p>Unfortunately, neither the MPEP nor 37 CFR 1.116 provide any examples, standards, or other guidance as to what constitutes &#8220;good and sufficient reasons.&#8221; And, this is a significant standard. Indeed, the Patent Office&#8217;s own <a href="http://www.uspto.gov/ebc/portal/efs/dct_amendment_after_finalrej_tutorial.pdf" target="_blank">electronic filing system (EFS-Web) tutorial</a> wholly ignores the possibility of the existence of &#8220;good and sufficient reasons,&#8221; advising that an Amendment After Final &#8220;will not be entered if it requires an additional search or more than a cursory review.&#8221;</p>
<p>Additionally, section 714.13 (II) of the MPEP instructs Examiners to advise an Applicant when: (1) certain portions of the amendment would be acceptable as placing some of the claims in better form for appeal or complying with objections or requirements as to form, if a separate paper were filed containing only such amendments; and/or (2) proposed amendment(s) to some of the claims would render them allowable.</p>
<p><strong><span style="text-decoration: underline;">The After Final Hierarchy</span></strong></p>
<p>The foregoing regulations and MPEP guidance establishes the following hierarchy:</p>
<blockquote><p>1. Responses After Final that cancel claims or amend an application to address a formal requirement made earlier (e.g., adopting Examiner suggestions) are entered as a matter of right. No showing of &#8220;good and sufficient reasons&#8221; is required.</p>
<p>2. Responses After Final that require only a cursory review by the Examiner (e.g ., removing issues for appeal or presenting rejected claims in better form for appeal) may entered at the non-arbitrary discretion of Examiner with or without a showing of &#8220;good and sufficient reasons.&#8221;</p>
<p>3. Responses After Final that &#8220;touch on the merits&#8221; or otherwise do not require &#8220;only a cursory review by the Examiner&#8221; (e.g., necessitating further search) may be entered at discretion of Examiner with a showing of &#8220;good and sufficient reasons.&#8221;</p></blockquote>
<p>In view of this hierarchy, it would appear to be a better practice to prepare after final responses that appeal to the discretion of the Examiner, when they are not to be entered as a matter of right. Such responses would ideally reflect the restricted nature of after final practice, satisfy the requirements of the relevant rules, and reflect the MPEP&#8217;s guidance, so as to maximize the likelihood of entry.</p>
<p><strong><span style="text-decoration: underline;">Suggestions</span></strong></p>
<p>The following are examples of suggested modifications tailored for after final practice, including some examples of paragraphs to consider including in after final responses to maximize the likelihood of their entry.</p>
<p><strong>1. Acknowledge The Restricted Nature Of After Final Practice And Ask The Examiner To Exercise His/Her Discretion To Enter Your Response</strong></p>
<p>One way to accomplish this might be to begin an after final response with a paragraph like the following:</p>
<blockquote><p>In response to the final Office Action mailed April 5, 2007, and having a period for response set to expire on July 5, 2007, Applicant respectfully requests that the Examiner amend the present application in the manner set forth in this Amendment.</p></blockquote>
<p>Or alternatively,</p>
<blockquote><p>In response to the final Office Action mailed April 5, 2007, and having a period for response set to expire on July 5, 2007, Applicant respectfully requests that the Examiner favorably consider the following remarks.<strong><br />
</strong></p></blockquote>
<p><strong>2. </strong><strong>Determine Where A Reply After Final Rejection Should Be Categorized In The Hierarchy And Expressly Explain Why The Reply Should Be Entered</strong></p>
<p>For example, an Amendment After Final that addresses formal matters raised by an Examiner should be entered as a matter of right. So, an appropriate explanation might be:</p>
<blockquote><p>Applicant submits that this Amendment After Final Rejection only addresses formal matters raised a previous Office Action. Accordingly, Applicant is entitled to entry of this Amendment as a matter of right under 37 C.F.R. §1.116 (b)(1).</p></blockquote>
<p>When an Amendment arguably places the application in better form for appeal, an appropriate explanation might be:</p>
<blockquote><p>Applicant submits that this Amendment After Final Rejection at least places this application in better form for appeal. Applicant respectfully submits that this Amendment should only require a cursory review because the claim amendments presented herein do not add any new features and/or do not significantly alter the scope of the claims. Consequently, the claim amendments should not require any further search by the Examiner. This Amendment is necessary as it clarifies and/or narrows the issues for consideration by the Board and was not earlier presented because Applicant believed that the prior response(s) placed this application in condition for allowance, for at least the reasons set forth in those response(s). Accordingly, entry of the present Amendment, as an earnest attempt to advance prosecution and/or to reduce the number of issues, is requested under 37 C.F.R. §1.116.</p></blockquote>
<p>When an Amendment touches on the merits, an appropriate explanation might be:</p>
<blockquote><p>Applicant submits that this Amendment After Final Rejection places this application in condition for allowance by amending claims in manners that are believed to render all pending claims allowable over the cited art and/or at least place this application in better form for appeal. This Amendment is necessary because &#8230; and was not earlier presented because Applicant believed that the prior response(s) placed this application in condition for allowance, for at least the reasons discussed in those responses. Accordingly, entry of the present Amendment, as an earnest attempt to advance prosecution and/or to reduce the number of issues, is requested under 37 C.F.R. §1.116.</p></blockquote>
<p>Of course, this type of paragraph should be modified to articulate the particular &#8220;good and sufficient&#8221; reason(s) specific to a particular application.</p>
<p><strong>3.  Include An Express Request For The Specific Notice That MPEP §714.13 Instructs Examiners To Provide An Applicant</strong></p>
<p>For example</p>
<blockquote><p>In the event that the Office declines to enter the present Amendment, and (i) any portion of the present Amendment would place some of the claims in better form for appeal if a separate paper were filed containing only such amendments or (ii) any proposed amendment to any claim would render that claim allowable, Applicant respectfully requests that the Office inform Applicant of the same pursuant to MPEP §714.13.</p></blockquote>
<p><strong>4.  File After Final Responses Electronically</strong></p>
<p>Filing electronically avoids the delay between the time documents are received by the Patent Office and the time they are converted and placed into the image file wrapper (IFW). And, since time can be of the essence in after final practice, knowing a document has been received and is in the IFW can be a great benefit. For example, if the after final reply is filed within 2 months of the date of the final Office Action, the shortened statutory period for response will expire either 3 months from the mailing date of the final rejection or on the date the advisory action is mailed, whichever is later. Still further, there are also patent term extension advantages to filing electronically, as I discussed <a href="http://patentablydefined.com/?p=6" target="_blank">here</a>.</p>
<p><strong>5.  When Filing By Mail Or By Hand, Take Advantage Of The U.S. Patent Office&#8217;s Expedited Procedure For After Final Responses</strong></p>
<p>The Patent Office has an expedited processing procedure for processing paper responses after final rejection under 37 CFR 1.116. To take advantage of the expedited procedure, after final responses under 37 CFR 1.116 need to be marked as a &#8220;Reply under 37 CFR 1.116 &#8211; Expedited Procedure &#8211; Technology Center (XXXX)&#8221; on the upper right portion of the paper. Also, if the response is filed by mail, the envelope must be marked &#8220;Mail Stop AF&#8221; in the lower left hand corner. The markings preferably should be written in a bright color with a felt point marker. If the reply is hand-carried to the Customer Window, the outside of the envelope should be marked &#8220;Reply Under 37 CFR 1.116 &#8211; Expedited Procedure &#8211; Technology Center (XXXX).&#8221; See MPEP 714.13(V).</p>
<p><strong><span style="text-decoration: underline;">Three Final Comments</span></strong></p>
<p>1. If you are not filing electronically through the Patent Office&#8217;s EFS-Web, I suggest that you consider starting to. The system is surprisingly simple and easy to use.</p>
<p>2. Under Patent Office rules, every Amendment must include markings showing the changes relative to the last entered amendment. So, in Amendments After Final (or Amendments filed with a request for continued examination (RCE)), it is important to take care not to include markings that indicate changes relative to any unentered amendment. Doing so should result in a Notice Of Non-Compliant Amendment. Never assume that an after final amendment has entered because they are not entered as a matter of right.</p>
<p>3. In view of the U.S. Patent Office&#8217;s new rules changing continuation practice, it appears that getting the most out of every response, before and after final, is going to be more important than ever.</p>
<p style="text-align: left;"><strong>If you like this post, why not </strong><a href="http://patentablydefined.com/feed" target="_self"><strong>grab the RSS feed</strong></a><strong> or </strong><a href="http://feedburner.google.com/fb/a/mailverify?uri=Patentablydefinedcom" target="_self"><strong>subscribe by email</strong></a><strong> and get the latest updates delivered straight to your news reader or inbox?</strong></p>
<p style="text-align: center;">© 2007, Michael E. Kondoudis</p>
<p style="text-align: center;"><strong>The Law Office of Michael E. Kondoudis<br />
</strong><a href="http://www.mekiplaw.com/" target="_blank"><strong>DC Patent Attorney</strong></a><strong><br />
www.mekiplaw.com</strong></p>
]]></content:encoded>
			<wfw:commentRss>http://patentablydefined.com/2007/09/04/comments-on-and-practical-suggestions-for-improved-after-final-practice/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Practical Prosecution Strategies In View Of The U.S. Patent Office&#8217;s New Continuation Rules  &#8211; Part I</title>
		<link>http://patentablydefined.com/2007/08/23/practical-prosecution-strategies-in-view-of-the-us-patent-offices-new-continuation-rules-part-i/</link>
		<comments>http://patentablydefined.com/2007/08/23/practical-prosecution-strategies-in-view-of-the-us-patent-offices-new-continuation-rules-part-i/#comments</comments>
		<pubDate>Thu, 23 Aug 2007 21:56:51 +0000</pubDate>
		<dc:creator>mike</dc:creator>
				<category><![CDATA[Examples of Responses]]></category>
		<category><![CDATA[Prosecution Strategy]]></category>

		<guid isPermaLink="false">http://patentablydefined.com/?p=27</guid>
		<description><![CDATA[On August 21, 2007, the long awaited final rules (“the new rules”) substantially changing (limiting) continuation practice and requests for continued examination (RCEs) were published. This post is the first of a series discussing practice suggestions and prosecution strategies to consider in response to these changes. A Summary of the New Rules Regarding Continuation Practice [...]]]></description>
			<content:encoded><![CDATA[<p></p><p>On August 21, 2007, the long awaited final rules (“the new rules”) substantially changing (limiting) continuation practice and requests for continued examination (RCEs) were published.  This post is the first of a series discussing practice suggestions and prosecution strategies to consider in response to these changes.</p>
<p><strong><span style="text-decoration: underline;">A Summary of the New Rules Regarding Continuation Practice</span></strong></p>
<p>The new rules limit the the number of continuations to which an Applicant is entitled to two.  The new rules also limit the number of RCEs to which an Applicant is entitled to one.  After these quotas are exhausted, an Applicant will be required to show why the content of further filings could not have been previously submitted.  Importantly, these restrictions apply to each claim family, which the Patent Office defines as including an initial application and its continuation or continuation-in-part applications.  Consequently, an Applicant is entitled to just a single RCE for the an entire claim family, as a matter of right.</p>
<p><strong><span style="text-decoration: underline;">The New Rules Are An “Amplification” Of The Patent Office&#8217;s Policy Of “Compact Prosecution”</span></strong></p>
<p>The Patent Office says that these new rules will improve application quality and prevent piecemeal and protracted examination, thereby enhancing the quality and timeliness of both the examination process and issued patents.  Commissioner for Patents John Doll has been quoted as saying that “[these changes] will lead to a more focused examination process that will effectively promote innovation.”</p>
<p><strong><span style="text-decoration: underline;">Commentary On The New Rules</span></strong></p>
<p>I find it difficult to see how limiting continuations and RCEs will effect the Office&#8217;s desired result.  In fact, it seems to me (and many others) that the new rules almost guarantee protracted examination by ensuring that more cases will be appealed to the Board of Patent Appeals.  It is my belief that the companies that have the resources to file multiple continuations are the ones who will easily have the resources to appeal final rejections.  The end result, I believe, will be a tremendous bottleneck at the Board.  One of the best discussions of the problems with the new rules was put forth by the AIPLA in a <a href="http://www.aipla.org/Template.cfm?template=/ContentManagement/ContentDisplay.cfm&amp;ContentID=11276" target="_blank">letter</a> to the Patent Office commenting on the new rules when they were proposed last year.  I agree with the AIPLA, deliberate and cautious prosecution should not be punished.</p>
<p><strong><span style="text-decoration: underline;">Practice Suggestions And Prosecution Strategies</span></strong></p>
<p>It is axiomatic that one way to minimize the effects of the new rules is to try to avoid final Office Actions, while still deliberately and cautiously prosecuting applications.  The following are a few ways to increase the likelihood of achieving this goal.</p>
<p><strong>1.	Use the Office&#8217;s policy of “compact prosecution” to the Applicant&#8217;s advantage</strong></p>
<blockquote><p>The Office&#8217;s policy of “compact prosecution” imposes obligations on Examiners that have important practical ramifications that can be of strategic value in prosecution. So, I suggest getting reacquainted with the policy and exercise every opportunity to use it to try to preclude the finality of second (and/or subsequent) Office Actions.  Aspects of the policy of “compact prosecution” as well as examples of how to advantageously use the policy are discussed <a href="http://patentablydefined.com/?p=18" target="_blank">here</a>.</p></blockquote>
<p><strong>2.	Maximize persuasiveness by avoiding the temptation to make every possible argument in every response</strong></p>
<blockquote><p>A natural reaction to the new rules is to make every possible patentability argument in every response.  I suggest avoiding this temptation.  Instead, try to think like the writer of an appeal brief and present to the Examiner only the best two or three patentability arguments available.  In other words, follow the adage “less is more.”  This approach tends to avoid inadvertently diluting or “burying” the best arguments.  Just make certain to take steps to avoid any implication of a waiver of selectively withheld arguments.  I discussed some techniques for avoiding any such implications in a couple of earlier posts <a href="http://patentablydefined.com/?p=7" target="_blank">here</a> and <a href="http://patentablydefined.com/?p=9" target="_blank">here</a>.</p></blockquote>
<p><strong> 3.  Include a summary when multiple patentability arguments are presented</strong></p>
<blockquote><p>To increase the likelihood that every argument will be considered, I suggest including a summary of the arguments being presented.  This will alert the Examiner that multiple, discrete patentability arguments rather than one long argument will follow.  One way to accomplish is might be to use the following technique.</p></blockquote>
<blockquote><p>Presume that independent claim 1, recites features of an apparatus that includes, among other features, a curved widget with a center passage.  Then, an appropriate summary might look like the following.</p></blockquote>
<blockquote>
<blockquote><p>Applicant respectfully submits that independent claim 1 patentably defines over the asserted combination of the patents to Smith and Jones for at least the following reasons.</p>
<p>1.  The asserted combination is deficient because it does not disclose at least the aforementioned features of claim 1, at least because:</p>
<blockquote><p>(i) the Smith and Jones patents expressly teach that the widget must be flat; and</p>
<p>(ii) the Jones patent does not disclose the center passage.</p></blockquote>
<p>2.The asserted combination is improper at least because each of the combined citations teaches against the asserted combination.</p>
<p>Also, Applicant respectfully submits that the Office has failed to make out a <span style="text-decoration: underline;">prima</span> <span style="text-decoration: underline;">facie</span> case of obviousness against independent claim 1 because it has failed to sufficiently articulate why one of ordinary skill in the art would have been motivated to make the asserted combination.</p></blockquote>
</blockquote>
<p><strong>Coming Up In Part II &#8211; Examiner Interviews, After Final Practice, and Pre-Appeal Requests for Review</strong></p>
<p><strong> </strong></p>
<p><strong> </strong></p>
<p><em></p>
<p style="text-align: left;"><span style="font-style: normal;"><strong>If you like this post, why not </strong></span><a href="http://patentablydefined.com/feed" target="_self"><span style="font-style: normal;"><strong>grab the RSS feed</strong></span></a><span style="font-style: normal;"><strong> or </strong></span><a href="http://feedburner.google.com/fb/a/mailverify?uri=Patentablydefinedcom" target="_self"><span style="font-style: normal;"><strong>subscribe by email</strong></span></a><span style="font-style: normal;"><strong> and get the latest updates delivered straight to your news reader or inbox?</strong></span></p>
<p style="text-align: center;"><span style="font-style: normal;">© 2007, Michael E. Kondoudis</span></p>
<p style="text-align: center;"><span style="font-style: normal;"><strong>The Law Office of Michael E. Kondoudis<br />
</strong></span><a href="http://www.mekiplaw.com/" target="_blank"><span style="font-style: normal;"><strong>DC Patent Attorney</strong></span></a><span style="font-style: normal;"><strong><br />
www.mekiplaw.com</strong></span></p>
<p></em></p>
]]></content:encoded>
			<wfw:commentRss>http://patentablydefined.com/2007/08/23/practical-prosecution-strategies-in-view-of-the-us-patent-offices-new-continuation-rules-part-i/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Advising Clients About The Duty Of Candor &#8211; Part II</title>
		<link>http://patentablydefined.com/2007/07/23/advising-clients-about-the-duty-of-candor-part-ii/</link>
		<comments>http://patentablydefined.com/2007/07/23/advising-clients-about-the-duty-of-candor-part-ii/#comments</comments>
		<pubDate>Mon, 23 Jul 2007 00:12:27 +0000</pubDate>
		<dc:creator>mike</dc:creator>
				<category><![CDATA[Client Communications]]></category>
		<category><![CDATA[Examples of Responses]]></category>

		<guid isPermaLink="false">http://patentablydefined.com/?p=24</guid>
		<description><![CDATA[I have received several inquiries for the memorandum referenced in the first form paragraph of my earlier post on this subject. The following is the basic text I start with when drafting the memorandum for a new client. 2006 Memorandum Re: The Duty of Disclosure and Materiality Every applicant for a U.S. patent has a [...]]]></description>
			<content:encoded><![CDATA[<p></p><p class="MsoNormal"><span style="font-family: Arial; font-size: 15px;">I have received several inquiries for the memorandum referenced in the first form paragraph of my earlier post on this subject. The following is the basic text I start with when drafting the memorandum for a new client.</span></p>
<p class="MsoNormal" style="text-align: center;"><strong><span style="font-size: 11pt; font-family: Arial;"> </span></strong></p>
<p class="MsoNormal" style="text-align: center;"><strong><span style="font-size: 11pt; font-family: Arial;"> </span></strong></p>
<blockquote>
<p class="MsoNormal" style="text-align: center;"><strong><span style="font-size: 11pt; font-family: Arial;">2006 Memorandum Re: The Duty of Disclosure and Materiality</span></strong></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Arial;"> </span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Arial;">Every applicant for a U.S. patent has a duty of candor and good faith in dealing with the United States Patent and Trademark Office (USPTO). This duty generally requires, during the pendency of an application, that certain individuals disclose to the USPTO all known information that is “material to patentability.”<span> </span>A failure to satisfy this duty of candor can have severe consequences, including the unenforceability of any patent that issues from the application.<span> </span>Therefore, it is important to be aware of who must comply with this duty of candor and what makes information “material.”<span> </span></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Arial;"> </span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Arial;">Section 1.56 of Title 37 of the Code of Federal Regulations (known as &#8220;Rule 56&#8243;) provides, among other things, that any individual who is associated with the filing or prosecution of a patent application must comply with this duty.<span> </span>In essence, this means that everyone involved in the procurement of a patent has a duty to disclose information material to the patentability of a claimed invention.<span> </span>This means that Rule 56 applies to, but is not limited to, named inventors, their attorney(s) or agent(s) involved in the preparation or prosecution of the application, any assignee(s), and anyone else who is substantively involved in the preparation of the application and who is associated with the inventor or<span> </span>any assignee.<span> </span>It is importation to appreciate that the application of Rule 56 is limited only those individuals who are involved in the patenting process.<span> </span>A copy of Rule 56 is attached for your review and future reference. </span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Arial;"> </span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Arial;">There is no “bright line test” for determining what information is “material.”<span> </span>Most courts, however, follow a relatively expansive test in which information is deemed material if it is arguably relevant to the issue of patentability of any claim.<span> </span>Rule 56 defines information as “material” when: </span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Arial;"> </span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Arial;"><span> </span>(1)<span> </span>it is not cumulative to information already of record in the application; and</span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Arial;"><span> </span></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Arial;"><span> </span>(2)<span> </span>either (i) establishes a <span style="text-decoration: underline;">prima</span> <span style="text-decoration: underline;">facie</span> case of unpatentability of any claim, by itself or in combination with other information, or (ii) refutes, or is inconsistent with, a position that the applicant has taken relating to the patentability of any claim.<span> </span></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Arial;"> </span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Arial;">Information is generally considered cumulative when it is merely repetitive or is less relevant than information already of record in the application.<span> </span>A <span style="text-decoration: underline;">prima</span> <span style="text-decoration: underline;">facie</span> case of unpatentability exists when the information compels a conclusion that a claim is unpatentable based on a preponderance of evidence, when each term in the claim is given its broadest reasonable construction consistent with the specification, and before any patentablity argument.<span> </span></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Arial;"> </span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Arial;">Non-limiting examples of potentially material information include U.S. or foreign patents or published patent applications, communications from foreign patent offices in related applications, scientific and other journal articles, brochures, and web sites. </span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Arial;"> </span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Arial;">As a “rule of thumb,” we generally recommend erring on the side of caution and disclosing to the USPTO any information that may arguably be relevant to the issue of patentability, so long as it is not overly cumulative.</span></p>
</blockquote>
<p style="text-align: left;"><strong>If you like this post, why not </strong><a href="http://patentablydefined.com/feed" target="_self"><strong>grab the RSS feed</strong></a><strong> or </strong><a href="http://feedburner.google.com/fb/a/mailverify?uri=Patentablydefinedcom" target="_self"><strong>subscribe by email</strong></a><strong> and get the latest updates delivered straight to your news reader or inbox?</strong></p>
<p style="text-align: center;">© 2007, Michael E. Kondoudis</p>
<p style="text-align: center;"><strong>The Law Office of Michael E. Kondoudis<br />
</strong><a href="http://www.mekiplaw.com/" target="_blank"><strong>DC Patent Attorney</strong></a><strong><br />
www.mekiplaw.com</strong></p>
]]></content:encoded>
			<wfw:commentRss>http://patentablydefined.com/2007/07/23/advising-clients-about-the-duty-of-candor-part-ii/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Advising Clients About The Duty Of Candor &#8211; Part I</title>
		<link>http://patentablydefined.com/2007/06/29/advising-clients-about-the-duty-of-candor/</link>
		<comments>http://patentablydefined.com/2007/06/29/advising-clients-about-the-duty-of-candor/#comments</comments>
		<pubDate>Fri, 29 Jun 2007 19:52:01 +0000</pubDate>
		<dc:creator>mike</dc:creator>
				<category><![CDATA[Client Communications]]></category>
		<category><![CDATA[Examples of Responses]]></category>

		<guid isPermaLink="false">http://patentablydefined.com/?p=22</guid>
		<description><![CDATA[This post is a slight departure from previous posts on this blog in that it focuses on communications between prosecutors and clients rather than communications between prosecutors and the U.S. Patent and Trademark Office. The duty of candor that every applicant and patent practitioner owes to the U.S. Patent and Trademark Office (USPTO) has been [...]]]></description>
			<content:encoded><![CDATA[<p></p><p>This post is a slight departure from previous posts on this blog in that it focuses on communications between prosecutors and clients rather than communications between prosecutors and the U.S. Patent and Trademark Office.</p>
<p>The duty of candor that every applicant and patent practitioner owes to the U.S. Patent and Trademark Office (USPTO) has been of increased attention since the Federal Circuit issued its opinion in <a href="http://www.fedcir.gov/opinions/06-1517.pdf">McKesson Information Solutions, Inc. v. Bridge Medical, Inc., 06-1517 (2007)</a>. For now, I will leave the debate about the practical effects of that decision to others. Instead, this post focuses on ways a practitioner can advise and remind a client of this important duty.</p>
<p><em><strong>A Review of the Duty of Candor (Rule 56)</strong></em></p>
<p>The filing of a patent application in the USPTO imposes an obligation on all persons involved with the prosecution of that application to satisfy a duty of candor. This duty of candor is articulated by Section 1.56 of Title 37 of the Code of Federal Regulations (commonly referred to as Rule 56) and requires that all information &#8220;material to patentability&#8221;  must be cited to the USPTO. Information is &#8220;material to patentability&#8221; when (1) it is not cumulative to information already of record in the application, and (2) either: establishes, by itself or in combination with other information, a <em>prima facie</em> case of unpatentability of a claim; or refutes, or is inconsistent with, a position the applicant has taken in (i) opposing an argument of unpatentability relied on by the Office, or (ii) asserting an argument of patentability.</p>
<p>A failure to satisfy this duty can have severe consequences, including the unenforceability of any patent that issues from the application. I submit, therefore, that it is only prudent to expressly advise clients of this continuing duty, and to do so at multiple stages of prosecution. The following are examples of the different form paragraphs I find useful.</p>
<p><em><strong>1.    Upon Filing Of An Application</strong></em></p>
<blockquote><p>Please be advised that every applicant for a U.S. patent has a duty of candor and good faith in dealing with the United States Patent and Trademark Office. This duty extends to all persons involved with the filing and prosecution of an application and requires, during the pendency of the application, the submission of all known information that is material to the patentability of any claim. Accordingly, if you are presently aware of any information that may be material, please let us know so that we may submit that information in an Information Disclosure Statement (IDS). Also, if you become aware of any information that may be material, please let us know as soon as practicable after it is discovered so that we may submit that information in an IDS. A copy of the rule setting forth this duty, along with a memorandum about the duty of disclosure, are enclosed for your convenience and future reference. If you have any questions about this duty, please let us know so that we may answer them for you.</p></blockquote>
<p><em><strong>2.    After A First Or Non-Final Office Action Has Issued</strong></em></p>
<blockquote><p>We remind you that information material to patentability must be cited to the U.S. Patent and Trademark Office. Since an Office Action has been issued in this application, any information cited at this time will be considered as a matter of right only if accompanied by either (i) a government fee <span style="text-decoration: underline;">or</span> (ii) a statement that the information was first cited in any foreign counterpart, or first discovered, within the last three months. Accordingly, if you are or become aware of any information material to patentability that has not yet been cited, please inform us as soon as possible.</p></blockquote>
<p><em><strong>3.    After A Final Office Action Has Issued</strong></em></p>
<blockquote><p>We remind you that information material to patentability must be cited to the U.S. Patent and Trademark Office. Since a final Office Action has been issued in this application, any information cited at this time will be considered as a matter of right only if accompanied by <span style="text-decoration: underline;">both</span> (i) a government fee <span style="text-decoration: underline;">and</span> (ii) a statement that the information was first cited in any foreign counterpart, or first discovered, within the last three months. Accordingly, if you are or become aware of any information material to patentability that has not yet been cited, please inform us as soon as possible.</p></blockquote>
<p><strong>If you like this post, why not </strong><a href="http://patentablydefined.com/feed" target="_self"><strong>grab the RSS feed</strong></a><strong> or </strong><a href="http://feedburner.google.com/fb/a/mailverify?uri=Patentablydefinedcom" target="_self"><strong>subscribe by email</strong></a><strong> and get the latest updates delivered straight to your news reader or inbox?</strong></p>
<p style="text-align: center;">© 2007, Michael E. Kondoudis</p>
<p style="text-align: center;"><strong>The Law Office of Michael E. Kondoudis<br />
</strong><a href="http://www.mekiplaw.com/" target="_blank"><strong>DC Patent Attorney</strong></a><strong><br />
www.mekiplaw.com</strong></p>
]]></content:encoded>
			<wfw:commentRss>http://patentablydefined.com/2007/06/29/advising-clients-about-the-duty-of-candor/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>
