<?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>HuffingtonPost: At the Heart of the Knowledge Economy: Should Patents Be Limited To Technology?</title>
		<link>http://www.digitalmajority.org/forum/t-58305/huffingtonpost:at-the-heart-of-the-knowledge-economy:should</link>
		<description>Posts in the discussion thread &quot;HuffingtonPost: At the Heart of the Knowledge Economy: Should Patents Be Limited To Technology?&quot; - The case, In re Bilski, involves a pure business method, no technology, not even making use of a computer. It involves hedging bets in commodity markets by matching conservative buyers against others more inclined to gamble on the expected. In fact, it sounds a lot like how bookies handle betting on horse races. But the issue here is not whether this process is new or nonobvious but whether it should be patentable in the first place. Should we allow patents on tax-avoidance strategies? Legal arguments? Mathematical algorithms? Toilet reservation systems? Negotiation tactics? Business models?</description>
				<copyright></copyright>
		<lastBuildDate>Sun, 12 Feb 2012 02:26:48 +0000</lastBuildDate>
		
					<item>
				<guid>http://www.digitalmajority.org/forum/t-58305#post-159385</guid>
				<title>HuffingtonPost: At the Heart of the Knowledge Economy: Should Patents Be Limited To Technology?</title>
				<link>http://www.digitalmajority.org/forum/t-58305/huffingtonpost:at-the-heart-of-the-knowledge-economy:should#post-159385</link>
				<description></description>
				<pubDate>Wed, 07 May 2008 16:25:28 +0000</pubDate>
				<wikidot:authorName>zoobab</wikidot:authorName>				<wikidot:authorUserId>2946</wikidot:authorUserId>				<content:encoded>
					<![CDATA[
						 <p><a href="http://www.huffingtonpost.com/brian-kahin/at-the-heart-of-the-knowl_b_100404.html">http://www.huffingtonpost.com/brian-kahin/at-the-heart-of-the-knowl_b_100404.html</a></p> 
				 	]]>
				</content:encoded>							</item>
				</channel>
</rss>
