<?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: Q) 35 USC 101</title>
	<atom:link href="http://mypatentbar.com/2008/09/04/q-35-usc-101/feed/" rel="self" type="application/rss+xml" />
	<link>http://mypatentbar.com/2008/09/04/q-35-usc-101/</link>
	<description>Patent Bar Review and Study Guide</description>
	<lastBuildDate>Tue, 22 May 2012 00:33:43 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: scruff</title>
		<link>http://mypatentbar.com/2008/09/04/q-35-usc-101/#comment-1468</link>
		<dc:creator>scruff</dc:creator>
		<pubDate>Sat, 20 Jun 2009 18:25:03 +0000</pubDate>
		<guid isPermaLink="false">http://patentbar.wordpress.com/?p=789#comment-1468</guid>
		<description>I suppose I agree with you. This particular type of rejection assumes that there is no utility of invention, even though the invention might comply with one of the statutory classes: machine, manufacture, composition of matter, process. However, you can imagine a case where the invention has utility, but is rejected under 101 because it is not a machine, manufacture, composition of matter, or process. In that case, a rejection under 112(1) would not necessarily follow, unless the specification is independently non-enabling.</description>
		<content:encoded><![CDATA[<p>I suppose I agree with you. This particular type of rejection assumes that there is no utility of invention, even though the invention might comply with one of the statutory classes: machine, manufacture, composition of matter, process. However, you can imagine a case where the invention has utility, but is rejected under 101 because it is not a machine, manufacture, composition of matter, or process. In that case, a rejection under 112(1) would not necessarily follow, unless the specification is independently non-enabling.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: triedandtested</title>
		<link>http://mypatentbar.com/2008/09/04/q-35-usc-101/#comment-1467</link>
		<dc:creator>triedandtested</dc:creator>
		<pubDate>Sat, 23 May 2009 00:41:00 +0000</pubDate>
		<guid isPermaLink="false">http://patentbar.wordpress.com/?p=789#comment-1467</guid>
		<description>I agree with this answer but in real life I guess such a situation arises only when there is a specific rejection of &quot;utility&quot; under 101, as opposed to other type of 101 rejection (like the non-statutory type rejection), and then 101 is followed by 112 (1), not always.

Any thoughts anyone?</description>
		<content:encoded><![CDATA[<p>I agree with this answer but in real life I guess such a situation arises only when there is a specific rejection of &#8220;utility&#8221; under 101, as opposed to other type of 101 rejection (like the non-statutory type rejection), and then 101 is followed by 112 (1), not always.</p>
<p>Any thoughts anyone?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

