Finally sat down and read the amicus brief [pdf] filed by Red Hat in the In Re Bilski case. In it, Red Hat argues that software patents “do not always promote innovation, and they may substantially hinder it.” They note that the software industry matured and thrived without software patents, and quote Dr. Knuth at Stanford University, who said that “I strongly believe that the recent trend to patenting algorithms is of benefit only to a very small number of attorneys and inventors, while it is seriously harmful to the vast majority of people who want to do useful things with computers.” Red Hat argues that the Federal Circuit decision [pdf] holding that software patents should be restricted to those algorithms “tied to a particular machine or apparatus.” In effect, they are arguing that the legal world has turned its back on the teachings of Benson and Diehr, which required algorithms to be tied to tangible machines or transformative processes, and have instead adopted the more murky State Street Bank outlook that a patent is valid if the practical application “produces a useful, concrete and tangible result.” Red Hat notes that software developers enjoy a robust amount of protection under copyright law, and that software patents create a world in which small-time developers are squeezed out by litigious trolls and patent war chests held as a defensive measure by large corporations.
Now, I do I agree with Red Hat that software patenting certainly needs to be reigned in somewhat; it does seem strange that Amazon can obtain a patent on 1-click purchases or that a company can make blanket claims to streaming audio and video with incredibly nebulous claims. And I will concede that software patents do lend themselves to patent trolling in ways that mechanical and biological patents do not, chief amongst them the fact that quite a few early-issued ones were granted with overly broad terms. Finally, the success of open-source software has shown that developers and companies can, and will, innovate without the presumed impetus provided by strong patent protection.
At the same time, though, I think there is some overreaction to the inevitable growing pains that software patents have gone through over the years. While mechanical and chemical patents have existed for hundreds of years, software patents are significantly younger than the Baby Boomers. This is still a young field, one that has been undergoing a significant examination and maturation since the 1970s. Inevitably, there have been setbacks and poor decisions, and some of these missteps have led to unnecessary litigation that has stymied innovation, at least temporarily. At the same time, though, I think it is too early to just dismiss software patents as wholly unnecessary and a pox on innovation, because I think they still can serve as a tool for growth in the industry if properly monitored. For while the industry certainly matured somewhat during the 60′s and 70′s, it has also taken immense steps forward in the age of software patents.
Because the arguments I hear most often against software patents seem to focus far more on the inferior quality of issued patents rather than the value of patents in general. I think all will admit that bad patents, in any discipline, need to be eradicated; but to dismiss all patents because of a few bad examples is the equivalent to throwing the proverbial baby out with the bath water.
Can Patents Level the Playing Field?
A key argument made supporting software patents is that it helps to level the playing field, especially as it relates to small companies and single inventors, because it provides a tangible manifestation of algorithms that, by their nature, are more fluid and commutable than other technologies. By allowing an inventor to identify his/her novel invention and clearly articulate its metes and bounds to the world, he/she is afforded at least some protection from others “stealing” or otherwise using this invention without proper recognition and (I assume) financial compensation.
For example, small-time company A has invented a novel way to compress video and transmit it over a network connection with far greater efficiency than the current competition. Now, they may try to license the technology to others, and during this process a major tech company such as Microsoft, Google, or Apple may catch wind of it and, based on some hint or revelation provided by this exposure, create a competing technology that is similar to company A’s technology. Under current patent law, if company A filed a patent application for the technology and properly described the utility and novel elements of the technology, they would be entitled to some protections against this major tech company’s integration of company A’s novel technology. And from a pragmatic sense, this works – company A put in the effort and R&D to create this improvement, and it would seemingly be unfair to allow this hard work to go for naught because a major player in the field joined the party late.
Because while I do not have much experience working in the tech industry, what little I have has shown the industry to be very Darwinian – large companies feast upon smaller companies and inventors specifically because they cannot adequately protect themselves. Company A may be able to mount an offense via public relations on blogs and sue someone over a breach of confidentiality, but without patents the major tech company will release its own software and, because of its significant market advantage, dominate the competition even though they may not have been responsible for the innovation. Sometimes the strong survive not because they are the best, but simply because they are able to leverage their size/knowledge/experience/resources to a degree that its competitors cannot. But with a valid patent, the small inventors and innovators are able to level the playing field immensely, taking advantage of a system designed to protect the creators and expose their inventions to society at large.
But What About Copyrights?
One of the chief arguments made by Red Hat and other opponents of software patents is that software designers already receive adequate protection under current copyright law. To an extent, I agree with them – copyright law forbids the exact copying (and some limited “equivalence”) of code without authorization. This provides some protection for the inventor from direct copying by a competitor, and provides adequate remedies for violations at least on the small scale. And unlike software patents, the rights conveyed by a copyright exist as soon as the code is recorded on a tangible medium, with further public registration an option but not a necessity. No messy paperwork, no major fees, and some certainty that your innovation will not go unnoticed.
At the same time, though, copyright always felt like a round hole into which software was jammed into. At its core, copyright law was intended to protect literary, artistic, and musical works – tangible works that by their nature can only take a single form. If you significantly change the elements of a copyrighted work, the result is a wholly new and unique copyrightable work, not necessarily bound to the earlier work. In other words, Moby Dick is only Moby Dick in the way Melville wrote it – the arrangement of words in a particular order that are embodied in the novel. Take those same words and jumble them up, and you have another original work, but it is not Moby Dick. Sure, there are a bundle of exclusive rights for a copyright holder that grant him/her some protections against unauthorized duplication and piracy, but by their nature that are less expansive than those granted by patents.
By its nature, though, software does not lend itself to a single permutation. Though this is highly simplistic, while loops and for loops often do the exact same thing, yet can appear markedly different depending on how they are implemented. Image rendering algorithms can have significantly different processing times depending on the order in which they perform a certain set of shared steps, making one significantly more attractive than another to a particular customer. The same really could not be said for a novel or a song – place the refrain of a song before the intro and it wouldn’t make much sense, nor would splicing chapters of a novel together in an illogical order. While the value of most copyrighted works is in the expression of the work on a tangible medium, software’s value is derived far more from the ideas behind it, the innovation in the outlook and the fresh perspective and improvements they provide over the current guard. Yet copyright protection doesn’t usually extend out to the mental ether – it is rooted in the crumpled pages and sheet music, the framed canvases and the blueprints. Copyright is like a lasso; at first it might seem expansive and wide-ranging, but pull on it a bit and it ultimately captures only the tangible object it is wrapped around.
So if copyright can best be described as a tight lasso, patents are more like a free-flowing net. While patents are not perfect, they cast a wider net over an invention, capturing at least some of this novel thinking beyond what is submitted as the best mode or manifestation of the idea. True, this net needs to be further inspected and refined to make sure that it does not capture more than it should, but it does provide far more protection for the “essence” of an invention than copyright, protection that I suspect most inventors would rather retain at least initially.
Can Open-Source and Patent Law Co-Exist?
The success of the open-source movement is indisputable; I am currently writing this post using Firefox on a system running Ubuntu while listening to music with Songbird. Some of the best programs available today are open-source, and the community has proven to be far more robust and innovative than I think even its greatest proponents ever imagined. It has also shown to be a very adaptive movement, adroitly dealing with legal issues through community-based decisions such as the GPL. It has fostered innovation and has shown to be a viable competitor in virtually every arena, from operating systems to gaming, and all without the use of software patents or proprietary software.
At the same time, open source is not a purely altruistic movement. Red Hat, for example, generates millions of dollars a year in income through its various products and services. Many companies that provide “free” software generate income through maintenance, training, and other services that, arguably, are as profit-driven as those from industry “behemoths” such as Apple, IBM, and Microsoft. Even those companies and individuals who provide their expertise to the open-source movement without any demand for direct compensation usually expect to benefit in a variety of non-monetary ways, such as increased market presence, prestige, and recognition. And it is a safe bet that if someone were to benefit from the use of their code or innovation without proper attribution or recognition, many of them would feel betrayed and take measures to remedy it.
I guess that is my point – open-source and the proprietary/patent software worlds are profoundly different on some levels and remarkably similar on others. They will likely never be fully reconciled, and that is perfectly fine. But can only one survive, or can both co-exist provided that they limit their interactions?
Red Hat argues that “[a] separate but related problem faces all software developers—that of the impossibility of patent clearance, or determining whether there are existing patents that may be said to read on a new product.” By allowing software patents, you are creating a world in which innovators are constantly at the mercy of some unknown patent being hoarded by a patent troll, to be used as a crude ax at a moment’s notice to eviscerate the innovator. And to an extent, I understand why this must be troubling to small companies and single inventors – your work is independent of this patent, yet you are held subject to it even if you had no knowledge of its existence before your were served with the lawsuit.
But I think the argument here goes more to a bad patent than the notion of a patent. Companies and inventors alike hate bad software patents, those patents which are incredibly broad and poorly-written, claiming far-reaching technologies without providing adequate description and disclosure. That I understand, and I think the patent system is slowly eliminating these mistakes while correcting the flaws that allowed them to exist in the first place. At the same time, though, the patent system also provides a level of protection for these smaller companies otherwise unavailable in the industry. And for all the complaints that software lawsuits are exploding, litigation exists across all disciplines, and the uptick in recent years probably has more to do with the relative immaturity of the art compared to other, more established disciplines, where there are more precedents clearly-defined stakes. Given time, I suspect that litigation will subside and fall more in line with other fields.
What I think is oftentimes lost in the debate over software patents is that for every party “losing” out because a patent exists covering their technology, there is a party whose rights are being protected for the work they put into it. Sure, this “race to the office” is a major shortcoming of the current patent system, but no system is perfect. Red Hat argues that software patents make it impossible to perform a complete search of the prior art – try performing a similar search over just copyrights, which do not require registration and receive virtually not scrutiny or vetting. At some point, you just have to keep innovating and hope that you are the first to truly innovate. And if there is a patent that covers your current invention, do what most companies do when they run into a competing patent – design and innovate around it. In crowded arts this might be difficult, but it is possible. Companies make billions of dollars by innovating around what is known, and my guess is that some of these innovations would never have been considered without the current state of the art being codified in some USPTO filings.
Conclusion
Ultimately, I think that software patents are not going to disappear from the landscape, though they will likely be further massaged and augmented by decisions like In Re Bilski and cases that have not even been filed. While I recognize that there are flaws to the current patent system, it also provides a substantial number of benefits both to inventors and society in general. To cast it aside at this point would be premature, and may very well have a detrimental impact on innovation going forward.
No Comments »