<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Examples Of Responses To Enablement Rejections</title>
	<atom:link href="http://patentablydefined.com/2009/07/14/examples-of-responses-to-enablement-rejections/feed/" rel="self" type="application/rss+xml" />
	<link>http://patentablydefined.com/2009/07/14/examples-of-responses-to-enablement-rejections/</link>
	<description>A practical patent prosecution blog published by Michael Kondoudis</description>
	<lastBuildDate>Tue, 13 Jul 2010 12:07:52 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Quotidian Dude</title>
		<link>http://patentablydefined.com/2009/07/14/examples-of-responses-to-enablement-rejections/comment-page-1/#comment-4804</link>
		<dc:creator>Quotidian Dude</dc:creator>
		<pubDate>Thu, 23 Jul 2009 16:54:51 +0000</pubDate>
		<guid isPermaLink="false">http://patentablydefined.com/?p=79#comment-4804</guid>
		<description>Beautiful, Michael.  Thanks.

One dilemma I often face is whether to combine procedural and substantive arguments.  This is not just for 112  rejections.  

The examiner does not even come close to making a prima facie case for 102, 103, 112 -- no Wands analysis, no Graham/KSR analysis, conclusory inherency rejection, whatever -- and I traverse by explaining the problem, hopefully as well as your example 1.

Now, the temptation is to go on and argue, notwithstanding the fact that the burden hasn&#039;t shifted, why there is sufficient enablement or why the reference doesn&#039;t disclose half of the elements of the claim, etc.  This easily doubles the cost of the response, but hopefully, it will help cut off another rejection and make it clear to the examiner an appeal is certain.

Often, if I only attack the procedural errors, the examiner will tidy up the rejection and make it final.  That way he avoids addressing the substantive arguments unless I file an appeal, at which point he re-opens prosecution to prevent his mess from reaching the BPAI.</description>
		<content:encoded><![CDATA[<p>Beautiful, Michael.  Thanks.</p>
<p>One dilemma I often face is whether to combine procedural and substantive arguments.  This is not just for 112  rejections.  </p>
<p>The examiner does not even come close to making a prima facie case for 102, 103, 112 &#8212; no Wands analysis, no Graham/KSR analysis, conclusory inherency rejection, whatever &#8212; and I traverse by explaining the problem, hopefully as well as your example 1.</p>
<p>Now, the temptation is to go on and argue, notwithstanding the fact that the burden hasn&#8217;t shifted, why there is sufficient enablement or why the reference doesn&#8217;t disclose half of the elements of the claim, etc.  This easily doubles the cost of the response, but hopefully, it will help cut off another rejection and make it clear to the examiner an appeal is certain.</p>
<p>Often, if I only attack the procedural errors, the examiner will tidy up the rejection and make it final.  That way he avoids addressing the substantive arguments unless I file an appeal, at which point he re-opens prosecution to prevent his mess from reaching the BPAI.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://patentablydefined.com/2009/07/14/examples-of-responses-to-enablement-rejections/comment-page-1/#comment-4803</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Thu, 23 Jul 2009 16:48:59 +0000</pubDate>
		<guid isPermaLink="false">http://patentablydefined.com/?p=79#comment-4803</guid>
		<description>Beautiful, Michael.  Thanks.

One dilemma I often face is whether to combine procedural and substantive arguments.  This is not just for 112  rejections.  

The examiner does not even come close to making a prima facie case for 102, 103, 112, whatever, and I traverse by explaining the problem, hopefully as well as your example 1.

Now, the temptation is to go on and argue, notwithstanding the fact that the burden hasn&#039;t shifted, why there is sufficient enablement or why the reference doesn&#039;t disclose half of the elements of the claim.  Hopefully, it will help cut off another rejection or set the stage for the appeal.

Often, if I only attack the procedural errors, the examiner will tidy up the rejection and make it final.  That way he avoids addressing the substantive arguments unless I file an appeal, at which point he re-opens prosecution to prevent his mess from reaching the BPAI.</description>
		<content:encoded><![CDATA[<p>Beautiful, Michael.  Thanks.</p>
<p>One dilemma I often face is whether to combine procedural and substantive arguments.  This is not just for 112  rejections.  </p>
<p>The examiner does not even come close to making a prima facie case for 102, 103, 112, whatever, and I traverse by explaining the problem, hopefully as well as your example 1.</p>
<p>Now, the temptation is to go on and argue, notwithstanding the fact that the burden hasn&#8217;t shifted, why there is sufficient enablement or why the reference doesn&#8217;t disclose half of the elements of the claim.  Hopefully, it will help cut off another rejection or set the stage for the appeal.</p>
<p>Often, if I only attack the procedural errors, the examiner will tidy up the rejection and make it final.  That way he avoids addressing the substantive arguments unless I file an appeal, at which point he re-opens prosecution to prevent his mess from reaching the BPAI.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bob Sayre</title>
		<link>http://patentablydefined.com/2009/07/14/examples-of-responses-to-enablement-rejections/comment-page-1/#comment-4799</link>
		<dc:creator>Bob Sayre</dc:creator>
		<pubDate>Thu, 16 Jul 2009 13:06:39 +0000</pubDate>
		<guid isPermaLink="false">http://patentablydefined.com/?p=79#comment-4799</guid>
		<description>Good stuff, as always, Michael.</description>
		<content:encoded><![CDATA[<p>Good stuff, as always, Michael.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
