<?xml version="1.0" encoding="UTF-8" ?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wikidot="http://www.wikidot.com/rss-namespace">

	<channel>
		<title>IPWatchdog: Bilski Arguments Complete at the US Supreme Court</title>
		<link>http://www.digitalmajority.org/forum/t-195268/ipwatchdog:bilski-arguments-complete-at-the-us-supreme-court</link>
		<description>Posts in the discussion thread &quot;IPWatchdog: Bilski Arguments Complete at the US Supreme Court&quot; - At 2pm ET on November 9, 2009, Chief Justice John Roberts gaveled the session to a close announcing that the case had now been submitted. The arguments were good, and the Court was most assuredly hot, peppering both sides with question after question seeking to probe the issues. It is clear that the Supreme Court did their homework</description>
				<copyright></copyright>
		<lastBuildDate></lastBuildDate>
		
					<item>
				<guid>http://www.digitalmajority.org/forum/t-195268#post-628779</guid>
				<title>IPWatchdog: Bilski Arguments Complete at the US Supreme Court</title>
				<link>http://www.digitalmajority.org/forum/t-195268/ipwatchdog:bilski-arguments-complete-at-the-us-supreme-court#post-628779</link>
				<description></description>
				<pubDate>Mon, 09 Nov 2009 21:23:01 +0000</pubDate>
				<wikidot:authorName>ggiedke</wikidot:authorName>				<wikidot:authorUserId>32664</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p><em>"At 2pm ET on November 9, 2009, Chief Justice John Roberts gaveled the session to a close announcing that the case had now been submitted. The arguments were good, and the Court was most assuredly hot, peppering both sides with question after question seeking to probe the issues. It is clear that the Supreme Court did their homework."</em></p> <p>Source: <a href="http://www.ipwatchdog.com/2009/11/09/bilski-arguments-complete-at-the-us-supreme-court/id=7217/">http://www.ipwatchdog.com/2009/11/09/bilski-arguments-complete-at-the-us-supreme-court/id=7217/</a></p> 
				 	]]>
				</content:encoded>							</item>
				</channel>
</rss>