<?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 How To Respond To Written Description Rejections &#8211; The Fundamentals Of The Written Description Requirement And Strategies For Responding To Written Description Rejections – Part II</title>
	<atom:link href="http://patentablydefined.com/2008/02/27/examples-of-how-to-respond-to-written-description-rejections-the-fundamentals-of-the-written-description-requirement-and-strategies-for-responding-to-written-description-rejections-%e2%80%93-part-ii/feed/" rel="self" type="application/rss+xml" />
	<link>http://patentablydefined.com/2008/02/27/examples-of-how-to-respond-to-written-description-rejections-the-fundamentals-of-the-written-description-requirement-and-strategies-for-responding-to-written-description-rejections-%e2%80%93-part-ii/</link>
	<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: Lazarus Long</title>
		<link>http://patentablydefined.com/2008/02/27/examples-of-how-to-respond-to-written-description-rejections-the-fundamentals-of-the-written-description-requirement-and-strategies-for-responding-to-written-description-rejections-%e2%80%93-part-ii/comment-page-1/#comment-2276</link>
		<dc:creator>Lazarus Long</dc:creator>
		<pubDate>Sun, 09 Mar 2008 18:09:06 +0000</pubDate>
		<guid isPermaLink="false">http://patentablydefined.com/?p=40#comment-2276</guid>
		<description>Hyatt could not comply as he did not have any explanation for what he was claiming.  I have read not only the decisions, but the various claims &amp; specs.  What he tried to do is point out that word &quot;X&quot; is on page 52 and word &quot;Y&quot; is on page 319 and word &quot;Z&quot; is on page 519 therefore I support for the combination of XYZ.  The problem was that the only place he actually combined XYZ together in any way, shape or form was in claims that were filed years after the filing of the applications, and up to 2 decades after the effective filing date claimed.  Those are (some of) the facts behind the cases.

BTW, here I DO agree with JD&#039;s analysis as to how to properly rebut the 112, 1, written desc. rej.  Just point out where the elements are described in the manner claimed.

thanks,

LL</description>
		<content:encoded><![CDATA[<p>Hyatt could not comply as he did not have any explanation for what he was claiming.  I have read not only the decisions, but the various claims &amp; specs.  What he tried to do is point out that word &#8220;X&#8221; is on page 52 and word &#8220;Y&#8221; is on page 319 and word &#8220;Z&#8221; is on page 519 therefore I support for the combination of XYZ.  The problem was that the only place he actually combined XYZ together in any way, shape or form was in claims that were filed years after the filing of the applications, and up to 2 decades after the effective filing date claimed.  Those are (some of) the facts behind the cases.</p>
<p>BTW, here I DO agree with JD&#8217;s analysis as to how to properly rebut the 112, 1, written desc. rej.  Just point out where the elements are described in the manner claimed.</p>
<p>thanks,</p>
<p>LL</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JD</title>
		<link>http://patentablydefined.com/2008/02/27/examples-of-how-to-respond-to-written-description-rejections-the-fundamentals-of-the-written-description-requirement-and-strategies-for-responding-to-written-description-rejections-%e2%80%93-part-ii/comment-page-1/#comment-2251</link>
		<dc:creator>JD</dc:creator>
		<pubDate>Thu, 06 Mar 2008 14:35:28 +0000</pubDate>
		<guid isPermaLink="false">http://patentablydefined.com/?p=40#comment-2251</guid>
		<description>Michael,

One thing that should be considered is the 2007 case of Hyatt v. Dudas, involving &quot;legendary&quot; inventor Gilbert Hyatt. 

The Fed. Cir. basically ruled that the examiner can force an applicant to point out where in the spec a particular claim, or claim feature, is supported.  That is all the examiner has to do:  challenge the applicant.  And the burden will be shifted to applicant.

However, my reading of Hyatt (and I&#039;ll admit I haven&#039;t read it very recently, but I have read it a couple times, but sometimes it takes more readings for things to sink in) is that the applicant only has to point out &quot;where&quot; the written description support can be found in the spec.  Applicant does not have to explain &quot;how&quot; the claim is supported.  Of course, explaining &quot;where&quot; the support is may not always be that different from explaining &quot;how&quot; it is supported.

Once the applicant explains &quot;where&quot; it is, my reading of Hyatt is that the applicant has successfully shifted the burden back to the examiner.  But we&#039;ll see.

I&#039;m not sure if Hyatt v. Dudas has made it into the latest version of the MPEP (I don&#039;t have a paper copy of the latest version, and scrolling through pdf&#039;s on a monitor is so unsatisfying), but I&#039;m sure it will make its way in there eventually.  And I&#039;m sure many examiners will latch onto it pretty quick.

Mr. Hyatt was clearly tilting at windmills and did all of us in the patent bar a disservice.  Sometimes it&#039;s better to just comply.

Pick your battles wisely.

JD</description>
		<content:encoded><![CDATA[<p>Michael,</p>
<p>One thing that should be considered is the 2007 case of Hyatt v. Dudas, involving &#8220;legendary&#8221; inventor Gilbert Hyatt. </p>
<p>The Fed. Cir. basically ruled that the examiner can force an applicant to point out where in the spec a particular claim, or claim feature, is supported.  That is all the examiner has to do:  challenge the applicant.  And the burden will be shifted to applicant.</p>
<p>However, my reading of Hyatt (and I&#8217;ll admit I haven&#8217;t read it very recently, but I have read it a couple times, but sometimes it takes more readings for things to sink in) is that the applicant only has to point out &#8220;where&#8221; the written description support can be found in the spec.  Applicant does not have to explain &#8220;how&#8221; the claim is supported.  Of course, explaining &#8220;where&#8221; the support is may not always be that different from explaining &#8220;how&#8221; it is supported.</p>
<p>Once the applicant explains &#8220;where&#8221; it is, my reading of Hyatt is that the applicant has successfully shifted the burden back to the examiner.  But we&#8217;ll see.</p>
<p>I&#8217;m not sure if Hyatt v. Dudas has made it into the latest version of the MPEP (I don&#8217;t have a paper copy of the latest version, and scrolling through pdf&#8217;s on a monitor is so unsatisfying), but I&#8217;m sure it will make its way in there eventually.  And I&#8217;m sure many examiners will latch onto it pretty quick.</p>
<p>Mr. Hyatt was clearly tilting at windmills and did all of us in the patent bar a disservice.  Sometimes it&#8217;s better to just comply.</p>
<p>Pick your battles wisely.</p>
<p>JD</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mike</title>
		<link>http://patentablydefined.com/2008/02/27/examples-of-how-to-respond-to-written-description-rejections-the-fundamentals-of-the-written-description-requirement-and-strategies-for-responding-to-written-description-rejections-%e2%80%93-part-ii/comment-page-1/#comment-2243</link>
		<dc:creator>mike</dc:creator>
		<pubDate>Wed, 05 Mar 2008 14:53:37 +0000</pubDate>
		<guid isPermaLink="false">http://patentablydefined.com/?p=40#comment-2243</guid>
		<description>Robert,

Thank you for your compliment.  I am glad you find my blog of interest.

To answer your questions: no and no. 

Responses are not like IRAC essays, although that format is a useful guide when presenting a technical or legal argument.  Essays explore every aspect of a subject an author can think of.  The art or patent prosecution is the opposite.  That is, to be effective without damaging the case by saying or implying things that will limit the claims in future litigation and/or licensing.  This is where knowledge of the law, tactical experience, and mentoring come into play, and where pro se applicants are at an EXTREME disadvantage.  A skilled prosecutor handles a response (and the Examiner) with great care and respect.  Anyone can get an application allowed.  But, the scope of the protection (and thus value) is measured by the allowed claims and what was said about them during prosecution.  So, rather than blindly adhering to any one form like IRAC, it is important to stay flexible and to employ an appropriate strategy to effectively and efficiently communicate what an applicant wants to communicate AND NO MORE.

Patent prosecution is not form-based work.  The examples I provide are road maps or starting points.  Every response is different because every application is unique in content and the way it is examined.  Looking at the examples on my blog as form paragraphs ignores the dimensions of strategy behind them.  These dimensions are the sum of my experience and that of numerous elder prosecutors and litigators.  A perceptive prosecutor should be able to extrapolate from the strategies I explore and apply the underlying principles on which they are based to other situations, analogous or not.</description>
		<content:encoded><![CDATA[<p>Robert,</p>
<p>Thank you for your compliment.  I am glad you find my blog of interest.</p>
<p>To answer your questions: no and no. </p>
<p>Responses are not like IRAC essays, although that format is a useful guide when presenting a technical or legal argument.  Essays explore every aspect of a subject an author can think of.  The art or patent prosecution is the opposite.  That is, to be effective without damaging the case by saying or implying things that will limit the claims in future litigation and/or licensing.  This is where knowledge of the law, tactical experience, and mentoring come into play, and where pro se applicants are at an EXTREME disadvantage.  A skilled prosecutor handles a response (and the Examiner) with great care and respect.  Anyone can get an application allowed.  But, the scope of the protection (and thus value) is measured by the allowed claims and what was said about them during prosecution.  So, rather than blindly adhering to any one form like IRAC, it is important to stay flexible and to employ an appropriate strategy to effectively and efficiently communicate what an applicant wants to communicate AND NO MORE.</p>
<p>Patent prosecution is not form-based work.  The examples I provide are road maps or starting points.  Every response is different because every application is unique in content and the way it is examined.  Looking at the examples on my blog as form paragraphs ignores the dimensions of strategy behind them.  These dimensions are the sum of my experience and that of numerous elder prosecutors and litigators.  A perceptive prosecutor should be able to extrapolate from the strategies I explore and apply the underlying principles on which they are based to other situations, analogous or not.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert</title>
		<link>http://patentablydefined.com/2008/02/27/examples-of-how-to-respond-to-written-description-rejections-the-fundamentals-of-the-written-description-requirement-and-strategies-for-responding-to-written-description-rejections-%e2%80%93-part-ii/comment-page-1/#comment-2195</link>
		<dc:creator>Robert</dc:creator>
		<pubDate>Thu, 28 Feb 2008 19:46:50 +0000</pubDate>
		<guid isPermaLink="false">http://patentablydefined.com/?p=40#comment-2195</guid>
		<description>I read your blog frequently and I think you do a good job explaining certain aspects of patent prosecution (especially to new patent attorneys). Am I correct in noticing that essentially all responses to office actions are IRAC styled essays like in law school? Also, a lot of paragraphs here seem to be template paragraphs that just can be asserted or minimally changed to fit a certain situation? Is that true or do you rewrite the paragraphs? Thanks.</description>
		<content:encoded><![CDATA[<p>I read your blog frequently and I think you do a good job explaining certain aspects of patent prosecution (especially to new patent attorneys). Am I correct in noticing that essentially all responses to office actions are IRAC styled essays like in law school? Also, a lot of paragraphs here seem to be template paragraphs that just can be asserted or minimally changed to fit a certain situation? Is that true or do you rewrite the paragraphs? Thanks.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
