<?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: CAFC: A Divisional By Any Other Name Is Not a Divisional</title>
	<atom:link href="http://www.ipwatchdog.com/2009/09/16/cafc-a-divisional-by-any-other-name-is-not-a-divisional/id=6140/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.ipwatchdog.com/2009/09/16/cafc-a-divisional-by-any-other-name-is-not-a-divisional/id=6140/</link>
	<description>Patents, Software Patents, Patent Applications &#38; Patent Law</description>
	<lastBuildDate>Thu, 09 Feb 2012 07:58:49 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: patent leather</title>
		<link>http://www.ipwatchdog.com/2009/09/16/cafc-a-divisional-by-any-other-name-is-not-a-divisional/id=6140/#comment-8246</link>
		<dc:creator>patent leather</dc:creator>
		<pubDate>Thu, 17 Sep 2009 17:34:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.ipwatchdog.com/?p=6140#comment-8246</guid>
		<description>However, I&#039;m assuming all this could have been easiy cured by filing a terminal disclaimer with the continuation. I&#039;ll be sure to be checking all my cases for this issue...</description>
		<content:encoded><![CDATA[<p>However, I&#8217;m assuming all this could have been easiy cured by filing a terminal disclaimer with the continuation. I&#8217;ll be sure to be checking all my cases for this issue&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: EG</title>
		<link>http://www.ipwatchdog.com/2009/09/16/cafc-a-divisional-by-any-other-name-is-not-a-divisional/id=6140/#comment-8245</link>
		<dc:creator>EG</dc:creator>
		<pubDate>Thu, 17 Sep 2009 15:15:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.ipwatchdog.com/?p=6140#comment-8245</guid>
		<description>Dale,

I hear you, but I&#039;m not sure I would characterize this as a &quot;minor technical error.&quot;.  Amgen made the deliberate choice to designate the two key applications (&#039;178 and &#039;179) as &quot;continuations.&quot;  What I still can&#039;t figure out is why Amgen choose to designate these applications as &quot;continuations.&quot;   The benefit of doing so (versus designating these applications as  &quot;divisionals&quot;) escapes me.

In defense of the Federal Circuit&#039;s opinion in Amgen, 35 USC 121, including the title of it, only refers to &quot;original&quot; and &quot;divisional&quot; applications.  Accordingly, their view that designating the application as a &quot;divisional&quot; that is being filed in response a restriction requirement (also necessary under 35 USC 121 to get the &quot;safe harbor&quot;) is reasonable to make clear that the benefit of the &quot;safe harbor&quot; applies..  For example, a &quot;continuation&quot; application could be to present claims different from or even broader than those presented in the &quot;original&quot; (parent) application, i.e., is not in response to a restriction requirement.  Again, Amgen made the designation of &quot;continuation,&quot; not the Federal Circuit.

Thanks for your comment and thoughts.</description>
		<content:encoded><![CDATA[<p>Dale,</p>
<p>I hear you, but I&#8217;m not sure I would characterize this as a &#8220;minor technical error.&#8221;.  Amgen made the deliberate choice to designate the two key applications (&#8217;178 and &#8217;179) as &#8220;continuations.&#8221;  What I still can&#8217;t figure out is why Amgen choose to designate these applications as &#8220;continuations.&#8221;   The benefit of doing so (versus designating these applications as  &#8220;divisionals&#8221;) escapes me.</p>
<p>In defense of the Federal Circuit&#8217;s opinion in Amgen, 35 USC 121, including the title of it, only refers to &#8220;original&#8221; and &#8220;divisional&#8221; applications.  Accordingly, their view that designating the application as a &#8220;divisional&#8221; that is being filed in response a restriction requirement (also necessary under 35 USC 121 to get the &#8220;safe harbor&#8221;) is reasonable to make clear that the benefit of the &#8220;safe harbor&#8221; applies..  For example, a &#8220;continuation&#8221; application could be to present claims different from or even broader than those presented in the &#8220;original&#8221; (parent) application, i.e., is not in response to a restriction requirement.  Again, Amgen made the designation of &#8220;continuation,&#8221; not the Federal Circuit.</p>
<p>Thanks for your comment and thoughts.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dale B. Halling</title>
		<link>http://www.ipwatchdog.com/2009/09/16/cafc-a-divisional-by-any-other-name-is-not-a-divisional/id=6140/#comment-8244</link>
		<dc:creator>Dale B. Halling</dc:creator>
		<pubDate>Thu, 17 Sep 2009 14:57:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.ipwatchdog.com/?p=6140#comment-8244</guid>
		<description>Another case of formalism being more important than substance.  Because of a minor technical error an inventor loses their rights.  How does that promote science and the useful arts?</description>
		<content:encoded><![CDATA[<p>Another case of formalism being more important than substance.  Because of a minor technical error an inventor loses their rights.  How does that promote science and the useful arts?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

