<?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: Making patent claims easier to read</title>
	<atom:link href="http://www.concurringopinions.com/archives/2007/01/making_patent_c.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.concurringopinions.com/archives/2007/01/making_patent_c.html</link>
	<description>The Law, the Universe, and Everything</description>
	<lastBuildDate>Sun, 22 Nov 2009 17:51:16 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.3</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: dak</title>
		<link>http://www.concurringopinions.com/archives/2007/01/making_patent_c.html/comment-page-1#comment-55552</link>
		<dc:creator>dak</dc:creator>
		<pubDate>Mon, 22 Jan 2007 19:18:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.solove.org/archives/2007/01/making-patent-claims-easier-to-read.html#comment-55552</guid>
		<description>Foreign jurisdictions allow multiple dependent claims that depend from multitply dependent claims, for example:

&lt;p&gt; 1. A PB&amp;J sandwich.

&lt;p&gt;2. The PB&amp;J sandwich of claim 1, with crunchy PB.

&lt;p&gt;3. The PB&amp;J sandwich of claim 1 or 2, with strawberry jam.

&lt;p&gt;&lt;b&gt;4. The PB&amp;J sandwich of claim 1, 2 or 3, on whole wheat bread.&lt;/b&gt;

&lt;p&gt;

Under US law (35 USC 112, para. 4), claim 4 is improper, as one multiple dependent claim that depends from another. If such claims were permissible (and understood to mean that each possible combination of dependency is included),  that would allow drafters to write compact claim sets that cover many independent combinations of features. &lt;/p&gt;&lt;/p&gt;&lt;/p&gt;&lt;/p&gt;&lt;/p&gt;

</description>
		<content:encoded><![CDATA[<p>Foreign jurisdictions allow multiple dependent claims that depend from multitply dependent claims, for example:</p>
<p> 1. A PB&#038;J sandwich.</p>
<p>2. The PB&#038;J sandwich of claim 1, with crunchy PB.</p>
<p>3. The PB&#038;J sandwich of claim 1 or 2, with strawberry jam.</p>
<p><b>4. The PB&#038;J sandwich of claim 1, 2 or 3, on whole wheat bread.</b></p>
<p>Under US law (35 USC 112, para. 4), claim 4 is improper, as one multiple dependent claim that depends from another. If such claims were permissible (and understood to mean that each possible combination of dependency is included),  that would allow drafters to write compact claim sets that cover many independent combinations of features. </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mmm</title>
		<link>http://www.concurringopinions.com/archives/2007/01/making_patent_c.html/comment-page-1#comment-55551</link>
		<dc:creator>mmm</dc:creator>
		<pubDate>Mon, 22 Jan 2007 16:00:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.solove.org/archives/2007/01/making-patent-claims-easier-to-read.html#comment-55551</guid>
		<description>Adam, I do not think his proposal changes things.  The idea of a &quot;land grab&quot; is essentially what the broadest claim is anyway.  Everything in the &quot;outlined&quot; claims already are encompassed by the broad claim (that&#039;s the point) For example:

I claim

1. A sandwich.

2. A sandwich in 1 comprising peanut butter and jelly.

The reason to do this isn&#039;t to expand the scope, it&#039;s to CYA.  If there is invalidating material for 1 that you may not be aware of, you still can protect 2.

My hunch, however, is not that this way of claiming is difficult to read, but that there are just a number of bad writers.

In it&#039;s own way, patent law is arcane and obscure.  This has a lot to do with the proclivity of patent prosecutors to adopt language with known/litigation-tested meaning.

</description>
		<content:encoded><![CDATA[<p>Adam, I do not think his proposal changes things.  The idea of a &#8220;land grab&#8221; is essentially what the broadest claim is anyway.  Everything in the &#8220;outlined&#8221; claims already are encompassed by the broad claim (that&#8217;s the point) For example:</p>
<p>I claim</p>
<p>1. A sandwich.</p>
<p>2. A sandwich in 1 comprising peanut butter and jelly.</p>
<p>The reason to do this isn&#8217;t to expand the scope, it&#8217;s to CYA.  If there is invalidating material for 1 that you may not be aware of, you still can protect 2.</p>
<p>My hunch, however, is not that this way of claiming is difficult to read, but that there are just a number of bad writers.</p>
<p>In it&#8217;s own way, patent law is arcane and obscure.  This has a lot to do with the proclivity of patent prosecutors to adopt language with known/litigation-tested meaning.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adam</title>
		<link>http://www.concurringopinions.com/archives/2007/01/making_patent_c.html/comment-page-1#comment-55550</link>
		<dc:creator>Adam</dc:creator>
		<pubDate>Sun, 21 Jan 2007 23:12:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.solove.org/archives/2007/01/making-patent-claims-easier-to-read.html#comment-55550</guid>
		<description>I don&#039;t think we should make it easier to claim combinations of elements in the way you outline.  To be perjorative to the idea, patents should not be land-grabs, but disclosure of what you think is new, useful, and non-obvious.  If you think combo ABDE is useful, say so; don&#039;t say &quot;and we&#039;d like to protect a set of things whose use we can&#039;t really concieve of.&quot;

</description>
		<content:encoded><![CDATA[<p>I don&#8217;t think we should make it easier to claim combinations of elements in the way you outline.  To be perjorative to the idea, patents should not be land-grabs, but disclosure of what you think is new, useful, and non-obvious.  If you think combo ABDE is useful, say so; don&#8217;t say &#8220;and we&#8217;d like to protect a set of things whose use we can&#8217;t really concieve of.&#8221;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
