<?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; Prosecution Strategy</title>
	<atom:link href="http://patentablydefined.com/category/avoiding-implications-by-silence/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>The USPTO&#8217;S Newest Pilot Program &#8211; The Patents Ombudsman</title>
		<link>http://patentablydefined.com/2010/04/07/the-usptos-newest-pilot-program-the-patents-ombudsman/</link>
		<comments>http://patentablydefined.com/2010/04/07/the-usptos-newest-pilot-program-the-patents-ombudsman/#comments</comments>
		<pubDate>Wed, 07 Apr 2010 18:03:36 +0000</pubDate>
		<dc:creator>mike</dc:creator>
				<category><![CDATA[Practice Suggestions]]></category>
		<category><![CDATA[Prosecution Strategy]]></category>
		<category><![CDATA[Useful Information]]></category>

		<guid isPermaLink="false">http://patentablydefined.com/2010/04/07/the-usptos-newest-pilot-program-the-patents-ombudsman/</guid>
		<description><![CDATA[Have you ever had a question about an application in prosecution but have been unable to find the correct person to assist you?  Have you ever been unsuccessful in obtaining assistance from an examiner or Supervisory Patent Examiner?  If so, you will want to take note of the USPTO’s new Ombudsman Pilot Program. The Ombudsman [...]]]></description>
			<content:encoded><![CDATA[<p></p><p><span style="font-size: small;">Have you ever had a question about an application in prosecution but have been unable to find the correct person to assist you?  Have you ever been unsuccessful in obtaining assistance from an examiner or Supervisory Patent Examiner?  If so, you will want to take note of the USPTO’s new <span style="color: #cc6600;"> Ombudsman Pilot Program.</span></span></p>
<p><span style="font-size: small;">The Ombudsman Pilot Program is designed to assist in getting the process back on track when there is a breakdown in the normal prosecution process.  This program is not intended to circumvent normal communication between applicants and/or their representatives and examiners or SPEs, however.  Rather, it is intended to serve as an additional resource to practitioners and applicants. </span></p>
<p><span style="font-size: small;">The Ombudsman Pilot Program began yesterday and will continue for at least 12 months.</span></p>
<p><span style="font-size: small;">&gt;&gt; Click <a href="http://www.uspto.gov/patents/ombudsman.jsp" target="_blank">here</a> to visit the homepage for the Ombudsman Pilot Program Ombudsman, which includes an electronic contact form.</span></p>
<p><span style="font-size: small;">&gt;&gt; Click <a href="http://www.uspto.gov/patents/ombudsman_faqs.jsp" target="_blank">here</a> to view some FAQs on the Ombudsman Pilot Program.</span></p>
<p><span style="font-size: small;">&gt;&gt; Click <a href="http://www.uspto.gov/patents/law/notices/75fr17380.pdf" target="_blank">here</a> to download the Federal Register notice for the Ombudsman Pilot Program.</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;">© 2010, 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/2010/04/07/the-usptos-newest-pilot-program-the-patents-ombudsman/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>A Few Ways To Get On The Bad Side Of Your Examiner</title>
		<link>http://patentablydefined.com/2010/02/02/a-few-ways-to-get-on-the-bad-side-of-your-examiner/</link>
		<comments>http://patentablydefined.com/2010/02/02/a-few-ways-to-get-on-the-bad-side-of-your-examiner/#comments</comments>
		<pubDate>Tue, 02 Feb 2010 23:41:32 +0000</pubDate>
		<dc:creator>mike</dc:creator>
				<category><![CDATA[After Final Practice]]></category>
		<category><![CDATA[Prosecution Strategy]]></category>

		<guid isPermaLink="false">http://patentablydefined.com/2010/02/02/a-few-ways-to-get-on-the-bad-side-of-your-examiner/</guid>
		<description><![CDATA[It is almost always in an Applicant’s best interest to maintain the best working relationship possible with an Examiner. After all, a happy Examiner is more likely to be a helpful Examiner. Also, despite the high turnover at the USPTO, you may very well be working with an Examiner again. So, staying on an Examiner’s [...]]]></description>
			<content:encoded><![CDATA[<p></p><p><span style="font-family: Arial; font-size: 15px;">It is almost always in an Applicant’s best interest to maintain the best working relationship possible with an Examiner.<span> </span>After all, a happy Examiner is more likely to be a helpful Examiner.<span> </span>Also, despite the high turnover at the USPTO, you may very well be working with an Examiner again.<span> </span>So, staying on an Examiner’s “good side” is often good business.</span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Arial;">There are many ways to get on the bad side of an Examiner.<span> </span>Some ways are obvious, while others may not be.<span> </span>An exhaustive list is impossible because just like every application, every Examiner is different. <span> </span>Nonetheless, from my many discussions with Examiners over the years, here are five sure-fire ways to get on your Examiner’s bad side.</span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Arial;"> </span><span style="font-size: small;"><span style="color: #cc6600;"><span style="text-decoration: underline;"><span style="font-family: Arial;">The List</span></span></span></span></p>
<p class="MsoNormal"><strong><span style="font-size: 11pt; font-family: Arial;"><span> </span></span></strong></p>
<p class="MsoNormal"><strong><span style="font-size: 11pt; font-family: Arial;"><span> </span><span style="color: #cc6600;">#5 &#8211; File multiple after final papers.<span> </span></span></span></strong></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Arial;">Remember &#8211; Examiners don’t get production credit for issuing Advisory Actions.</span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Arial;"> </span></p>
<p class="MsoNormal"><strong><span style="font-size: 11pt; font-family: Arial;"><span style="color: #cc6600;">#4 &#8211; Present only a general argument with only generic citations to several pieces of art, without an explanation as to how the art supports the argument</span></span></strong></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Arial;">Comment – It appears to me that leaving the grunt work to an Examiner is both unfair and a recipe for a poor Office action in response.<span> </span>Besides, specific citations of evidence tend to make an argument more persuasive.<span> </span>Also, keep in mind the requirements of 37 CFR 1.111(b):</span></p>
<p class="MsoNormal" style="margin-left: 1in;"><strong><span style="font-size: 10pt; font-family: Arial;">In order to be entitled to reconsideration or further examination, the applicant or patent owner must reply to the Office action. The reply by the applicant or patent owner must be reduced to a writing which distinctly and specifically points out the supposed errors in the examiner&#8217;s action and must reply to every ground of objection and rejection in the prior Office action. The reply must present arguments pointing out the specific distinctions believed to render the claims, including any newly presented claims, patentable over any applied references.</span></strong></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Arial;">Moreover, general arguments do not help a pre-appeal request for review because an Applicant cannot direct the panel back to the record when that record lacks specificity. </span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Arial;"> </span></p>
<p class="MsoNormal"><strong><span style="font-size: 11pt; font-family: Arial;"><span style="color: #cc6600;">#3 &#8211; Submit a needlessly lengthy response inflated with numerous boilerplate paragraphs</span></span></strong></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Arial;">Comment &#8211; No examiner needs a legal primer on the law of anticipation.<span> </span>Responses with paragraph after paragraph of boilerplate explanations of §§ 102 and/or 103 tend to lack clarity and can pose a challenge to even the most interested reader.<span> </span><span> </span>Examiners are human and their natural inclination is to skip such paragraphs.<span> </span>This means that they may miss relevant, persuasive arguments, if they are embedded in or near these paragraphs.<span> </span>This also means that an Applicant is wasting resources writing paragraphs that will not be read by the Examiner.<span> </span></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Arial;">Here, I would suggest taking a look at <a href="http://patentablydefined.com/2007/11/20/the-benefits-of-efficient-responses-and-approaches-for-efficiently-responding-to-rejections-under-35-usc-%C2%A7103/" target="_blank">my earlier blog post</a> on this subject. <strong></strong></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Arial;"> </span></p>
<p class="MsoNormal" style="margin-bottom: 0.0001pt;"><strong><span style="font-size: 11pt; font-family: Arial;"><span style="color: #cc6600;">#2 &#8211; Use uncommon terminology when there </span></span></strong></p>
<p class="MsoNormal"><strong><span style="font-size: 11pt; font-family: Arial;">are perfectly good and commonly acceptable terms of art </span></strong></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Arial;">Comment &#8211; Under MPEP § 2111.01(IV) an applicant is entitled to be his or her own lexicographer.<span> </span>But, when an applicant chooses not to characterize an invention in terms that are consistent with commonly used and familiar terminology, he or she potentially impedes the examination of the application.<span> </span>For example, uncommon terminology makes an Examiner’s searching more difficult (i.e., time consuming).<span> </span>With limited time to examine an application, why force an Examiner to spend more time on the art search to the potential detriment of the Office action? </span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Arial;"> </span></p>
<p class="MsoNormal"><strong><span style="font-size: 11pt; font-family: Arial;"><span style="color: #cc6600;">#1 &#8211; Attempting to bully an Examiner at an interview</span></span></strong></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Arial;">With good fortune, you will be working in the patent profession for many years to come.<span> </span>With some misfortune, you will be back before that Examiner you just tried to bully.<span> </span>Enough said.</span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Arial;"> </span></p>
<p class="MsoNormal"><span style="font-size: small;"><span style="color: #cc6600;"><span style="text-decoration: underline;"><span style="font-family: Arial;">Honorable Mentions</span></span></span></span><strong><span style="text-decoration: underline;"><span style="font-size: 11pt; font-family: Arial;"></span></span></strong></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Arial;"><span style="color: #cc6600;">1.</span><span> </span>Asserting that a rejection is somehow incorrect/deficient because claim features you just amended or added were not addressed in the rejections and/or are not found in the art.<span> </span>It seems both illogical and insulting to assert error based on claim features that were not present when the rejection was made.<span> </span>Instead, consider the following approach:</span></p>
<p class="MsoNormal" style="margin-left: 1in;"><strong><span style="font-size: 11pt; font-family: Arial;">Without conceding the propriety of the Office’s characterization of the Smith widget, Applicant respectfully submits that Smith cannot teach the widget of claim 1, as presently amended.</span></strong></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Arial;"><span style="color: #cc6600;">2.</span><span> </span>Responding to a rejection by adding more claims with different combinations of previously presented limitations just to see if the new claims might be patentable, especially when (1) the original claims are left unchanged and/or (2) the applicant has argued that a rejection is traversed because the previously presented claims define over the cited art.</span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Arial;"><span style="color: #cc6600;">3.</span><span> </span>Reaching an agreement during an interview and then doing something completely different in the next response, without any explanation at all.<span> </span></span></p>
<p class="MsoNormal">
<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;">© 2010, 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 class="MsoNormal"><span style="font-family: Arial;"> </span></p>
<p class="MsoNormal"><span style="font-family: Arial;"> </span></p>
<p><!--EndFragment--></p>
]]></content:encoded>
			<wfw:commentRss>http://patentablydefined.com/2010/02/02/a-few-ways-to-get-on-the-bad-side-of-your-examiner/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
		<item>
		<title>A Few More Useful Sections Of The Manual Of Patent Examining Procedure</title>
		<link>http://patentablydefined.com/2009/10/16/a-few-more-useful-sections-of-the-manual-of-patent-examining-procedure/</link>
		<comments>http://patentablydefined.com/2009/10/16/a-few-more-useful-sections-of-the-manual-of-patent-examining-procedure/#comments</comments>
		<pubDate>Fri, 16 Oct 2009 14:31:51 +0000</pubDate>
		<dc:creator>mike</dc:creator>
				<category><![CDATA[Prosecution Strategy]]></category>
		<category><![CDATA[The MPEP]]></category>
		<category><![CDATA[Useful Information]]></category>

		<guid isPermaLink="false">http://patentablydefined.com/2009/10/16/a-few-more-useful-sections-of-the-manual-of-patent-examining-procedure/</guid>
		<description><![CDATA[In my earlier post in this series, I discussed a few sections of the MPEP that I have found to be useful in some specific circumstances.  This post discusses a few more. Some Help For When Patentability Arguments Are Ignored We have all received Office actions in which the Office seems to have ignored patentability [...]]]></description>
			<content:encoded><![CDATA[<p></p><p><span style="font-size: small;">In <a href="http://patentablydefined.com/?p=75" target="_blank">my earlier post in this series</a>, I discussed a few sections of the MPEP that I have found to be useful in some specific circumstances.  This post discusses a few more.</span></p>
<p><span style="font-size: small;"><span style="text-decoration: underline;"><strong>Some Help For When Patentability Arguments Are Ignored</strong></span></span></p>
<p><span style="font-size: small;">We have all received Office actions in which the Office seems to have ignored patentability arguments.  In these situations, take a look at the following sections of the MPEP:</span></p>
<blockquote><p><span style="font-size: small;"><strong>707.07(f) Answer All Material Traversed</strong><br />
In order to provide a complete application file history and to enhance the clarity of the prosecution history record, <em>an examiner must provide clear explanations of all actions taken by the examiner during prosecution of an application</em>&#8230;.<em>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</em>.</span></p></blockquote>
<blockquote><p><span style="font-size: small;"><strong>706 Rejection of Claims</strong><br />
After the application has been read and the claimed invention understood, a prior art search for the claimed invention is made. With the results of the prior art search, including any references provided by the applicant, the patent application should be reviewed and analyzed in conjunction with the state of the prior art to determine whether the claims define a useful, novel, nonobvious, and enabled invention that has been clearly described in the specification. <em>The goal of examination is to clearly articulate any rejection early in the prosecution process so that the applicant has the opportunity to provide evidence of patentability and otherwise reply completely at the earliest opportunity. The examiner then reviews all the evidence, including arguments and evidence responsive to any rejection, before issuing the next Office action.</em> Where the examiner determines that information reasonably necessary for the examination should be required from the applicant under 37 CFR  1.105, such a requirement should generally be made either prior to or with the first Office action on the merits and should follow the procedures in MPEP §   704.10 et seq.</span></p>
<p><span style="font-size: small;">*****</span></p></blockquote>
<p><span style="font-size: small;">(<em>emphasis added</em>).</span></p>
<p><span style="font-size: small;"><span style="text-decoration: underline;"><strong>Some Help When There Appears To Be A Policy of Rejecting All Claims</strong></span></span></p>
<p><span style="font-size: small;">I have been asked on more than one occasion to offer suggestions on how to respond to Examiners who appear to simply refuse to allow claims.  This happens from time to time in various art groups, for a variety of reasons.  While there is no “silver bullet” so to speak, the MPEP does provide some help.</span></p>
<blockquote><p><span style="font-size: small;"><strong>706 Rejection of Claims</strong></span></p>
<p><span style="font-size: small;"> </span></p>
<p><span style="font-size: small;">*****<br />
Although this part of the Manual explains the procedure in rejecting claims, the examiner should never overlook the importance of his or her role in allowing claims which properly define the invention.</span></p></blockquote>
<p><span style="font-size: small;"><span style="text-decoration: underline;"><strong>Some Help For When Office Actions Do Not Apply Cited Art</strong></span></span></p>
<p><span style="font-size: small;">For any number of reasons, some Office actions fail to apply cited art against the claims, except to say that the cited patent teaches or suggests every feature of the claims.  In these situations, take a look at 37 CFR 1.104(c)(2), which is replicated in § 707 of the MPEP:</span></p>
<blockquote><p><span style="font-size: small;"><strong>707 Examiner&#8217;s Letter or Action </strong></span></p>
<p><span><span style="font-size: small;"> </span></span></p>
<p><span><span style="font-size: small;">*****</span></span><br />
<span style="font-size: small;"> (2) In rejecting claims for want of novelty or for obviousness, the examiner must cite the best references at his or her command. <em>When a reference is complex or shows or describes inventions other than that claimed by the applicant, the particular part relied on must be designated as nearly as practicable. The pertinence of each reference, if not apparent, must be clearly explained and each rejected claim specified</em>.</span></p></blockquote>
<p><span style="font-size: small;">(<em>emphasis added</em>).</span></p>
<p><span style="font-size: small;"><span style="text-decoration: underline;"><strong>Some Help for Pro Se Applications</strong></span></span></p>
<p><span style="font-size: small;">For all of you inventors out there prosecuting your own cases, keep the following section of the MPEP in mind:</span></p>
<blockquote><p><span style="font-size: small;"><strong>707.07(j)(I) State When Claims Are Allowable </strong><br />
</span></p>
<p><span style="font-size: small;">I.    INVENTOR FILED APPLICATIONS<br />
When, during the examination of a pro se application it becomes apparent to the examiner that there is patentable subject matter disclosed in the application, the examiner should draft one or more claims for the applicant and indicate in his or her action that such claims would be allowed if incorporated in the application by amendment.</span></p>
<p><span style="font-size: small;"><br />
This practice will expedite prosecution and offer a service to individual inventors not represented by a registered patent attorney or agent. Although this practice may be desirable and is permissible in any case deemed appropriate by the examiner, it will be expected to be applied in all cases where it is apparent that the applicant is unfamiliar with the proper preparation and prosecution of patent applications.</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/10/16/a-few-more-useful-sections-of-the-manual-of-patent-examining-procedure/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>USPTO Joint Labor-Management Task Force Proposes Significant Changes To Examiner Count System</title>
		<link>http://patentablydefined.com/2009/09/30/uspto-joint-labor-management-task-force-proposes-significant-changes-to-examiner-count-system/</link>
		<comments>http://patentablydefined.com/2009/09/30/uspto-joint-labor-management-task-force-proposes-significant-changes-to-examiner-count-system/#comments</comments>
		<pubDate>Thu, 01 Oct 2009 03:02:53 +0000</pubDate>
		<dc:creator>mike</dc:creator>
				<category><![CDATA[Prosecution Strategy]]></category>
		<category><![CDATA[Useful Information]]></category>

		<guid isPermaLink="false">http://patentablydefined.com/2009/09/30/uspto-joint-labor-management-task-force-proposes-significant-changes-to-examiner-count-system/</guid>
		<description><![CDATA[The USPTO has unveiled a series of proposals that would bring significant change to the examiner “count system” – the methodology for determining the time a patent examiner has to complete a patent examination and how much credit is given for each stage of an examination. The proposals were developed by a task force comprised [...]]]></description>
			<content:encoded><![CDATA[<p></p><p><span style="font-size: small;">The USPTO has unveiled a series of proposals that would bring significant change to the examiner “count system” – the methodology for determining the time a patent examiner has to complete a patent examination and how much credit is given for each stage of an examination. The proposals were developed by a task force comprised of senior USPTO patent managers and representatives of the Patent Office Professional Association (POPA), the union that represents patent examiners.</span></p>
<p><span style="font-size: small;">The proposed changes would be the most significant in more than 30 years. The last revision to the count system was in 1976.</span></p>
<p><span style="font-size: small;">According to the USPTO, the proposals provide the following:</span></p>
<ul> <span style="font-size: x-small;"></p>
<li><strong>Improved working conditions:</strong> While the proposal increases the time examiners have overall, it provides incentives to encourage examiners to do a high-quality first action, and shifts resources from a focus on examiner recertification to front-end quality improvements. This change in incentives will ultimately encourage examiners to dispose of applications more quickly.</li>
<li><strong>More time for  examiners: </strong>The proposed changes will give examiners more time overall, more time for a first action on the merits, and time for examiner-initiated interviews, while decreasing credits on requests for continued examination (RCEs)* and providing consistent credits for transferred or inherited amendments.</li>
<li><strong>Process changes</strong>:  These changes will increase work credit certainty for examiners, increase fairness to applicants, and balance the load on IT systems.</li>
<p></span></ul>
<p><span style="font-size: small;">The USPTO&#8217;s press release on the proposed changes can be found <a href="http://www.uspto.gov/web/offices/com/speeches/09-19.htm" target="_blank">here</a>.</span></p>
<p><span style="font-size: small;">The USPTO&#8217;s full proposal can be found <a href="http://www.uspto.gov/web/offices/ac/ahrpa/opa/documents/briefing_for_corps-final_draft-093009-external-jrb.pdf" target="_blank">here</a>.</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/09/30/uspto-joint-labor-management-task-force-proposes-significant-changes-to-examiner-count-system/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Post Bilski Prosecution Strategy – Can It Really Be This Simple?</title>
		<link>http://patentablydefined.com/2009/07/27/post-bilski-prosecution-strategy-%e2%80%93-can-it-really-be-this-simple/</link>
		<comments>http://patentablydefined.com/2009/07/27/post-bilski-prosecution-strategy-%e2%80%93-can-it-really-be-this-simple/#comments</comments>
		<pubDate>Mon, 27 Jul 2009 18:56:10 +0000</pubDate>
		<dc:creator>mike</dc:creator>
				<category><![CDATA[Prosecution Strategy]]></category>

		<guid isPermaLink="false">http://patentablydefined.com/?p=84</guid>
		<description><![CDATA[Post Bilski, only methods “tied to a particular machine or apparatus” or that “transform a particular article into a different state or thing” remain patent-eligible.  One option to satisfy this &#8220;machine-or-transformation test&#8221; is to define a method so that it is tied to a device. An efficient way to accomplish this is to tie a [...]]]></description>
			<content:encoded><![CDATA[<p></p><p><span style="font-size: small;">Post <em>Bilski</em>, only methods “tied to a particular machine or apparatus” or that “transform a particular article into a different state or thing” remain patent-eligible.  One option to satisfy this &#8220;machine-or-transformation test&#8221; is to define a method so that it is tied to a device.</span></p>
<p><span style="font-size: small;">An efficient way to accomplish this is to tie a single operation of the </span><span style="font-size: small;">claimed </span><span style="font-size: small;">method to a device.  And, according to the BPAI, in the case of a computerized method, this may be accomplished merely by reciting the output of a solution from the system.  That’s right.  In <a href="http://des.uspto.gov/Foia/ReterivePdf?system=BPAI&amp;flNm=fd2009001172-07-09-2009-1" target="_blank">Ex Parte Dickerson</a>, a final decision issued by the Board earlier this month, a § 101 rejection of the following claim was reversed:</span></p>
<blockquote><p><span style="font-size: small;">23. A computerized method for identifying a solution to address exposed performance gaps of a company in a specific industry, comprising:</span></p>
<p><span style="font-size: small;">first identifying a plurality of operational metrics for the specific industry, wherein the operational metrics includes a factor used to measure health or viability of a generic company in the specific industry, wherein the specific industry is a grocery store industry, wherein the operational metrics include at least one of a rate of inventory turnover and a number of customers per day;<br />
assembling a set of solutions for application by the specific industry, wherein the set includes one of a decision, an action, a product, and a service;</span></p>
<p><span style="font-size: small;">assessing impacts of application of the set of solutions on the operational metrics for the specific industry, wherein the assessing includes determining which of the set of solutions has a negative impact on an operational metric and determining which of the set of solutions has a positive impact on the operational metric;</span></p>
<p><span style="font-size: small;">after identifying, assembling, and assessing, then comparing a current operational performance of the company to an operational performance of another company within the specific industry to obtain at least one performance gap, wherein the operational performance includes a performance of a company based upon the operational metric for the specific industry;</span></p>
<p><span style="font-size: small;">identifying a solution based upon the impacts to address the exposed performance gaps, wherein the solution is at least one of a decision, an action, a product, and a service that impacts a problem in a positive manner; and</span></p>
<p><span style="font-size: small;"><em><strong>outputting the solution from the computer system.</strong></em></span></p></blockquote>
<p><span style="font-size: small;">The Board&#8217;s rationale:</span></p>
<blockquote><p><span style="font-size: small;">“We find that claims 23, 29 and 30 a computerized method which includes a step of outputting information from a computer (FF 7 and 9-10) and therefore, are tied to a particular machine or apparatus.”</span></p></blockquote>
<p><span style="font-size: medium;"><span style="color: orange;">My question to you, the readers of this blog, is could satisfying § 101 be this simple?  And, if not, what other strategies have you found effective?  Please leave a comment if you have a successful strategy to share in a follow up post.<br />
</span></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/07/27/post-bilski-prosecution-strategy-%e2%80%93-can-it-really-be-this-simple/feed/</wfw:commentRss>
		<slash:comments>10</slash:comments>
		</item>
		<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>A Few Useful Sections Of The Manual Of Patent Examining Procedure</title>
		<link>http://patentablydefined.com/2009/05/29/a-few-useful-sections-of-the-manual-of-patent-examining-procedure/</link>
		<comments>http://patentablydefined.com/2009/05/29/a-few-useful-sections-of-the-manual-of-patent-examining-procedure/#comments</comments>
		<pubDate>Fri, 29 May 2009 12:07:08 +0000</pubDate>
		<dc:creator>mike</dc:creator>
				<category><![CDATA[Prosecution Strategy]]></category>
		<category><![CDATA[The MPEP]]></category>

		<guid isPermaLink="false">http://patentablydefined.com/?p=75</guid>
		<description><![CDATA[As regular readers of this blog know, I advocate using the USPTO’s Manual of Patent Examining Procedure (MPEP) as primary authority during prosecution.  I discussed my reasons for doing so in this earlier post.  Basically, it is the USPTO’s official manual, so its instructions to Examiners are beyond dispute. From time to time, when responding [...]]]></description>
			<content:encoded><![CDATA[<p></p><p><span style="font-size: small;">As regular readers of this blog know, I advocate using the USPTO’s Manual of Patent Examining Procedure (MPEP) as primary authority during prosecution.  I discussed my reasons for doing so in this <a href="http://patentablydefined.com/?p=34" target="_blank">earlier post</a>.  Basically, it is the USPTO’s official manual, so its instructions to Examiners are beyond dispute.</span></p>
<p><span style="font-size: small;">From time to time, when responding to an Office action or preparing a post for this blog, I come across interesting, useful MPEP sections that I think that other practitioners may not know about.   Admittedly, these sections are not useful in everyday prosecution.  Nonetheless, in certain, specific circumstances, these sections of the MPEP may be helpful.</span></p>
<p><span style="font-size: small;"><span style="text-decoration: underline;"><strong>Some help for older applications</strong></span><br />
Often, the prosecution of an application extends into third Office actions.  In these cases, as well as “mature” cases, take note of <a href="http://www.uspto.gov/web/offices/pac/mpep/documents/0700_707_02.htm" target="_blank">§707.02</a> of the MPEP.</span></p>
<blockquote><p><span style="font-size: small;"><strong>707.02 Applications Up for Third Action and 5-Year Applications </strong><br />
The supervisory patent examiners should impress their assistants with the fact that the shortest path to the final disposition of an application is by finding the best references on the first search and carefully applying them.</span></p>
<p><span style="font-size: small;">The supervisory patent examiners are expected to personally check on the pendency of every application which is up for the third or subsequent Office action with a view to finally concluding its prosecution.</span></p>
<p><span style="font-size: small;">Any application that has been pending five years should be carefully studied by the supervisory patent examiner and every effort should be made to terminate its prosecution. In order to accomplish this result, the application is to be considered &#8220;special&#8221; by the examiner.</span></p></blockquote>
<p><span style="font-size: small;"><span style="text-decoration: underline;"><strong>Some help for a generic rejection of a group of claims</strong></span><br />
We have all seen rejections in which an Examiner has erroneously characterized several independent claims, grouped them together, and generically rejected the group.  In situations like this in which an Examiner has grouped claims together to make a generic, omnibus rejection, <a href="http://www.uspto.gov/web/offices/pac/mpep/documents/0700_707_07_d.htm" target="_blank">§707.07(d)</a> of the MPEP may be of interest.  That section warns:</span></p>
<blockquote><p><span style="font-size: small;"><strong>707.07(d) Language to be Used in Rejecting Claims</strong></span></p>
<p><span style="font-size: small;">*****</span></p>
<p><span style="font-size: small;">A plurality of claims should never be grouped together in a common rejection, unless that rejection is equally applicable to all claims in the group.</span></p></blockquote>
<p><span style="font-size: small;"><span style="text-decoration: underline;"><strong>Some help for inventor filed (pro se) applications</strong></span><br />
The MPEP expressly instructs Examiners to offer specific help to <em>pro se</em> applicants by writing proposed claims.  If you are a <em>pro se </em>applicant, keep <a href="http://www.uspto.gov/web/offices/pac/mpep/documents/0700_707_07_j.htm" target="_blank">§707.07(j)</a> in mind.<br />
</span></p>
<blockquote><p><span style="font-size: small;"><strong>707.07(j)(I) State When Claims Are Allowable </strong></span></p>
<p><span style="font-size: small;">When, during the examination of a <em>pro se</em> application it becomes apparent to the examiner that there is patentable subject matter disclosed in the application, the examiner should draft one or more claims for the applicant and indicate in his or her action that such claims would be allowed if incorporated in the application by amendment.</span></p></blockquote>
<p><span style="font-size: small;">Coming Next &#8211; More Help from the MPEP</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/05/29/a-few-useful-sections-of-the-manual-of-patent-examining-procedure/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
		<item>
		<title>Application Data Sheets And How They Help</title>
		<link>http://patentablydefined.com/2009/05/15/application-data-sheets-and-how-they-help/</link>
		<comments>http://patentablydefined.com/2009/05/15/application-data-sheets-and-how-they-help/#comments</comments>
		<pubDate>Fri, 15 May 2009 23:44:56 +0000</pubDate>
		<dc:creator>mike</dc:creator>
				<category><![CDATA[Practice Suggestions]]></category>
		<category><![CDATA[Prosecution Strategy]]></category>
		<category><![CDATA[The MPEP]]></category>

		<guid isPermaLink="false">http://patentablydefined.com/?p=74</guid>
		<description><![CDATA[An application data sheet (ADS) is a document that provides the bibliographic data for an application to the USPTO.  The USPTO prefers, but does not require, the use of an ADS.  An ADS can be advantageous, however, because it tends to reduce errors in the conversion/recordation of application data into the  USPTO’s official electronic  data [...]]]></description>
			<content:encoded><![CDATA[<p></p><p><span style="font-size: small;">An application data sheet (ADS) is a document that provides the bibliographic data for an application to the USPTO.  The USPTO prefers, but does not require, the use of an ADS.  An ADS can be advantageous, however, because it tends to reduce errors in the conversion/recordation of application data into the  USPTO’s official electronic  data record.  While electronic filing via the USPTO’s EFS-Web has certainly reduced some errors, the USPTO relies on the uploaded documents (e.g., declaration, specification), rather than a user’s input, to create its official electronic record.  For example, in a national stage application filed under 35 USC § 371, the USPTO might look to the publication of the international application for the title and to other documents for the listing of inventors and the correspondence address.   The use of an ADS, because it provides this information in a single document and in a specified format, improves the accuracy of this conversion and the resulting electronic record.</span></p>
<p><span style="font-size: small;"><strong><span style="text-decoration: underline;">Examples of What Can Happen Without an ADS</span></strong><br />
The USPTO’s procedures for converting the application data of paper applications and for recording electronic data into its official data record are surprisingly accurate, in view of the number of application data records it must create.  Nonetheless, as with any system, errors do occur.  And, even when they are remedied early in the prosecution process, they still take time and can cause processing delays.  Worse yet, sometimes errors in the USPTO data records are not corrected.  Consider the following U.S. patents, which could have benefited from an ADS:</span></p>
<ol> <span style="font-size: small;"></p>
<li> U.S. Patent Nos. <a href="http://www.google.com/patents?id=aysDAAAAEBAJ&amp;dq=6,112,451" target="_blank">6,112,451</a>, <a href="http://www.google.com/patents?id=eFsOAAAAEBAJ&amp;dq=6,631,400" target="_blank">6,631,400</a>, and <a href="http://www.google.com/patents?id=apUMAAAAEBAJ&amp;dq=6,637,044" target="_blank">6,637,044</a>, each for a “Statement Regarding Federally Sponsored Research or Development”;</li>
<li> U.S. Patent No. <a href="http://www.google.com/patents?id=02mBAAAAEBAJ&amp;dq=7,263,562" target="_blank">7,263,562</a> for a “Method and System for Describing Uploaded Files Statement Regarding Federally Sponsored Research or Development”; and</li>
<li> U.S. Patent No. <a href="http://www.google.com/patents?id=KcoLAAAAEBAJ&amp;dq=6,389,215" target="_blank">6,389,215</a> for “Low Birefringent Polyimides for Optical Waveguides Statement Regarding Federally Sponsored Research or Development”.</li>
<p></span></ol>
<p><span style="font-size: small;">And then there are:</span></p>
<ol> <span style="font-size: small;"></p>
<li> U.S. Patent No. <a href="http://www.google.com/patents?id=isIUAAAAEBAJ&amp;dq=6,930,045" target="_blank">6,930,045</a> for “Cross Reference to Related Application”;</li>
<li> U.S. Patent No. <a href="http://www.google.com/patents?id=wEESAAAAEBAJ&amp;dq=6,829,526" target="_blank">6,829,526</a> for a “Train Detection System and a Train Detection Method Cross Reference to Related Application”; and</li>
<li> U.S. Patent No.  <a href="http://www.google.com/patents?id=SsMQAAAAEBAJ&amp;dq=6,786,734" target="_blank">6,786,734</a> for an “Electrical Adapter With a Foldable Housing Cross-Reference to Related Application”.</li>
<p></span></ol>
<p><span style="font-size: small;">Clearly, there are instances when an ADS would have helped the USPTO more accurately convert bibliographic information into an official data record.</span></p>
<p><span style="font-size: small;"><strong><span style="text-decoration: underline;">The Requirements for an ADS</span></strong><br />
<a href="http://www.uspto.gov/web/offices/pac/mpep/documents/appxr_1_76.htm" target="_blank">37 CFR § 1.76</a> governs application data sheets and sets forth specific requirements for each ADS.  The following are some of the more noteworthy.</span></p>
<blockquote><p><span style="font-size: small;">1.  An ADS may be used in provisional and nonprovisional applications.  37 CFR § 1.37(a).</span></p></blockquote>
<blockquote><p><span style="font-size: small;"> 2.  The USPTO offers a fillable pdf form (Form PTO/SB/14) on its website <a href="http://www.uspto.gov/web/forms/index.html#patent" target="_blank">here</a>.  <strong>CAUTION</strong> &#8211; The USPTO ADS fillable form must be submitted as a text-based PDF file. A scanned version of the ADS fillable form will be rejected via EFS-Web because EFS-Web will not be able to auto-load scanned in data into backend systems.   (Answer to <a href="http://www.uspto.gov/main/faq/p220efs252.htm" target="_blank">USPTO.GOV EFS-Web Help FAQ # 252</a>).</span></p></blockquote>
<blockquote><p><span style="font-size: small;"> 3.  An ADS must be in a specific format.  An ADS must be titled &#8220;Application Data Sheet&#8221; and must contain all of the following section headings, with any appropriate data for each section heading:</span></p>
<ol> <span style="font-size: x-small;"></p>
<li> Applicant information (i.e., the name, residence, mailing address, and citizenship of each applicant);</li>
<li> Correspondence information (i.e., the correspondence address, which may be indicated by reference to a customer number);</li>
<li> Application information (i.e., the title of the invention, a suggested classification, by class and subclass, the Technology Center to which the subject matter of the invention is assigned, the total number of drawing sheets, any docket number assigned to the application, the type of application);</li>
<li> Representative information (i.e., the registration number of each practitioner having a power of attorney in the application);</li>
<li> Domestic priority information (i.e., the application number, the filing date, the status, and relationship of each application for which a benefit is claimed under 35 U.S.C. 119(e), 120, 121, or 365(c));</li>
<li> Foreign priority information (i.e., the application number, country, and filing date of each foreign application for which priority is claimed) (NOTE &#8211; providing this information in the application data sheet constitutes the claim for priority as required by 35 U.S.C. 119(b) and § 1.55(a); and</li>
<li> Assignee information.</li>
<p></span></ol>
<p><span style="font-size: small;">37 CFR §§ 1.76 (a) and (b).</span></p></blockquote>
<blockquote><p><span style="font-size: small;">4.  Providing domestic priority information in an ADS constitutes the specific reference required by 35 USC § 119(e) or 120, and 37 CFR §§ 1.78(a)(2) or 1.78(a)(5), such that this information need not otherwise be made part of the specification.  37 CFR 1.76 (b)(5).<a href="http://www.uspto.gov/web/offices/pac/mpep/documents/0600_601_05.htm" target="_blank"> </a></span></p></blockquote>
<blockquote><p><span style="font-size: small;"> 5.  The USPTO will interpret any blank section in an ADS to mean that there is no corresponding data for that label anywhere in the application.  37 CFR § 1.76(a).</span></p></blockquote>
<blockquote><p><span style="font-size: small;"> 6.  In the event of an inconsistency between the ADS and other submitted documents, the timing of the submission of the conflicting information controls.</span></p>
<ul> <span style="font-size: x-small;"></p>
<li><em>When the conflicting information is submitted at different times</em> &#8211; the latest submitted information governs regardless of how it is supplied, except that an oath or declaration governs inconsistencies in the naming of inventors or their citizenship.</li>
<li><em> When the conflicting information is submitted at the same time</em> &#8211; the ADS will govern when the inconsistent information is supplied at the same time, except that an oath or declaration governs inconsistencies in the naming of inventors or their citizenship.</li>
<p></span></ul>
<p><span style="font-size: small;">37 CFR 1.76 (d)</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>
<p><span id="more-74"></span><!--more--><!--more--></p>
]]></content:encoded>
			<wfw:commentRss>http://patentablydefined.com/2009/05/15/application-data-sheets-and-how-they-help/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
		<item>
		<title>Exercise Care When Selecting International Searching Authorities</title>
		<link>http://patentablydefined.com/2009/03/19/exercise-care-when-selecting-international-searching-authorities/</link>
		<comments>http://patentablydefined.com/2009/03/19/exercise-care-when-selecting-international-searching-authorities/#comments</comments>
		<pubDate>Thu, 19 Mar 2009 18:56:02 +0000</pubDate>
		<dc:creator>mike</dc:creator>
				<category><![CDATA[Practice Suggestions]]></category>
		<category><![CDATA[Prosecution Strategy]]></category>

		<guid isPermaLink="false">http://patentablydefined.com/?p=71</guid>
		<description><![CDATA[The USPTO recently published a Notice to applicants filing applications under the PCT in the United States Receiving Office (RO/US) to exercise care in selecting a competent International Searching Authority (ISA) for claimed subject matter.  The USPTO reminds applicants that:  (1)  the EPO will not act as an ISA/IPEA for applications with one or more [...]]]></description>
			<content:encoded><![CDATA[<p></p><p><span style="font-size: small;">The USPTO recently published a <a href="http://www.uspto.gov/web/offices/pac/dapps/pct/ann.htm">Notice</a> to applicants filing applications under the PCT in the United States Receiving Office (RO/US) to exercise care in selecting a competent International Searching Authority (ISA) for claimed subject matter.  The USPTO reminds applicants that:  (1)  the EPO will not act as an ISA/IPEA for applications with one or more business method claims; and (2)  the AU-IPO will not act as an ISA/IPEA for applications with one or more claims drawn to certain fields of technology specified in Annex A of the Arrangement between IP Australia and the United States Patent and Trademark Office, which was published in the USPTO’s Official Gazette at 1337 OG 263.</span></p>
<p><span style="font-size: small;">From the USPTO’s website &#8230;</span></p>
<blockquote><p><span style="font-size: small;"><strong>Limited Competency of Certain International Searching<br />
Authorities With Respect to Applications Filed in the USPTO</strong></span></p>
<p><span style="font-size: small;">The USPTO has noticed a significant number of international applications filed in the United States receiving Office (RO/US) under the Patent Cooperation Treaty (PCT) where the applicant has chosen an International Searching Authority (ISA) which is not competent for the subject matter of the claimed invention.  This can result in significant delays in the issuance of the International Search Report and Written Opinion of the International Searching Authority.  When such an application is filed it is forwarded by the RO/US to the ISA selected by applicant.  After processing the application, the ISA will return the application to the RO/US with an indication that it is drawn to subject matter for which the ISA is not competent to act. The RO/US will then notify applicant of such and invite applicant to select a competent ISA.  Once the RO/US receives a new indication from applicant as to a new ISA, the RO/US will forward the application to the newly selected ISA where it will undergo further processing and will eventually receive a search in accordance with Chapter I of the PCT.</span></p>
<p><span style="font-size: small;">Applicants are hereby reminded that certain ISAs have limited their competency for applications filed with the RO/US.  Specifically, the European Patent Office (EPO) will not act as an ISA/IPEA for applications with one or more claims to a business method (citation omitted).  Further, the Australian Patent Office (IP Australia) has declared that it is not competent for applications with one or more claims drawn to subject matter set forth in Annex A of the Arrangement between IP Australia and the United States Patent and Trademark Office (see 1337 OG 263).  To avoid significant processing delays, applicants filing international applications naming either the EPO or IP Australia as the ISA should take care to ensure that the application does not contain any claims for which the selected ISA is not competent.</span></p></blockquote>
<p><span style="font-size: small;">The relevant portion of Annex A is reproduced below.</span></p>
<blockquote><p><span style="font-size: small;"><strong>Annex A of the Arrangement between IP Australia and the USPTO</strong></span></p>
<p><span style="font-size: small;">Subject matter for which the Australian Patent Office is NOT a competent International Search Authority or International Preliminary Examination Authority for international applications filed with the RO/US by International Patent Classification (8th edition):</span></p>
<p><span style="font-size: small;">A01-AGRICULTURE; FORESTRY; ANIMAL HUSBANDRY; HUNTING; TRAPPING; FISHING, all classes except:  A01H, A01N, A01P(i.e. new plants or processes of obtaining them thereof, Preservation of human, animals bodies or plants, biocidal, pest repellent, pest attractant or plant growth regulatory activity of chemical compounds or preparations)<br />
A21-BAKING; EQUIPMENT FOR MAKING OR PROCESSING DOUGHS; DOUGHS FOR BAKING all classes except:  A21D, (i.e. Treatment of flour or dough for baking)<br />
A22-BUTCHERING; MEAT TREATMENT; PROCESSING POULTRY OR FISH<br />
A23N-MACHINES OR APPARATUS FOR TREATING HARVESTED FRUIT, VEGETABLES OR FLOWER BULBS IN BULK<br />
A23P-SHAPING OR WORKING OF FOODSTUFFS<br />
A24-TOBACCO; CIGARS; CIGARETTES<br />
A41-47 PERSONAL AND DOMESTIC ARTICLES (eg. headgear (A42), footwear(A43),<br />
haberdashery (A44))<br />
A61-MEDICAL OR VETERINARY SCIENCE, all classes except:  A61K, A61L, A61P and A61Q (i.e. preparations for medical, dental or toilet purposes, methods, apparatus for sterilising materials or objects, chemical aspects of bandages, dressings, absorbent pads, or surgical articles, therapeutic activity of chemical compounds, use of cosmetics or similar toilet preparations)<br />
A62-LIFE-SAVING all classes except:  A62D (i.e. chemical means for extinguishing fires, processes for making harmful chemical substances harmless, or less harmful, by effecting a chemical change, composition of materials for coverings or clothing for protecting against harmful chemical agents; composition of materials for transparent parts of gas-masks, respirators, breathing bags or helmets; composition of chemical materials for use in breathing apparatus)<br />
A63-SPORTS; GAMES; AMUSEMENTS</span></p>
<p><span style="font-size: small;">B06-GENERATING OR TRANSMITTING MECHANICAL VIBRATIONS IN GENERAL<br />
B21, B23-B27 all except: B23K (i.e. soldering or unsoldering; welding; cladding or plating by soldering or welding; cutting by applying heat locally, e.g. flame cutting; working by laser beam)<br />
B31-MAKING PAPER ARTICLE WORKING PAPER<br />
B60-B68 all except: B60L, B60M and B60Q (i.e. electric equipment or propulsion of electrically-propelled vehicles; magnetic suspension or levitation for vehicles; electrodynamic brake systems for vehicles, in general, power supply lines, or devices along rails, for electrically-propelled vehicles, arrangement of signalling or lighting devices, the mounting or supporting thereof or circuits therefor, for vehicles in general)</span></p>
<p><span style="font-size: small;">D01-D07 Textiles all except:  D06L, D06M, D06N,  D06P, D06Q (i.e. bleaching, treatment of fabrics, dyeing or printing textiles, decorating textiles)</span></p>
<p><span style="font-size: small;">E01-E06 FIXED CONSTRUCTION<br />
E21-EARTH OR ROCK DRILLING; MINING</span></p>
<p><span style="font-size: small;">F01-F04 MACHINES<br />
F15-F17 ENGINEERING ELEMENTS, ACTUATORS, STORAGE OR DISTRIBUTION OF GASES OR LIQUIDS<br />
F41-F42 WEAPONS, AMMUNITION</span></p>
<p><span style="font-size: small;">G04-HOR0LOGY<br />
GO6-COMPUTING; Calculating; Counting<br />
G10-MUSICAL INSTRUMENTS<br />
G11-INFORMATION STORAGE</span></p></blockquote>
<p><span style="font-size: small;">The UPSTO’s announcement can be read <a href="http://www.uspto.gov/web/offices/pac/dapps/pct/ann.htm" target="_blank">here</a>.</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/19/exercise-care-when-selecting-international-searching-authorities/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>An Interesting Perspective Of The USPTO From The Inside</title>
		<link>http://patentablydefined.com/2009/03/19/an-interesting-perspective-of-the-uspto-from-the-inside/</link>
		<comments>http://patentablydefined.com/2009/03/19/an-interesting-perspective-of-the-uspto-from-the-inside/#comments</comments>
		<pubDate>Thu, 19 Mar 2009 18:50:23 +0000</pubDate>
		<dc:creator>mike</dc:creator>
				<category><![CDATA[Prosecution Strategy]]></category>
		<category><![CDATA[Useful Information]]></category>

		<guid isPermaLink="false">http://patentablydefined.com/?p=72</guid>
		<description><![CDATA[Gene Quinn of IPWATCHDOG.COM has a troubling an interesting post about the USPTO from the inside.  For anyone curious as to why the allowance rate has dropped below 50% (it is presently at 42%), and why the quality of examination has declined so much in recent years, I recommend taking a few minutes to read [...]]]></description>
			<content:encoded><![CDATA[<p></p><p><span style="font-size: small;">Gene Quinn of <a href="http://www.ipwatchdog.com/" target="_blank">IPWATCHDOG.COM</a> has <span style="text-decoration: line-through;">a troubling</span> an interesting post about the USPTO from the inside.  For anyone curious as to why the allowance rate has dropped below 50% (it is presently at 42%), and why the quality of examination has declined so much in recent years, I recommend taking a few minutes to read Mr. Quinn&#8217;s post entitled &#8220;<a href="http://www.ipwatchdog.com/2009/03/16/prespective-of-an-anonymous-patent-examiner/id=2190/" target="_blank">Perspective of an Anonymous Patent Examiner</a>&#8220;.  A few nuggets from the anonymous Examiner:</span></p>
<blockquote><p><span style="font-size: small;"> <span style="line-height: 160%;">[The USPTO's] “reject, reject, reject now” policy is encouraged by management’s policy of issuing a written warning on an examiner’s permanent file for allowance error percentage above 10%. </span></span></p></blockquote>
<blockquote><p><span style="font-size: small;"> <span style="line-height: 160%;">Additionally, there is a lack of motivation to get cases allowed, because there is no incentive for the examiner to do the extra work required to arrive at claim language which can be allowed.</span></span></p></blockquote>
<p><span style="font-size: small;">Over the years, I too have heard many of the same views from multiple Examiners.  It is little wonder why morale at the USPTO is so low.  I leave you with Mr. Quinn&#8217;s final question from his post, which I second:</span></p>
<blockquote><p><span style="font-size: small;"><span style="line-height: 160%;">With so many Czars and hundreds of billions of dollars being thrown around Washington, DC, can’t we get just a little attention at the agency that is tasked with promoting the progress of science and useful arts?  I don’t think that is too much to ask for, is it?</span></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/03/19/an-interesting-perspective-of-the-uspto-from-the-inside/feed/</wfw:commentRss>
		<slash:comments>2</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>Examples Of Strategic Uses Of Requests For Continued Examination (RCEs)</title>
		<link>http://patentablydefined.com/2009/02/17/examples-of-strategic-uses-of-requests-for-continued-examination-rces/</link>
		<comments>http://patentablydefined.com/2009/02/17/examples-of-strategic-uses-of-requests-for-continued-examination-rces/#comments</comments>
		<pubDate>Tue, 17 Feb 2009 17:56:30 +0000</pubDate>
		<dc:creator>mike</dc:creator>
				<category><![CDATA[Practice Suggestions]]></category>
		<category><![CDATA[Prosecution Strategy]]></category>
		<category><![CDATA[Useful Information]]></category>

		<guid isPermaLink="false">http://patentablydefined.com/?p=67</guid>
		<description><![CDATA[This is the second part of a two-part discussion of RCEs and the submission requirement.  In my earlier post here, I discussed legal principles about RCEs and some RCE strategy.  This post presents and discusses some additional strategic uses for RCEs beyond reopening/continuing prosecution after a final Office action. An RCE can be used to [...]]]></description>
			<content:encoded><![CDATA[<p></p><p><span style="font-size: small;">This is the second part of a two-part discussion of RCEs and the submission requirement.  In my earlier post <a href="http://patentablydefined.com/?p=53" target="_blank">here</a>, I discussed legal principles about RCEs and some RCE strategy.  This post presents and discusses some additional strategic uses for RCEs beyond reopening/continuing prosecution after a final Office action.</span></p>
<blockquote><p><span style="font-size: small;"><strong>An RCE can be used to have art considered and made of record when the statement under 37 CFR § 1.97(e) is required but cannot properly be made.</strong></span></p>
<p><span style="font-size: small;">Consider a circumstance where an Applicant seeks to have art considered by the Office</span><span style="font-size: small;"> (i) after a final Office action and (ii) more than three months after the art was cited in a corresponding foreign application</span><span style="font-size: small;">.  If the Examiner declines to consider the art (the Rules do not prohibit the Examiner from considering art at any time during prosecution), filing an RCE with an IDS will require the USPTO to consider the art as a matter of right. </span></p>
<p><span style="font-size: small;">In this circumstance, the Applicant may consider foregoing a Response After Final and file an RCE with two submissions, a fully responsive Response and an IDS.</span></p></blockquote>
<p><span style="font-size: small;"><span style="text-decoration: underline;">Two Comments About RCEs and IDSs</span><br />
1.  Keep in mind that 37 CFR 1.97 specifies when an IDS <em><strong><span style="text-decoration: underline;">shall</span></strong></em> be considered by the Office.  Thus, compliance with this rule ensures consideration of submitted art as a matter of right.  A failure to satisfy the requirements of this rule <em><strong><span style="text-decoration: underline;">does not</span></strong></em> preclude the consideration of the cited art, just consideration as a matter of right.</span></p>
<p><span style="font-size: small;">2.  The three-month window of 37 CFR 1.53(b) (an IDS will be considered if filed within three months after the filing date) does not apply to RCE applications.  An IDS after an RCE will, however, be considered without a statement and fee so long as the IDS is filed before the first action after the RCE.</span></p>
<blockquote><p><span style="font-size: small;"><strong>An RCE can be used to withdraw an appeal.</strong></span></p>
<p><span style="font-size: small;">After a Notice of Appeal, an Applicant/Appellant sometimes (i) decides to amend claims or (ii) discovers new art that is material to patentabilty.  In either of these situations, filing an RCE would withdraw the appeal and reopen prosecution so that the amendments or art can be made of record.</span></p></blockquote>
<blockquote><p><span style="font-size: small;"><strong>An RCE can be used to withdraw an allowed application from issue.</strong></span></p>
<p><span style="font-size: small;">After a Notice of Allowance, but before payment of the Issue Fee, an Applicant begins to evaluate whether the claims are of adequate scope or whether additional claims are warranted.  If there is a risk of the application issuing, an RCE will stop it.  In this circumstance, filing an RCE with a submission that merely amends the Abstract to change as little as a single word can be used to buy the Applicant time to decide whether to permit the application to issue.</span></p></blockquote>
<blockquote><p><span style="font-size: small;"><strong>An RCE may also be used to avoid paying an Issue Fee but maintaining pendency  when it is unclear whether an Applicant wants to pay an Issue Fee. </strong></span></p>
<p><span style="font-size: small;">Here again, a submission that merely amends the Abstract to change as little as a single word can be used.</span></p></blockquote>
<p><span style="font-size: small;"><span style="text-decoration: underline;">A Comment on Reporting Issue Fees</span><br />
To avoid the latter situation illustrated above in which it is unclear whether the Applicant wants to pay the Issue Fee, one might consider a paragraph such as the following in a Notice of Allowance and Notice of Allowability reporting letter:</span></p>
<blockquote><p><span style="font-size: small;">The Issue Fee and Publication Fee are due no later than January 1, 2009, and we will pay those fees on the due date unless we receive your instructions otherwise.  In that regard, if you instruct us to file a request for continued examination (RCE), we must have your proposed amendment or other submission before the due date.</span></p></blockquote>
<p><span style="font-size: small;">Such a paragraph makes clear that the fees will be paid in the absence of further instructions.</span></p>
<p><span style="font-size: x-small;"><strong> </strong></span></p>
<p style="text-align: left;"><strong><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></strong></p>
<p style="text-align: center;"><span style="font-weight: normal;">© 2009, Michael E. Kondoudis</span></p>
<p style="text-align: center;"><strong><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></strong></p>
<p><strong> </strong><span style="font-size: small;"> </span><span style="font-size: small;"><br />
</span></p>
]]></content:encoded>
			<wfw:commentRss>http://patentablydefined.com/2009/02/17/examples-of-strategic-uses-of-requests-for-continued-examination-rces/feed/</wfw:commentRss>
		<slash:comments>3</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>An Applicant Knows More About Their Invention Than An Examiner – USPTO Director Jon Dudas</title>
		<link>http://patentablydefined.com/2008/07/16/an-applicant-knows-more-about-their-invention-than-an-examiner-%e2%80%93-uspto-director-jon-dudas/</link>
		<comments>http://patentablydefined.com/2008/07/16/an-applicant-knows-more-about-their-invention-than-an-examiner-%e2%80%93-uspto-director-jon-dudas/#comments</comments>
		<pubDate>Wed, 16 Jul 2008 16:38:42 +0000</pubDate>
		<dc:creator>mike</dc:creator>
				<category><![CDATA[Prosecution Strategy]]></category>

		<guid isPermaLink="false">http://patentablydefined.com/?p=52</guid>
		<description><![CDATA[The USPTO website has a new story about the inclusion of USPTO Director Jon Dudas in Managing Intellectual Property Magazine’s 2008 “Top 50 Most Influential People in IP.”  Apart from the merits of the story (forgive me, but I think it is self-evident that such a list would necessarily include the Director of the USPTO), [...]]]></description>
			<content:encoded><![CDATA[<p></p><p><span style="font-size: small;">The USPTO website has a new story about the inclusion of USPTO Director Jon Dudas in Managing Intellectual Property Magazine’s 2008 “Top 50 Most Influential People in IP.”  Apart from the merits of the story (forgive me, but I think it is self-evident that such a list would necessarily include the Director of the USPTO), I found a quote attributed to Mr. Dudas to be of particular interest.  On the alleged merits of requiring Applicants to undertake an art search and provide the Office with a search report as part of a “quality initiative,” </span><span style="font-size: small;">he stated:</span></p>
<p><em><span style="font-size: small;"><strong><span style="text-decoration: underline;">the applicant knows more about their invention that [sic] anyone else.</span></strong></span></em></p>
<p><span style="font-size: small;">There it is.  The Director of the USPTO has now acknowledged that </span><span style="font-size: small;">the balance of knowledge </span><span style="font-size: small;">in an application </span><span style="font-size: small;">weighs in an Applicant’s favor.  A creative patent prosecutor can envision any number of ways this admission might be usable in proceedings before the USPTO.  Just a thought.</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/07/16/an-applicant-knows-more-about-their-invention-than-an-examiner-%e2%80%93-uspto-director-jon-dudas/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>A Discussion Of Strategies To Address Successive Non-Final Office Actions That Are Not Advancing Prosecution</title>
		<link>http://patentablydefined.com/2008/07/01/a-discussion-of-strategies-to-address-successive-non-final-office-actions-that-are-not-advancing-prosecution/</link>
		<comments>http://patentablydefined.com/2008/07/01/a-discussion-of-strategies-to-address-successive-non-final-office-actions-that-are-not-advancing-prosecution/#comments</comments>
		<pubDate>Tue, 01 Jul 2008 00:44:29 +0000</pubDate>
		<dc:creator>mike</dc:creator>
				<category><![CDATA[Practice Suggestions]]></category>
		<category><![CDATA[Prosecution Strategy]]></category>
		<category><![CDATA[The MPEP]]></category>

		<guid isPermaLink="false">http://patentablydefined.com/?p=50</guid>
		<description><![CDATA[In an earlier post, I discussed the Office’s policy of compact prosecution and how that policy affects patent prosecution in the USPTO. Under that policy, second Office actions are usually made final, except in limited circumstances. Consequently, except for an allowance or an indication of allowable subject matter, a response that triggers a non-final Office [...]]]></description>
			<content:encoded><![CDATA[<p></p><p><span style="font-size: x-small;">In an earlier post, I discussed <a href="http://patentablydefined.com/?p=18" target="_blank">the Office’s policy of compact prosecution</a> and how that policy affects patent prosecution in the USPTO.  Under that policy, second Office actions are usually made final, except in limited circumstances. Consequently, except for an allowance or an indication of allowable subject matter, a response that triggers a non-final Office action is often the best result an Applicant can expect.  After all, forcing the Office to deviate from its policy of compact prosecution is usually evidence of effective patent prosecution, particularly when a non-final Office action is triggered without a claim amendment.</span></p>
<p><span style="font-size: x-small;"><span style="text-decoration: underline;"><strong>A Problem &#8211; Successive Non-Final Office Actions That Do Not Advance Prosecution</strong></span></span></p>
<p><span style="font-size: x-small;">In some cases, however, second, third, or fourth non-final Office actions are arguably the result of poor Office action quality rather than the quality of the patentability arguments.   These Office actions are problematic because they don’t advance an application or even provide practical measures of potential patentability, yet they require formal responses.   Thus, Applicants incur the expenses of responses without the benefit of advancing prosecution.</span></p>
<p><span style="font-size: x-small;">A common example of this circumstance is a first non-final Office action that applies poor art.   Sometimes, after an Applicant traverses the art rejections with patentability arguments and/or claim amendments that amount to no more than a rewrite of an original independent claim to incorporate an original dependent claim, the Applicant receives another non-final Office action (with new art) and the cycle is repeated.</span></p>
<p><span style="font-size: x-small;">This post addresses this atypical but vexing situation in which an Applicant is required to respond to successive non-final Office actions that aren’t advancing prosecution. </span><span style="font-size: x-small;">To be clear, this post is <strong>NOT</strong> intended to address all successive non-final Office Actions. Rather, this post discusses some suggestions for escaping the administrative &#8220;purgatory&#8221; of successive non-final Office Actions that do not advance prosecution.</span></p>
<p><span style="font-size: x-small;"><span style="text-decoration: underline;"><strong>By Design or the Result of <em>Ex Parte </em>Prosecution?</strong></span></span></p>
<p><span style="font-size: x-small;">Some practitioners, at least anecdotally, seem to be of the opinion that this could be an intentional practice by some art groups in the USPTO, intended to wear down applicants and get them to either: unduly limit their claims rather than seeking protection for the full scope of their inventions; or to abandon their cases.  Others are of the opinion that this is the result of the sometimes inefficient process of <em>ex parte</em> prosecution and that Examiners cannot allow claims that they believe to be unpatentable.</span></p>
<p><span style="font-size: x-small;"><strong><span style="text-decoration: underline;">Options to Consider</span></strong></span></p>
<p><span style="font-size: x-small;"><span style="text-decoration: underline;"><strong> 1.  Consider An Appeal</strong></span><br />
One option might be to appeal at least some of the rejections.  An applicant whose claim has been twice rejected may appeal, regardless of whether the claim is under a final rejection.  See <a href="http://www.uspto.gov/web/offices/pac/mpep/documents/1200_1204.htm" target="_blank">MPEP § 1204</a>.  So, if any claim has faced the same rejection two times, appeal is an option.</span></p>
<p><span style="font-size: x-small;"><span style="text-decoration: underline;"><strong>2.  Consider an Interview</strong></span><br />
An Examiner interview is almost always an effective tool to advance prosecution.  Sometimes an Examiner misses novel features of the claims or misunderstands a patentability argument.  An interview is opportunity to meet the Examiner and to refocus prosecution. </span></p>
<p><span style="font-size: x-small;"> <span style="text-decoration: underline;"><strong>3.  Remind the Examiner of The Office’s Instructions for Art Searches</strong></span><br />
The MPEP establishes guidelines for art searches and the goals of these searches.  For example, <a href="http://www.uspto.gov/web/offices/pac/mpep/documents/0900_904_02.htm" target="_blank">Section 904.02</a> of the MPEP, entitled General Search Guidelines, advises Examiners that:</span></p>
<ul><span style="font-size: x-small;"> The search [for citable art] should cover the claimed subject matter and should also cover the disclosed features which might reasonably be expected to be claimed.</span></ul>
<p><span style="font-size: x-small;">Further, <a href="http://www.uspto.gov/web/offices/pac/mpep/documents/0900_904_03.htm" target="_blank">Section 904.03</a> of the MPEP, entitled Conducting the Search, instructs that:</span></p>
<ul><span style="font-size: x-small;">It is a prerequisite to a speedy and just determination of the issues involved in the examination of an application that a careful and comprehensive search, commensurate with the limitations appearing in the most detailed claims in the case, be made in preparing the first action on the merits so that the second action on the merits can be made final or the application allowed with no further searching other than to update the original search.</span></ul>
<p><span style="font-size: x-small;">This section goes on to warn that:</span></p>
<ul><span style="font-size: x-small;">It is normally not enough that references be selected to meet only the terms of the claims alone, especially if only broad claims are presented; but <span style="text-decoration: underline;">the search should, insofar as possible, also cover all subject matter which the examiner reasonably anticipates might be incorporated into applicant&#8217;s amendment</span>.  In doing a complete search, the examiner should find and cite references that, while not needed for treating the claims, would be useful for forestalling the presentation of claims to other subject matter regarded by applicant as his or her invention, by showing that this other subject matter is old or obvious.</span></ul>
<p><span style="font-size: x-small;">(emphasis added).  Finally, Section 904 warns that the examiner should cite only the best discovered art.<br />
</span></p>
<p><span style="font-size: x-small;">If anyone else has other strategies or suggestions to address this circumstance, I invite you to share them with other readers in the comments section.</span></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/07/01/a-discussion-of-strategies-to-address-successive-non-final-office-actions-that-are-not-advancing-prosecution/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
	</channel>
</rss>
