<?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: 35 USC 112, 1st paragraph (Specification)</title>
	<atom:link href="http://mypatentbar.com/2007/11/28/35-usc-112-1st-paragraph/feed/" rel="self" type="application/rss+xml" />
	<link>http://mypatentbar.com/2007/11/28/35-usc-112-1st-paragraph/</link>
	<description>Patent Bar Review and Study Guide</description>
	<lastBuildDate>Sat, 19 May 2012 22:04:39 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: 182.454545454545</title>
		<link>http://mypatentbar.com/2007/11/28/35-usc-112-1st-paragraph/#comment-1170</link>
		<dc:creator>182.454545454545</dc:creator>
		<pubDate>Sun, 06 Dec 2009 06:42:43 +0000</pubDate>
		<guid isPermaLink="false">http://mypatentbar.com/2007/11/28/35-usc-112-1st-paragraph/#comment-1170</guid>
		<description>hsIKkA  &lt;a href=&quot;http://bikagejjachy.com/&quot; rel=&quot;nofollow&quot;&gt;bikagejjachy&lt;/a&gt;, [url=http://qwcpgioxlwwn.com/]qwcpgioxlwwn[/url], [link=http://oshmqzmnwmul.com/]oshmqzmnwmul[/link], http://wkusidwnilvi.com/</description>
		<content:encoded><![CDATA[<p>hsIKkA  <a href="http://bikagejjachy.com/" rel="nofollow">bikagejjachy</a>, [url=http://qwcpgioxlwwn.com/]qwcpgioxlwwn[/url], [link=http://oshmqzmnwmul.com/]oshmqzmnwmul[/link], <a href="http://wkusidwnilvi.com/" rel="nofollow">http://wkusidwnilvi.com/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sean</title>
		<link>http://mypatentbar.com/2007/11/28/35-usc-112-1st-paragraph/#comment-1169</link>
		<dc:creator>Sean</dc:creator>
		<pubDate>Thu, 07 May 2009 22:46:59 +0000</pubDate>
		<guid isPermaLink="false">http://mypatentbar.com/2007/11/28/35-usc-112-1st-paragraph/#comment-1169</guid>
		<description>Can the applicant overcome a 112, para 1 rejection simply by amending the specification as opposed to amending the claims to agree with the spec, or arguing inherent or implied disclosure in the spec, or arguing that the missing alleged essential matter on which the rejection was based is in fact not essential?

But since the specification is disclosure embodied, amending it to agree with the claims is risky because of the &quot;no new matter&quot; rule.  Correct?

Thank you in advance.</description>
		<content:encoded><![CDATA[<p>Can the applicant overcome a 112, para 1 rejection simply by amending the specification as opposed to amending the claims to agree with the spec, or arguing inherent or implied disclosure in the spec, or arguing that the missing alleged essential matter on which the rejection was based is in fact not essential?</p>
<p>But since the specification is disclosure embodied, amending it to agree with the claims is risky because of the &#8220;no new matter&#8221; rule.  Correct?</p>
<p>Thank you in advance.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nik</title>
		<link>http://mypatentbar.com/2007/11/28/35-usc-112-1st-paragraph/#comment-1168</link>
		<dc:creator>Nik</dc:creator>
		<pubDate>Fri, 08 Feb 2008 21:48:22 +0000</pubDate>
		<guid isPermaLink="false">http://mypatentbar.com/2007/11/28/35-usc-112-1st-paragraph/#comment-1168</guid>
		<description>As the note re: ranges and failing to meet the written description requirement, the 112(1) issue with the &quot;at least 30%&quot; language is that &quot;at least&quot; has no upper limit, and thus is not supported by the as-filed specification.  Claiming an endpoint within a range described in the as-filed specification, or even one outside the as-filed range is permissible in certain instances.  See In re Wertheim (the specification need not provide ipsis verbis (word for word) support for all claim elements; rather, support for the claim elements may be found in the express, implicit, and inherent disclosuire of the as-filed specification and claims)</description>
		<content:encoded><![CDATA[<p>As the note re: ranges and failing to meet the written description requirement, the 112(1) issue with the &#8220;at least 30%&#8221; language is that &#8220;at least&#8221; has no upper limit, and thus is not supported by the as-filed specification.  Claiming an endpoint within a range described in the as-filed specification, or even one outside the as-filed range is permissible in certain instances.  See In re Wertheim (the specification need not provide ipsis verbis (word for word) support for all claim elements; rather, support for the claim elements may be found in the express, implicit, and inherent disclosuire of the as-filed specification and claims)</p>
]]></content:encoded>
	</item>
</channel>
</rss>

