<?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: For Chemical Obviousness, Need to Show That Prior Art Suggested Making Modifications to Get Claimed Compound</title>
	<atom:link href="http://www.patentbaristas.com/archives/2007/07/03/for-chemical-obviousness-need-to-show-that-prior-art-suggested-making-modifications-to-get-claimed-compound/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.patentbaristas.com/archives/2007/07/03/for-chemical-obviousness-need-to-show-that-prior-art-suggested-making-modifications-to-get-claimed-compound/</link>
	<description>Freshly Brewed Bio/Pharma Chat. Served Up Daily.</description>
	<lastBuildDate>Thu, 18 Mar 2010 11:54:35 -0400</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: The Fire of Genius &#187; New nonobviousness cases</title>
		<link>http://www.patentbaristas.com/archives/2007/07/03/for-chemical-obviousness-need-to-show-that-prior-art-suggested-making-modifications-to-get-claimed-compound/comment-page-1/#comment-13848</link>
		<dc:creator>The Fire of Genius &#187; New nonobviousness cases</dc:creator>
		<pubDate>Tue, 03 Jul 2007 20:34:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.patentbaristas.com/archives/2007/07/03/for-chemical-obviousness-need-to-show-that-prior-art-suggested-making-modifications-to-get-claimed-compound/#comment-13848</guid>
		<description>[...] Patent Baristas has a terrific post on the Takeda case.    Filed under: Patent Permalink &#124; Trackback URL&#124; [...]</description>
		<content:encoded><![CDATA[<p>[...] Patent Baristas has a terrific post on the Takeda case.    Filed under: Patent Permalink | Trackback URL| [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
