<?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/"
	xmlns:go='http://ns.gigaom.com/'
xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Here Comes Trouble: An Antidote to Software Patents</title>
	<atom:link href="http://gigaom.com/2008/01/18/here-comes-trouble-an-antidote-to-software-patents/feed/" rel="self" type="application/rss+xml" />
	<link>http://gigaom.com/2008/01/18/here-comes-trouble-an-antidote-to-software-patents/</link>
	<description></description>
	<lastBuildDate>Sat, 11 Feb 2012 00:50:04 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: El Mike&#8217;s Internet News Blog &#187; Blog Archive &#187; The Problem With A Database Of Prior Art Is You Don&#8217;t Know What&#8217;s Worth Putting In</title>
		<link>http://gigaom.com/2008/01/18/here-comes-trouble-an-antidote-to-software-patents/#comment-191297</link>
		<dc:creator><![CDATA[El Mike&#8217;s Internet News Blog &#187; Blog Archive &#187; The Problem With A Database Of Prior Art Is You Don&#8217;t Know What&#8217;s Worth Putting In]]></dc:creator>
		<pubDate>Wed, 23 Jan 2008 20:43:04 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/2008/01/18/here-comes-trouble-an-antidote-to-software-patents/#comment-191297</guid>
		<description><![CDATA[&lt;p&gt;[...] was brought to light by Berninger himself). His suggestion is that tech companies should create &#8220;a formal process of contributing software innovations to the public domain.&#8221; It&#8217;s one of those ideas that sounds good in theory, but won&#8217;t work in practice. In the [...]&lt;/p&gt;]]></description>
		<content:encoded><![CDATA[<p>[...] was brought to light by Berninger himself). His suggestion is that tech companies should create &#8220;a formal process of contributing software innovations to the public domain.&#8221; It&#8217;s one of those ideas that sounds good in theory, but won&#8217;t work in practice. In the [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: brave</title>
		<link>http://gigaom.com/2008/01/18/here-comes-trouble-an-antidote-to-software-patents/#comment-191296</link>
		<dc:creator><![CDATA[brave]]></dc:creator>
		<pubDate>Tue, 22 Jan 2008 18:14:13 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/2008/01/18/here-comes-trouble-an-antidote-to-software-patents/#comment-191296</guid>
		<description><![CDATA[&lt;p&gt;Take a look at the Peer to Patent project: http://dotank.nyls.edu/communitypatent/&lt;/p&gt;

&lt;p&gt;The project allows patent applications to be publicly peer reviewed before the applications are passed to patent examiners in hopes of providing the examiner with more complete information about potential prior art.&lt;/p&gt;]]></description>
		<content:encoded><![CDATA[<p>Take a look at the Peer to Patent project: <a href="http://dotank.nyls.edu/communitypatent/" rel="nofollow">http://dotank.nyls.edu/communitypatent/</a></p>
<p>The project allows patent applications to be publicly peer reviewed before the applications are passed to patent examiners in hopes of providing the examiner with more complete information about potential prior art.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave Coveney</title>
		<link>http://gigaom.com/2008/01/18/here-comes-trouble-an-antidote-to-software-patents/#comment-191295</link>
		<dc:creator><![CDATA[Dave Coveney]]></dc:creator>
		<pubDate>Tue, 22 Jan 2008 13:58:16 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/2008/01/18/here-comes-trouble-an-antidote-to-software-patents/#comment-191295</guid>
		<description><![CDATA[&lt;p&gt;How about a use it or lose it principle for any software patents?  That would stop what, to me, appear to be speculative patents designed to give lawyers something to sue for.  The patent holders never use the patent and just wait till someone solves the problems of actually making things work... they then take their losely formed patent and get litigous.&lt;/p&gt;

&lt;p&gt;A small company like ours would be royally stuffed if a patent lawyer came after us.&lt;/p&gt;]]></description>
		<content:encoded><![CDATA[<p>How about a use it or lose it principle for any software patents?  That would stop what, to me, appear to be speculative patents designed to give lawyers something to sue for.  The patent holders never use the patent and just wait till someone solves the problems of actually making things work&#8230; they then take their losely formed patent and get litigous.</p>
<p>A small company like ours would be royally stuffed if a patent lawyer came after us.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Boycott Novell &#187; Patent Concerns Invade GNU/Linux, GPLv3 Offers Remedy</title>
		<link>http://gigaom.com/2008/01/18/here-comes-trouble-an-antidote-to-software-patents/#comment-191294</link>
		<dc:creator><![CDATA[Boycott Novell &#187; Patent Concerns Invade GNU/Linux, GPLv3 Offers Remedy]]></dc:creator>
		<pubDate>Sun, 20 Jan 2008 05:53:41 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/2008/01/18/here-comes-trouble-an-antidote-to-software-patents/#comment-191294</guid>
		<description><![CDATA[&lt;p&gt;[...] distributions. This means that products have beneficial ingredients castrated, not to mention financial aspects of harm, as explained by the following new article.  The $250 million Vonage burned through as a result of [...]&lt;/p&gt;]]></description>
		<content:encoded><![CDATA[<p>[...] distributions. This means that products have beneficial ingredients castrated, not to mention financial aspects of harm, as explained by the following new article.  The $250 million Vonage burned through as a result of [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: plh</title>
		<link>http://gigaom.com/2008/01/18/here-comes-trouble-an-antidote-to-software-patents/#comment-191293</link>
		<dc:creator><![CDATA[plh]]></dc:creator>
		<pubDate>Sun, 20 Jan 2008 03:39:53 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/2008/01/18/here-comes-trouble-an-antidote-to-software-patents/#comment-191293</guid>
		<description><![CDATA[&lt;p&gt;Andrew wrote: &quot;Algorithms that are genuinely new in the sense that literature has never described the abstract process in any context, never mind a reduction to practice, should be as patentable as any other chemical process result if we are going to have patents at all.&quot;&lt;/p&gt;

&lt;p&gt;That might be a reasonable position if the patent system was merely a system for rewarding inventors with prizes, incapable of harm. However, it is not - far from it - and such a position is economically (and ethically) naive (to put it mildly). It is also extremely naive to believe that because some software inventions are just like some other inventions in some respects, they should be patentable.&lt;/p&gt;]]></description>
		<content:encoded><![CDATA[<p>Andrew wrote: &#8220;Algorithms that are genuinely new in the sense that literature has never described the abstract process in any context, never mind a reduction to practice, should be as patentable as any other chemical process result if we are going to have patents at all.&#8221;</p>
<p>That might be a reasonable position if the patent system was merely a system for rewarding inventors with prizes, incapable of harm. However, it is not &#8211; far from it &#8211; and such a position is economically (and ethically) naive (to put it mildly). It is also extremely naive to believe that because some software inventions are just like some other inventions in some respects, they should be patentable.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel Berninger</title>
		<link>http://gigaom.com/2008/01/18/here-comes-trouble-an-antidote-to-software-patents/#comment-191292</link>
		<dc:creator><![CDATA[Daniel Berninger]]></dc:creator>
		<pubDate>Sat, 19 Jan 2008 10:52:24 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/2008/01/18/here-comes-trouble-an-antidote-to-software-patents/#comment-191292</guid>
		<description><![CDATA[&lt;p&gt;Andrew,&lt;/p&gt;

&lt;p&gt;The larger problem comes from the fact litigation diluted the inventive step threshold over the years.&lt;/p&gt;

&lt;p&gt;The &quot;flash of genius&quot; standard from the 1940&#039;s&lt;/p&gt;

&lt;p&gt;http://en.wikipedia.org/wiki/Flash_of_genius&lt;/p&gt;

&lt;p&gt;is entirely gone.&lt;/p&gt;]]></description>
		<content:encoded><![CDATA[<p>Andrew,</p>
<p>The larger problem comes from the fact litigation diluted the inventive step threshold over the years.</p>
<p>The &#8220;flash of genius&#8221; standard from the 1940&#8242;s</p>
<p><a href="http://en.wikipedia.org/wiki/Flash_of_genius" rel="nofollow">http://en.wikipedia.org/wiki/Flash_of_genius</a></p>
<p>is entirely gone.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ajay</title>
		<link>http://gigaom.com/2008/01/18/here-comes-trouble-an-antidote-to-software-patents/#comment-191291</link>
		<dc:creator><![CDATA[Ajay]]></dc:creator>
		<pubDate>Sat, 19 Jan 2008 08:42:24 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/2008/01/18/here-comes-trouble-an-antidote-to-software-patents/#comment-191291</guid>
		<description><![CDATA[&lt;p&gt;Err, that first sentence should read &quot;patents that are obvious.&quot;&lt;/p&gt;]]></description>
		<content:encoded><![CDATA[<p>Err, that first sentence should read &#8220;patents that are obvious.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ajay</title>
		<link>http://gigaom.com/2008/01/18/here-comes-trouble-an-antidote-to-software-patents/#comment-191290</link>
		<dc:creator><![CDATA[Ajay]]></dc:creator>
		<pubDate>Sat, 19 Jan 2008 05:55:40 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/2008/01/18/here-comes-trouble-an-antidote-to-software-patents/#comment-191290</guid>
		<description><![CDATA[&lt;p&gt;Andrew, you rightly highlight the biggest failing in the current patent system when you point out that it gives out plenty of patents that are nonobvious, regardless of whether they&#039;re software or industrial patents.  However, your recurring analogy to chemical processes falls down because the patent system is a flawed way of doing even that.  As you point out, it doesn&#039;t stop drug companies from producing knockoff drugs and is a bad way of protecting drug innovation.  A better IP process for drugs would focus on the safety aspects and be focused on safety certification rather than the current extension of the patent system to something it wasn&#039;t designed for.&lt;/p&gt;

&lt;p&gt;As for software patents, the truth is that almost nothing algorithmic takes the level of R&amp;D investment that some industrial processes take.  You claim that you know of new algorithm patents that took years to develop but if you actually tabulate the money that was invested, you will find that it is a piddling amount.  I think that the overall case for patents of any kind is pretty weak, even when you consider the xerox copier or other famous cases of manufacturing patents.  When you overextend the patent system to areas it was never designed for, like software or pharmaceuticals, it breaks down completely.&lt;/p&gt;]]></description>
		<content:encoded><![CDATA[<p>Andrew, you rightly highlight the biggest failing in the current patent system when you point out that it gives out plenty of patents that are nonobvious, regardless of whether they&#8217;re software or industrial patents.  However, your recurring analogy to chemical processes falls down because the patent system is a flawed way of doing even that.  As you point out, it doesn&#8217;t stop drug companies from producing knockoff drugs and is a bad way of protecting drug innovation.  A better IP process for drugs would focus on the safety aspects and be focused on safety certification rather than the current extension of the patent system to something it wasn&#8217;t designed for.</p>
<p>As for software patents, the truth is that almost nothing algorithmic takes the level of R&amp;D investment that some industrial processes take.  You claim that you know of new algorithm patents that took years to develop but if you actually tabulate the money that was invested, you will find that it is a piddling amount.  I think that the overall case for patents of any kind is pretty weak, even when you consider the xerox copier or other famous cases of manufacturing patents.  When you overextend the patent system to areas it was never designed for, like software or pharmaceuticals, it breaks down completely.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew</title>
		<link>http://gigaom.com/2008/01/18/here-comes-trouble-an-antidote-to-software-patents/#comment-191289</link>
		<dc:creator><![CDATA[Andrew]]></dc:creator>
		<pubDate>Sat, 19 Jan 2008 01:01:34 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/2008/01/18/here-comes-trouble-an-antidote-to-software-patents/#comment-191289</guid>
		<description><![CDATA[&lt;p&gt;The absence of a working prototype is a minor point insofar as it is obvious to someone skilled in the art that such a prototype could be trivially built that functions as described.  The problem with the Verizon patents is that there is nothing there that really meets the threshold of patentability (IMO) and I do defend some software algorithms as reasonable.  The novelty of the patents in question is &lt;em&gt;not&lt;/em&gt; the algorithm, but their chosen reduction to practice of an existing process.&lt;/p&gt;

&lt;p&gt;Using chemical process patents to illustrate the point helps, because it is less contentious.  Suppose I patent a chemical process for synthesizing chemical B from chemical A by some new pathway P.  I am not patenting the production of chemical B, I am patenting the novel algorithm P that allows me to synthesize chemical B from chemical A.  This process P can then be reduced to practice in a diverse set of ways which are protected by copyright.  The kinds of so-called &quot;software patents&quot; that seem to cause the problems are not those that present a novel algorithm P, but those that frame a reduction to practice of an existing abstract algorithm as a patentable entity.  In the case of many business process patents, one could very much argue that they are patenting a reduction to practice which has traditionally been protected by copyright.  The old &quot;do X on the Internet&quot; patent model is clearly nothing more than a particular reduction to practice of well-known ideas.&lt;/p&gt;

&lt;p&gt;Where a lot of people get it wrong is that there are many algorithm patents that are not merely trivial reductions to practice of existing algorithms.  Algorithms that are genuinely new in the sense that literature has never described the abstract process in any context, never mind a reduction to practice, should be as patentable as any other chemical process result if we are going to have patents at all.  Patenting genuinely new abstract algorithms/processes/mechanisms has relatively few downsides in that novel but stupid ones do not matter and the ones that represent a technological improvement are at least nominally fulfilling the intention of patents.  The problem is that a lot of patents granted by the USPTO in &lt;em&gt;all&lt;/em&gt; areas are trivial reductions to practice of already understood ideas and therefore obnoxious.&lt;/p&gt;]]></description>
		<content:encoded><![CDATA[<p>The absence of a working prototype is a minor point insofar as it is obvious to someone skilled in the art that such a prototype could be trivially built that functions as described.  The problem with the Verizon patents is that there is nothing there that really meets the threshold of patentability (IMO) and I do defend some software algorithms as reasonable.  The novelty of the patents in question is <em>not</em> the algorithm, but their chosen reduction to practice of an existing process.</p>
<p>Using chemical process patents to illustrate the point helps, because it is less contentious.  Suppose I patent a chemical process for synthesizing chemical B from chemical A by some new pathway P.  I am not patenting the production of chemical B, I am patenting the novel algorithm P that allows me to synthesize chemical B from chemical A.  This process P can then be reduced to practice in a diverse set of ways which are protected by copyright.  The kinds of so-called &#8220;software patents&#8221; that seem to cause the problems are not those that present a novel algorithm P, but those that frame a reduction to practice of an existing abstract algorithm as a patentable entity.  In the case of many business process patents, one could very much argue that they are patenting a reduction to practice which has traditionally been protected by copyright.  The old &#8220;do X on the Internet&#8221; patent model is clearly nothing more than a particular reduction to practice of well-known ideas.</p>
<p>Where a lot of people get it wrong is that there are many algorithm patents that are not merely trivial reductions to practice of existing algorithms.  Algorithms that are genuinely new in the sense that literature has never described the abstract process in any context, never mind a reduction to practice, should be as patentable as any other chemical process result if we are going to have patents at all.  Patenting genuinely new abstract algorithms/processes/mechanisms has relatively few downsides in that novel but stupid ones do not matter and the ones that represent a technological improvement are at least nominally fulfilling the intention of patents.  The problem is that a lot of patents granted by the USPTO in <em>all</em> areas are trivial reductions to practice of already understood ideas and therefore obnoxious.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Top Posts &#171; WordPress.com</title>
		<link>http://gigaom.com/2008/01/18/here-comes-trouble-an-antidote-to-software-patents/#comment-191288</link>
		<dc:creator><![CDATA[Top Posts &#171; WordPress.com]]></dc:creator>
		<pubDate>Sat, 19 Jan 2008 00:02:35 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/2008/01/18/here-comes-trouble-an-antidote-to-software-patents/#comment-191288</guid>
		<description><![CDATA[&lt;p&gt;[...]  Here Comes Trouble: An Antidote to Software Patents The $250 million Vonage burned through as a result of the patent lawsuit brought by Verizon et al provides yet another [&#8230;] [...]&lt;/p&gt;]]></description>
		<content:encoded><![CDATA[<p>[...]  Here Comes Trouble: An Antidote to Software Patents The $250 million Vonage burned through as a result of the patent lawsuit brought by Verizon et al provides yet another [&#8230;] [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel Berninger</title>
		<link>http://gigaom.com/2008/01/18/here-comes-trouble-an-antidote-to-software-patents/#comment-191287</link>
		<dc:creator><![CDATA[Daniel Berninger]]></dc:creator>
		<pubDate>Fri, 18 Jan 2008 23:58:19 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/2008/01/18/here-comes-trouble-an-antidote-to-software-patents/#comment-191287</guid>
		<description><![CDATA[&lt;p&gt;Andrew,&lt;/p&gt;

&lt;p&gt;I appreciate the point as a theory, but the issues do not seem so clean cut in practice.&lt;/p&gt;

&lt;p&gt;Consider the Verizon patents in question.&lt;/p&gt;

&lt;p&gt;http://scratchpad.wikia.com/wiki/Vonage&lt;/p&gt;

&lt;p&gt;There is no working prototype.&lt;/p&gt;

&lt;p&gt;What is the bright line distinction between a series of ambiguous ideas that do not clearly move from A to B and a innovative algorithm?&lt;/p&gt;

&lt;p&gt;Verizon&#039;s name translation patents are the equivalent of patenting the idea of there should be a &quot;door&quot; on a house.&lt;/p&gt;]]></description>
		<content:encoded><![CDATA[<p>Andrew,</p>
<p>I appreciate the point as a theory, but the issues do not seem so clean cut in practice.</p>
<p>Consider the Verizon patents in question.</p>
<p><a href="http://scratchpad.wikia.com/wiki/Vonage" rel="nofollow">http://scratchpad.wikia.com/wiki/Vonage</a></p>
<p>There is no working prototype.</p>
<p>What is the bright line distinction between a series of ambiguous ideas that do not clearly move from A to B and a innovative algorithm?</p>
<p>Verizon&#8217;s name translation patents are the equivalent of patenting the idea of there should be a &#8220;door&#8221; on a house.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ike Elliott</title>
		<link>http://gigaom.com/2008/01/18/here-comes-trouble-an-antidote-to-software-patents/#comment-191286</link>
		<dc:creator><![CDATA[Ike Elliott]]></dc:creator>
		<pubDate>Fri, 18 Jan 2008 23:45:20 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/2008/01/18/here-comes-trouble-an-antidote-to-software-patents/#comment-191286</guid>
		<description><![CDATA[&lt;p&gt;Daniel, I just heard from an intellectual property lawyer friend of mine, who tells me that there already is a prior art database, formed for just the purpose you suggest.  More on my blog: http://ikeelliott.typepad.com/telecosm/2008/01/there-is-a-soft.html&lt;/p&gt;]]></description>
		<content:encoded><![CDATA[<p>Daniel, I just heard from an intellectual property lawyer friend of mine, who tells me that there already is a prior art database, formed for just the purpose you suggest.  More on my blog: <a href="http://ikeelliott.typepad.com/telecosm/2008/01/there-is-a-soft.html" rel="nofollow">http://ikeelliott.typepad.com/telecosm/2008/01/there-is-a-soft.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel Berninger</title>
		<link>http://gigaom.com/2008/01/18/here-comes-trouble-an-antidote-to-software-patents/#comment-191285</link>
		<dc:creator><![CDATA[Daniel Berninger]]></dc:creator>
		<pubDate>Fri, 18 Jan 2008 22:43:12 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/2008/01/18/here-comes-trouble-an-antidote-to-software-patents/#comment-191285</guid>
		<description><![CDATA[&lt;p&gt;Scott,&lt;/p&gt;

&lt;p&gt;I like your idea as it gets at existing patents whereas building the prior art database will addresses future patents.&lt;/p&gt;]]></description>
		<content:encoded><![CDATA[<p>Scott,</p>
<p>I like your idea as it gets at existing patents whereas building the prior art database will addresses future patents.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ike Elliott</title>
		<link>http://gigaom.com/2008/01/18/here-comes-trouble-an-antidote-to-software-patents/#comment-191284</link>
		<dc:creator><![CDATA[Ike Elliott]]></dc:creator>
		<pubDate>Fri, 18 Jan 2008 21:32:03 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/2008/01/18/here-comes-trouble-an-antidote-to-software-patents/#comment-191284</guid>
		<description><![CDATA[&lt;p&gt;Daniel, I&#039;ve posted a more complete overview of the argument for relying on copyright, instead of patents, to protect software intellectual property rights, on my blog at http://ikeelliott.typepad.com/telecosm/2008/01/a-prior-art-dat.html&lt;/p&gt;]]></description>
		<content:encoded><![CDATA[<p>Daniel, I&#8217;ve posted a more complete overview of the argument for relying on copyright, instead of patents, to protect software intellectual property rights, on my blog at <a href="http://ikeelliott.typepad.com/telecosm/2008/01/a-prior-art-dat.html" rel="nofollow">http://ikeelliott.typepad.com/telecosm/2008/01/a-prior-art-dat.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anthony Kuhn</title>
		<link>http://gigaom.com/2008/01/18/here-comes-trouble-an-antidote-to-software-patents/#comment-191283</link>
		<dc:creator><![CDATA[Anthony Kuhn]]></dc:creator>
		<pubDate>Fri, 18 Jan 2008 21:20:48 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/2008/01/18/here-comes-trouble-an-antidote-to-software-patents/#comment-191283</guid>
		<description><![CDATA[&lt;p&gt;Daniel:&lt;/p&gt;

&lt;p&gt;I think it might be hard to get those companies that benefit from winning a payout in the patent lawsuit lottery to come on board. At some point, the greater good has to be the deciding factor, and businesses aren&#039;t usually in business to do good, but to make money. Plain as that.&lt;/p&gt;

&lt;p&gt;Anthony Kuhn&lt;/p&gt;]]></description>
		<content:encoded><![CDATA[<p>Daniel:</p>
<p>I think it might be hard to get those companies that benefit from winning a payout in the patent lawsuit lottery to come on board. At some point, the greater good has to be the deciding factor, and businesses aren&#8217;t usually in business to do good, but to make money. Plain as that.</p>
<p>Anthony Kuhn</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ike Elliott</title>
		<link>http://gigaom.com/2008/01/18/here-comes-trouble-an-antidote-to-software-patents/#comment-191282</link>
		<dc:creator><![CDATA[Ike Elliott]]></dc:creator>
		<pubDate>Fri, 18 Jan 2008 20:30:46 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/2008/01/18/here-comes-trouble-an-antidote-to-software-patents/#comment-191282</guid>
		<description><![CDATA[&lt;p&gt;Great post, Dan, and your unique position, having worked with VocalTec in the mid-1990s, gives you a valuable perspective on the issue.  Lots to think about, here:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;Should software be patentable?  I would argue that copyright is the correct form of intellectual property protection for software.  The use of the patent system for software is a misapplication of law, in my view.  More on my blog at http://ikeelliott.typepad.com/telecosm/2007/12/licensing-the-b.html&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;The patent office is currently drowning in patent applications and is suffering from a backlog from which it may never recover.  Reforming what is patentable has to be part of the solution...it is just good government.  More here:  http://ikeelliott.typepad.com/telecosm/2008/01/how-the-patent.html&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;An &quot;open source&quot; approach to creating a prior art database sounds useful, and could help in the meantime, while patent reform hopefully winds it way through the system.  I may be overly optimistic about the chances for patent reform, but I think it is the right route.&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;]]></description>
		<content:encoded><![CDATA[<p>Great post, Dan, and your unique position, having worked with VocalTec in the mid-1990s, gives you a valuable perspective on the issue.  Lots to think about, here:</p>
<ol>
<li>
<p>Should software be patentable?  I would argue that copyright is the correct form of intellectual property protection for software.  The use of the patent system for software is a misapplication of law, in my view.  More on my blog at <a href="http://ikeelliott.typepad.com/telecosm/2007/12/licensing-the-b.html" rel="nofollow">http://ikeelliott.typepad.com/telecosm/2007/12/licensing-the-b.html</a></p>
</li>
<li>
<p>The patent office is currently drowning in patent applications and is suffering from a backlog from which it may never recover.  Reforming what is patentable has to be part of the solution&#8230;it is just good government.  More here:  <a href="http://ikeelliott.typepad.com/telecosm/2008/01/how-the-patent.html" rel="nofollow">http://ikeelliott.typepad.com/telecosm/2008/01/how-the-patent.html</a></p>
</li>
<li>
<p>An &#8220;open source&#8221; approach to creating a prior art database sounds useful, and could help in the meantime, while patent reform hopefully winds it way through the system.  I may be overly optimistic about the chances for patent reform, but I think it is the right route.</p>
</li>
</ol>
]]></content:encoded>
	</item>
</channel>
</rss>

