About This Blog
Automating Invention is Robert Plotkin's blog on the impact of computer-automated inventing on the law (primarily patent law). The blog also explores the implications of computer-automated inventing for creativity, ethics, and high-tech industry.
Categories
Links
Blogs
- 271 Patent Blog
- BLOG@IP::JUR
- Boalt IP Blawg
- Epistasis Blog
- Evolutionary Computation
- Genetic Argonaut
- IlliGAL Blog
- Invent Blog
- The Long Tail
- IP Newsflash
- The Open Road
- Patent Pending
- Peer to Patent
- The Singularity Institute
- Promote the Progress Blawg
Technology & Policy
- Berkman Center for Internet and Society
- Computer Professionals for Social Responsibility
- Electronic Frontier Foundation
- MIT STS Program
- Samuelson Law, Technology, and Public Policy Clinic
- Stanford Law School Center for Internet and Society
- U.S. Public Policy Committee of the Association for Computing Machinery
Resources (Law)
- Bitlaw
- European Patent Office
- Software Patent Institute
- Software Patents vs. Parliamentary Democracy
- United States Patent and Trademark Office
- World Intellectual Property Organization
Resources (Technology)
- Genetic-Programming.org (John Koza)
- Introduction to Genetic Algorithms
- Genetic Algorithms Archive
- Genetic Algorithms and Artificial Life Resources
- Genetic Programming FAQ
- Genetic Programming Bibliography
- Generative Programming
- HDL Page
- NASA Evolvable Systems Group
- Evolvable Hardware (Los Alamos National Laboratory)
- Evolvable Hardware (University of Oslo)
Commercial Applications
- Affinnova, Inc.
- Icosystem Corporation
- Imagination Engines, Inc.
- Matrix Advanced Solutions Ltd.
- Natural Selection, Inc.
- NuTech Solutions
- Quantum Leap Innovations
- Red Cedar Technology
- TenFold Corporation
People
- Sion Balass
- Peter J. Bentley
- Hans-Georg Beyer
- Eric Bonabeau
- Ralph Clifford
- David Davis
- David Fogel
- James Foster
- David Goldberg
- Erik Goodman
- J. Storrs Hall
- Andrew Hodges’ Alan Turing Site
- John Holland
- Gregory Hornby
- Lorenz Huelsbergen
- John Koza
- Ray Kurzweil
- Hod Lipson
- Jason Lohn
- Julian Miller
- James Moor
- Daniel H. Pink
- Jordan Pollack
- Joe Rothermich
- Karl Sims
- Daniel H. Pink
- Lee Spector
- Stephen Thaler
- Adrian Thompson
- Marcel Thuerk
- Christof Teuscher
- Andy Tyrell
- Tina Yu
Philosophy
Search
Recent Entries
- Patents vs. Prizes
- Your Genome for $399
- Outsourcing Manufacturing Isn't Just for Large Companies Anymore
- My Book on Invention Automation to be Published by Stanford in Spring 2009
- Gamers Solve Problems in Science and Computing
- Software Improvises Musical Accompaniments
- Computer Simulation Uncovers Evidence of Biological Evolution
- Has Microsoft Really Patented Page Up and Page Down?
- Breaking the Software Development Speed Limit with Agile Programming
- Complexity: Computers Come to the Rescue
- Calculator Dates Back Two Millenia
- Does Google Make Us Dumber or Smarter?
Archives
« Would the real invention please step forward? | Main | History of Evolutionary Computation »
December 21, 2005
Why the Solution to the Obviousness Problem in Software Patents Isn't Obvious
Techdirt says that there is a simple explanation for why software patents are dangerous. If I understand him correctly, there are two problems.
First, it takes too long for the U.S. Patent Office to figure out whether a patent is valid.
Second, "many programmers faced with similar problems will come up with similar solutions." Granting a patent to one of those programmers gives that programmer the ability to block the others from using the same solution, even if they developed it independently.
It might be true that programmers are more likely than other kinds of scientists and engineers to come up with similar solutions when faced with similar problems. People often make this claim, but I haven't seen any evidence for it. In evaluating whether any particular software patent claim is "obvious," the best that any patent office or court can do is to try to figure out what would have been obvious to an ordinary programmer in the relevant field at the time. This is a hard thing to do in any technological field, not just computer science. And if programmers want to help reduce the number of obvious patents being granted, they can contribute prior art to prior art databases (such as Gauss) or in a patent reexamination. Look here for another interesting proposal along these lines.
If it is true that "many programmers faced with similar problems will come up with similar solutions," the real problem with software patents might not be that the "obviousness" standard doesn't work correctly for software, but that there is no "independent creation" defense for patent infringement, as there is for copyright infringement. In other words, you can infringe a patent even if you independently invent the invention covered by the patent (i.e., without copying the invention covered by the patent). I raise this only to point out how many cans of worms can be opened even by a single seemingly simple observation about the nature of innovation in software.
Posted by Robert at December 21, 2005 5:58 PM
category:
Software Patents
Comments
Post a comment
Thanks for signing in, . Now you can comment. (sign out)
(If you haven't left a comment here before, you may need to be approved by the site owner before your comment will appear. Until then, it won't appear on the entry. Thanks for waiting.)

