ESP Wiki is looking for moderators and active contributors!

Difference between revisions of "Invalidating harmful patents"

(External links: Bradley M. Kuhn)
(# This can be difficult, expensive, and can take years. The Amazon's one-click shopping patent is an example.)
Line 1: Line 1:
{{dud}}(Note: '''This is not a solution.'''  [[Risks of supporting partial solutions|Supporting it is risky]], and it's results will be at best very limited)
+
{{dud}}
  
By '''invalidating the most harmful software patents''', we can reduce some harm being done by software patents.  However, this almost always relies on questing the obviousness or the newness of patents and thus the invalidations don't create any precedent which would reduce the scope for the patent office to grant software in future.  To do that, we need to [[invalidate patents based on subject matter]].
+
By '''invalidating the most harmful software patents''', we can reduce some harm being done by software patents.  However, this almost always relies on questioning the obviousness or the newness of patents and thus the invalidations don't create any precedent which would reduce the scope for the patent office to grant software in future.  To do that, we need to [[invalidate patents based on subject matter]].
  
This is usually done by finding [[prior art]] or by arguing that an idea was too obvious.  In this case, the limits below apply, however, if it is argued that the patent was granted for something that's not patentable (software, [[business methods]], math), then the precedent will be very significant because it will narrow the scope for the granting and enforcement of software patents.
+
If it is argued that the patent was granted for something that's not patentable (software, [[business methods]], math), then the precedent will be very significant because it will narrow the scope for the granting and enforcement of software patents.
  
 
==Limits to effectiveness==
 
==Limits to effectiveness==
Line 9: Line 9:
 
# We can only invalidate a small number of patents.  This can never solve the problem caused by the existence of tens of thousands of patents.
 
# We can only invalidate a small number of patents.  This can never solve the problem caused by the existence of tens of thousands of patents.
 
# Some software patent pests have a large collection of annoying patents they could use instead if their favourite patents were invalidated.  For example, [[Microsoft vs TomTom, 2008|Microsoft accused TomTom]] of violating eight patents.  The patents look invalid, but if they are invalidated there's still the worry that Microsoft will choose some other of its 10,000 patents to continue the menace.
 
# Some software patent pests have a large collection of annoying patents they could use instead if their favourite patents were invalidated.  For example, [[Microsoft vs TomTom, 2008|Microsoft accused TomTom]] of violating eight patents.  The patents look invalid, but if they are invalidated there's still the worry that Microsoft will choose some other of its 10,000 patents to continue the menace.
 +
# This can be difficult, expensive, and can take years.  The [[Amazon's one-click shopping patent]] is an example.
  
 
==Related pages on {{SITENAME}}==
 
==Related pages on {{SITENAME}}==
Line 19: Line 20:
 
* [http://www.post-issue.org/ Post-Issue Peer To Patent]
 
* [http://www.post-issue.org/ Post-Issue Peer To Patent]
 
** [http://www.ifosslr.org/ifosslr/article/viewArticle/9/6 Collaborative approach: Peer-to-Patent and the Open Source movement]
 
** [http://www.ifosslr.org/ifosslr/article/viewArticle/9/6 Collaborative approach: Peer-to-Patent and the Open Source movement]
 +
* [http://yro.slashdot.org/story/10/02/20/205232/USPTOs-1-Click-Indecisiveness-Enters-5th-Year USPTO's 1-Click Indecisiveness Enters 5th Year]
  
  

Revision as of 23:00, 20 February 2010

Red alert.png What this entry documents is not a solution.
This practice may be ineffective or useless in the long term.
ESP's position is that abolition of software patents is the only solution.


By invalidating the most harmful software patents, we can reduce some harm being done by software patents. However, this almost always relies on questioning the obviousness or the newness of patents and thus the invalidations don't create any precedent which would reduce the scope for the patent office to grant software in future. To do that, we need to invalidate patents based on subject matter.

If it is argued that the patent was granted for something that's not patentable (software, business methods, math), then the precedent will be very significant because it will narrow the scope for the granting and enforcement of software patents.

Limits to effectiveness

  1. Patents can only be invalidated if they are invalid to begin with.
  2. We can only invalidate a small number of patents. This can never solve the problem caused by the existence of tens of thousands of patents.
  3. Some software patent pests have a large collection of annoying patents they could use instead if their favourite patents were invalidated. For example, Microsoft accused TomTom of violating eight patents. The patents look invalid, but if they are invalidated there's still the worry that Microsoft will choose some other of its 10,000 patents to continue the menace.
  4. This can be difficult, expensive, and can take years. The Amazon's one-click shopping patent is an example.

Related pages on ESP Wiki

External links