<?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: How To Respond To § 103 Obviousness Rejections Using The “All Elements Test” In View Of Recent Revisions To Section 2143.03 Of The Manual Of Patent Examining Procedure</title>
	<atom:link href="http://patentablydefined.com/2008/05/05/how-to-respond-to-%c2%a7-103-obviousness-rejections-using-the-%e2%80%9call-elements-test%e2%80%9d-in-view-of-recent-revisions-to-section-214303-of-the-manual-of-patent-examining-procedure/feed/" rel="self" type="application/rss+xml" />
	<link>http://patentablydefined.com/2008/05/05/how-to-respond-to-%c2%a7-103-obviousness-rejections-using-the-%e2%80%9call-elements-test%e2%80%9d-in-view-of-recent-revisions-to-section-214303-of-the-manual-of-patent-examining-procedure/</link>
	<description>A practical patent prosecution blog published by Michael Kondoudis</description>
	<lastBuildDate>Mon, 23 Apr 2012 10:38:57 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: confused SCOTUS</title>
		<link>http://patentablydefined.com/2008/05/05/how-to-respond-to-%c2%a7-103-obviousness-rejections-using-the-%e2%80%9call-elements-test%e2%80%9d-in-view-of-recent-revisions-to-section-214303-of-the-manual-of-patent-examining-procedure/comment-page-1/#comment-4731</link>
		<dc:creator>confused SCOTUS</dc:creator>
		<pubDate>Tue, 18 Nov 2008 08:46:18 +0000</pubDate>
		<guid isPermaLink="false">http://patentablydefined.com/?p=45#comment-4731</guid>
		<description>Actually, there is ample case law that suggests limitation and element can (and often are) used synonymously or at least in the sense that there is no meaningful difference between the two. See for example famous Festo 1999, &quot;The claim 1 &#039;limitation&#039; or &#039;element&#039; at issue in the Carroll patent is stated as follows...&quot; The important thing to remember is simply &quot;what are the differences between the claimed invention and the prior art&quot;, whether the differences are components or parts, or modifications or descriptions of those components or parts.</description>
		<content:encoded><![CDATA[<p>Actually, there is ample case law that suggests limitation and element can (and often are) used synonymously or at least in the sense that there is no meaningful difference between the two. See for example famous Festo 1999, &#8220;The claim 1 &#8216;limitation&#8217; or &#8216;element&#8217; at issue in the Carroll patent is stated as follows&#8230;&#8221; The important thing to remember is simply &#8220;what are the differences between the claimed invention and the prior art&#8221;, whether the differences are components or parts, or modifications or descriptions of those components or parts.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Babel Boy</title>
		<link>http://patentablydefined.com/2008/05/05/how-to-respond-to-%c2%a7-103-obviousness-rejections-using-the-%e2%80%9call-elements-test%e2%80%9d-in-view-of-recent-revisions-to-section-214303-of-the-manual-of-patent-examining-procedure/comment-page-1/#comment-2719</link>
		<dc:creator>Babel Boy</dc:creator>
		<pubDate>Mon, 26 May 2008 16:22:48 +0000</pubDate>
		<guid isPermaLink="false">http://patentablydefined.com/?p=45#comment-2719</guid>
		<description>Chris

Exactly.  If the S/ware is claimed as a method, then the analysis is what is a step and what is a limitation of the step. To reject the claim, the examiner has to find each step in the art and the totality of the steps obvious. 

But if the S/ware is claimed as &quot;. . .media containing instructions executable by a computer, said instructions including . . .&quot; then you&#039;re right, it&#039;s all limitations, which are subjective and open to off-the-cuff obviousness rejections by examiners and courts.</description>
		<content:encoded><![CDATA[<p>Chris</p>
<p>Exactly.  If the S/ware is claimed as a method, then the analysis is what is a step and what is a limitation of the step. To reject the claim, the examiner has to find each step in the art and the totality of the steps obvious. </p>
<p>But if the S/ware is claimed as &#8220;. . .media containing instructions executable by a computer, said instructions including . . .&#8221; then you&#8217;re right, it&#8217;s all limitations, which are subjective and open to off-the-cuff obviousness rejections by examiners and courts.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Christopher Paul Mitchell (Chris)</title>
		<link>http://patentablydefined.com/2008/05/05/how-to-respond-to-%c2%a7-103-obviousness-rejections-using-the-%e2%80%9call-elements-test%e2%80%9d-in-view-of-recent-revisions-to-section-214303-of-the-manual-of-patent-examining-procedure/comment-page-1/#comment-2714</link>
		<dc:creator>Christopher Paul Mitchell (Chris)</dc:creator>
		<pubDate>Mon, 26 May 2008 02:16:25 +0000</pubDate>
		<guid isPermaLink="false">http://patentablydefined.com/?p=45#comment-2714</guid>
		<description>Babel Boy - thank you for your well articulated response.  I now fully appreciate the distinctions noted.  However, I remain curious as to their source.  That is, while these categories are logical, I am curious as to the breadth of their recognition, not just in America, but the world over.  

Also, I remain curious as to their applicability in the software arts:  My thought is that most claim “elements” in software cases are in fact “limitations.”  That is, I wonder if a software claim “element” could ever exist.  If the answer is no, then that suggests to me that the distinctions may have limited applicability (e.g., perhaps only in the mechanical arts).  

Again, thank you for your response.    

--Chris</description>
		<content:encoded><![CDATA[<p>Babel Boy &#8211; thank you for your well articulated response.  I now fully appreciate the distinctions noted.  However, I remain curious as to their source.  That is, while these categories are logical, I am curious as to the breadth of their recognition, not just in America, but the world over.  </p>
<p>Also, I remain curious as to their applicability in the software arts:  My thought is that most claim “elements” in software cases are in fact “limitations.”  That is, I wonder if a software claim “element” could ever exist.  If the answer is no, then that suggests to me that the distinctions may have limited applicability (e.g., perhaps only in the mechanical arts).  </p>
<p>Again, thank you for your response.    </p>
<p>&#8211;Chris</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Babel Boy</title>
		<link>http://patentablydefined.com/2008/05/05/how-to-respond-to-%c2%a7-103-obviousness-rejections-using-the-%e2%80%9call-elements-test%e2%80%9d-in-view-of-recent-revisions-to-section-214303-of-the-manual-of-patent-examining-procedure/comment-page-1/#comment-2664</link>
		<dc:creator>Babel Boy</dc:creator>
		<pubDate>Fri, 23 May 2008 17:56:04 +0000</pubDate>
		<guid isPermaLink="false">http://patentablydefined.com/?p=45#comment-2664</guid>
		<description>Chris,

You are bang-on, buddy. Not even the big cases make the distinction.  In fact I cannot cite a case on obviousness where an element was at issue.  They all seem to be decided on limitations. 

In Graham there is a section heading: &quot;Obviousness of the Differences.&quot;  I think we all tend to lose touch with what it is that must be obvious.  It&#039;s the difference between the claim and the art.  If the art lacks an element, it very hard to conclude that there is no difference.  But gradations and significance of differences in limitations in claims and art can always be argued.

What was at issue in Graham?  Not the plow shank or the spring clamp.  It was the position of a bolt relative to a hinge plate.  Bolts and hinge plates are elements, but it was the placement -- the limitation -- that was held obvious. Although the case was entirely about limitations, the USSCt did not mention &quot;limitation&quot; once.

In Calamar, the sister case reported contemporaneously with Graham, the issue was also entirely about limitations -- the positions of a rib seal and over-cap on a sprayer. Here, the USSCt explicitly pointed out that these were obvious limitations. 

In the original obviousness case, Hotchkiss v. Greenwood, 1850, the issue was using porcelain instead of wood to make a doorknob.  Choice of material of manufacture would be a limitation.  No new elements were at issue.  [The dissent raised the issue of how the knob was attached as a point of novelty.]  

How about KSR?  No elements at issue.  What was at issue was the position of the sensor of the pedal movement.  

I don&#039;t know of any cases in which an element is argued as being obvious or non-obvious over existing art.  I don&#039;t know of any cases making a distinction.  Judges, examiners, and prosecutors lump elements, limitations, and functions all together.  I think this is a major defect in  our case law and sloppy analysis.</description>
		<content:encoded><![CDATA[<p>Chris,</p>
<p>You are bang-on, buddy. Not even the big cases make the distinction.  In fact I cannot cite a case on obviousness where an element was at issue.  They all seem to be decided on limitations. </p>
<p>In Graham there is a section heading: &#8220;Obviousness of the Differences.&#8221;  I think we all tend to lose touch with what it is that must be obvious.  It&#8217;s the difference between the claim and the art.  If the art lacks an element, it very hard to conclude that there is no difference.  But gradations and significance of differences in limitations in claims and art can always be argued.</p>
<p>What was at issue in Graham?  Not the plow shank or the spring clamp.  It was the position of a bolt relative to a hinge plate.  Bolts and hinge plates are elements, but it was the placement &#8212; the limitation &#8212; that was held obvious. Although the case was entirely about limitations, the USSCt did not mention &#8220;limitation&#8221; once.</p>
<p>In Calamar, the sister case reported contemporaneously with Graham, the issue was also entirely about limitations &#8212; the positions of a rib seal and over-cap on a sprayer. Here, the USSCt explicitly pointed out that these were obvious limitations. </p>
<p>In the original obviousness case, Hotchkiss v. Greenwood, 1850, the issue was using porcelain instead of wood to make a doorknob.  Choice of material of manufacture would be a limitation.  No new elements were at issue.  [The dissent raised the issue of how the knob was attached as a point of novelty.]  </p>
<p>How about KSR?  No elements at issue.  What was at issue was the position of the sensor of the pedal movement.  </p>
<p>I don&#8217;t know of any cases in which an element is argued as being obvious or non-obvious over existing art.  I don&#8217;t know of any cases making a distinction.  Judges, examiners, and prosecutors lump elements, limitations, and functions all together.  I think this is a major defect in  our case law and sloppy analysis.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Christopher Paul Mitchell (Chris)</title>
		<link>http://patentablydefined.com/2008/05/05/how-to-respond-to-%c2%a7-103-obviousness-rejections-using-the-%e2%80%9call-elements-test%e2%80%9d-in-view-of-recent-revisions-to-section-214303-of-the-manual-of-patent-examining-procedure/comment-page-1/#comment-2651</link>
		<dc:creator>Christopher Paul Mitchell (Chris)</dc:creator>
		<pubDate>Thu, 22 May 2008 18:52:55 +0000</pubDate>
		<guid isPermaLink="false">http://patentablydefined.com/?p=45#comment-2651</guid>
		<description>Babel Boy - can you point to a single case recognizing a distinction between a limitaiton and an element (or a feature, or whatever other term practitioners may use use (e.g., &quot;feature&quot;))?

--Chris</description>
		<content:encoded><![CDATA[<p>Babel Boy &#8211; can you point to a single case recognizing a distinction between a limitaiton and an element (or a feature, or whatever other term practitioners may use use (e.g., &#8220;feature&#8221;))?</p>
<p>&#8211;Chris</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Babel Boy</title>
		<link>http://patentablydefined.com/2008/05/05/how-to-respond-to-%c2%a7-103-obviousness-rejections-using-the-%e2%80%9call-elements-test%e2%80%9d-in-view-of-recent-revisions-to-section-214303-of-the-manual-of-patent-examining-procedure/comment-page-1/#comment-2644</link>
		<dc:creator>Babel Boy</dc:creator>
		<pubDate>Tue, 20 May 2008 16:49:17 +0000</pubDate>
		<guid isPermaLink="false">http://patentablydefined.com/?p=45#comment-2644</guid>
		<description>Itzhak

In an article of manufacture context, an element would be a physical component; grammatically, a noun.  A limitation would be an adjective or adjective phrase modifying the element.  &quot;A wheel, said wheel comprising a metal rim and a plurality of spokes.&quot;  &quot;Rim&quot; and &quot;spokes&quot; are elements, &quot;metal&quot; and &quot;plurality&quot; are limitations.  

&quot;Wherein&quot; phrases are almost always limitations even if they include structure because they modify other structure.  &quot;. . .wherein the spokes have brass collars&quot; would be a limitation.

It is clear that every single element AND limitation must be met by a single reference in a 102 rejection.  My point is, and it is by no means widely accepted, that every element (or an equivalent) must be met by the references in a 103 rejection, but the examiner has &quot;103 latitude&quot; to add claimed limitations that are not expressly disclosed by any cited reference, if those limitations are obvious to a PHOSITA-head.</description>
		<content:encoded><![CDATA[<p>Itzhak</p>
<p>In an article of manufacture context, an element would be a physical component; grammatically, a noun.  A limitation would be an adjective or adjective phrase modifying the element.  &#8220;A wheel, said wheel comprising a metal rim and a plurality of spokes.&#8221;  &#8220;Rim&#8221; and &#8220;spokes&#8221; are elements, &#8220;metal&#8221; and &#8220;plurality&#8221; are limitations.  </p>
<p>&#8220;Wherein&#8221; phrases are almost always limitations even if they include structure because they modify other structure.  &#8220;. . .wherein the spokes have brass collars&#8221; would be a limitation.</p>
<p>It is clear that every single element AND limitation must be met by a single reference in a 102 rejection.  My point is, and it is by no means widely accepted, that every element (or an equivalent) must be met by the references in a 103 rejection, but the examiner has &#8220;103 latitude&#8221; to add claimed limitations that are not expressly disclosed by any cited reference, if those limitations are obvious to a PHOSITA-head.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Itzhak Yogev</title>
		<link>http://patentablydefined.com/2008/05/05/how-to-respond-to-%c2%a7-103-obviousness-rejections-using-the-%e2%80%9call-elements-test%e2%80%9d-in-view-of-recent-revisions-to-section-214303-of-the-manual-of-patent-examining-procedure/comment-page-1/#comment-2639</link>
		<dc:creator>Itzhak Yogev</dc:creator>
		<pubDate>Sun, 18 May 2008 15:17:56 +0000</pubDate>
		<guid isPermaLink="false">http://patentablydefined.com/?p=45#comment-2639</guid>
		<description>MPEP changed considerably, apparantly in the last few days. It now includes all KSR, and some of 2143 was taken out. Babel Boy, what is the difference between limitation and element? If the claim reads &quot;a device having an element&quot; isn&#039;t it a limitation??</description>
		<content:encoded><![CDATA[<p>MPEP changed considerably, apparantly in the last few days. It now includes all KSR, and some of 2143 was taken out. Babel Boy, what is the difference between limitation and element? If the claim reads &#8220;a device having an element&#8221; isn&#8217;t it a limitation??</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Babel Boy</title>
		<link>http://patentablydefined.com/2008/05/05/how-to-respond-to-%c2%a7-103-obviousness-rejections-using-the-%e2%80%9call-elements-test%e2%80%9d-in-view-of-recent-revisions-to-section-214303-of-the-manual-of-patent-examining-procedure/comment-page-1/#comment-2582</link>
		<dc:creator>Babel Boy</dc:creator>
		<pubDate>Thu, 15 May 2008 18:02:59 +0000</pubDate>
		<guid isPermaLink="false">http://patentablydefined.com/?p=45#comment-2582</guid>
		<description>Michael, this point is insidious and really needs to be aired.  Thanks.  There has also been some discussion of it over at PatObv where New Attorney raised the issue on Feb14.08.

I believe one of the difficulties with all 103 issues is the failure to recognize a 3-way distinction between steps/elements v. limitations v. functions.  I call this a S/ELF analysis. 

MPEP 2141 now says that all claimed LIMITATIONS need not be present in the cited PA. MPEP does not say, nor did KSR, that all of the STEPS/ELEMENTS need not be met by the PA. Note, KSR was not about elements, it was about limitations.  The elements were all known; the manner of combining, which is a limitation, was at issue.

If the examiner cites art in a 103 rejection that does not disclose each of the claimed steps/elements (or an obvious substitute), it&#039;s a bad rejection.  It is not prima facie. I call this the All Elements Rule II to distinguish from the infringement all elements rule.

In contrast, the claimed limitations need not be expressly disclosed in the cited PA, they can be added on the grounds that they would be obvious to an PHOSITA-head.  I mean, this was what Graham was all about.

IOW, claim limitations are subject to being inserted into the PA by the examiner as obvious. But if the examiner does that, he must provide an explanation. Moreover, the examiner cannot supply elements/steps that are missing from the PA. [I admit I am struggling to cite case law to support this last proposition.  Please anybody help if you can.]

This is the basis for a single-reference 103 rejection -- one reference that discloses all of the claim elements but not all of the limitations will not work for a 102 rejection, because 102 requires both claimed steps/elements AND claimed limitations to be disclosed in a single reference.  But the same reference might work for a 103 rejection if the missing claimed LIMITATION is supplied by the examiner as being obvious.

Like you, Mr. Hull, and New Attorney have already noted, pre-KSR MPEP 2141 said clearly all claimed elements must be present in the 103 PA.  But I do not now see in the post-KSR MPEP (or in KSR itself) a statement that all elements must be present in the 103 references.  Nor do I see the contrary statement that all elements need not be present in the PA in a 103 rejection.  

However, 103 itself says the subject matter as a whole must be met by the PA, and I take that to mean each and every element and step.  

Interestingly, KSR was about limitations but does not have a single word about claim limitations. I think the justices, like many examiners and practitioners, don&#039;t appreciate that there may be legal distinctions between elements/steps and limitations for the purposes of 103 analysis.  I believe a S/ELF analysis is very helpful in drafting claims and evaluating rejections. 

Finally, anon is absolutely right.  Royka has been removed from the MPEP, a discussion of Leapfrog is found at 2143.01 of the lastest version of MPEP.  

Recall that buried in the new rules package now before the CAFC was a regulation that would have given the MPEP the authority of law in rejections.  What a chilling thought. . .

Sorry this is so long.</description>
		<content:encoded><![CDATA[<p>Michael, this point is insidious and really needs to be aired.  Thanks.  There has also been some discussion of it over at PatObv where New Attorney raised the issue on Feb14.08.</p>
<p>I believe one of the difficulties with all 103 issues is the failure to recognize a 3-way distinction between steps/elements v. limitations v. functions.  I call this a S/ELF analysis. </p>
<p>MPEP 2141 now says that all claimed LIMITATIONS need not be present in the cited PA. MPEP does not say, nor did KSR, that all of the STEPS/ELEMENTS need not be met by the PA. Note, KSR was not about elements, it was about limitations.  The elements were all known; the manner of combining, which is a limitation, was at issue.</p>
<p>If the examiner cites art in a 103 rejection that does not disclose each of the claimed steps/elements (or an obvious substitute), it&#8217;s a bad rejection.  It is not prima facie. I call this the All Elements Rule II to distinguish from the infringement all elements rule.</p>
<p>In contrast, the claimed limitations need not be expressly disclosed in the cited PA, they can be added on the grounds that they would be obvious to an PHOSITA-head.  I mean, this was what Graham was all about.</p>
<p>IOW, claim limitations are subject to being inserted into the PA by the examiner as obvious. But if the examiner does that, he must provide an explanation. Moreover, the examiner cannot supply elements/steps that are missing from the PA. [I admit I am struggling to cite case law to support this last proposition.  Please anybody help if you can.]</p>
<p>This is the basis for a single-reference 103 rejection &#8212; one reference that discloses all of the claim elements but not all of the limitations will not work for a 102 rejection, because 102 requires both claimed steps/elements AND claimed limitations to be disclosed in a single reference.  But the same reference might work for a 103 rejection if the missing claimed LIMITATION is supplied by the examiner as being obvious.</p>
<p>Like you, Mr. Hull, and New Attorney have already noted, pre-KSR MPEP 2141 said clearly all claimed elements must be present in the 103 PA.  But I do not now see in the post-KSR MPEP (or in KSR itself) a statement that all elements must be present in the 103 references.  Nor do I see the contrary statement that all elements need not be present in the PA in a 103 rejection.  </p>
<p>However, 103 itself says the subject matter as a whole must be met by the PA, and I take that to mean each and every element and step.  </p>
<p>Interestingly, KSR was about limitations but does not have a single word about claim limitations. I think the justices, like many examiners and practitioners, don&#8217;t appreciate that there may be legal distinctions between elements/steps and limitations for the purposes of 103 analysis.  I believe a S/ELF analysis is very helpful in drafting claims and evaluating rejections. </p>
<p>Finally, anon is absolutely right.  Royka has been removed from the MPEP, a discussion of Leapfrog is found at 2143.01 of the lastest version of MPEP.  </p>
<p>Recall that buried in the new rules package now before the CAFC was a regulation that would have given the MPEP the authority of law in rejections.  What a chilling thought. . .</p>
<p>Sorry this is so long.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: anon</title>
		<link>http://patentablydefined.com/2008/05/05/how-to-respond-to-%c2%a7-103-obviousness-rejections-using-the-%e2%80%9call-elements-test%e2%80%9d-in-view-of-recent-revisions-to-section-214303-of-the-manual-of-patent-examining-procedure/comment-page-1/#comment-2483</link>
		<dc:creator>anon</dc:creator>
		<pubDate>Mon, 05 May 2008 15:06:45 +0000</pubDate>
		<guid isPermaLink="false">http://patentablydefined.com/?p=45#comment-2483</guid>
		<description>I bet Royka was deleted from the MPEP because of Leapfrog v. Fisher-Price (Fed. Cir. 2007), where the omission of a claim limitation (a reader) in the prior art references didn&#039;t preclude a finding of obviousness.</description>
		<content:encoded><![CDATA[<p>I bet Royka was deleted from the MPEP because of Leapfrog v. Fisher-Price (Fed. Cir. 2007), where the omission of a claim limitation (a reader) in the prior art references didn&#8217;t preclude a finding of obviousness.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

