I've been procrastinating for the last week and a half or so (admittedly with a Thanksgiving holiday thrown in the middle) writing up my impressions of the recent conference at Santa Clara University called Solutions to the Software Patent Problem
. If you want something of a play-by-play on what happened, Groklaw has a pretty good tick-tock
on the specifics. Unfortunately, I'm not sure that really covered some of the larger important themes that the conference brought out.
First off, I know that some patent system defenders took great offense to the idea that the event wasn't "balanced" with system supporters. Nearly every speaker presented an aspect of how the system was broken with suggestions to fix it. But I see this complaint as being misleading. There's this random belief out there that conference panels need to be "balanced" with "pro & con" and then let the panelists argue things out. I've argued against this in the past when setting up panels for other events, and with the events
that we run, we've tried to avoid that concept as well. While just setting up pro vs. con can make for an entertaining session, it rarely leads to productive discussions that move the conversation forward. They just lead to people arguing past each other. A productive
event is one in which people agree on a basic premise or problem and are then working towards possible responses. That's what this was. It was a conference for those who believe the system is broken
. Given that assumption, the point of the event was to suggest possible solutions. There are plenty of events where patent system defenders and skeptics can argue against each other, but I can't think of another where people were able to dig in deep on possible fixes.
Given all that, there were a lot
of different ideas proposed -- some broad, some specific. Many of them required people to have pretty deep knowledge of how the system works. For patent system geeks, it was really fascinating -- but for those less aware of the inner workings of the system I could see how the basic play-by-play seems confusing or uninteresting. However, in reality, there were a number of interesting ideas presented on ways to fix various problems, from getting Congress involved to having the courts better adhere to the law to getting the Patent Office to better adhere to rules to increasing maintenance fees to carving out software entirely... and many more. The conference schedule
has links to more detailed versions of various proposals, sometimes both the "academic" versions and more "mainstream" versions at Wired Opinion. I'll point to a few of the suggestions I found to be more compelling in a bit.
However, what I found really useful
about the event was twofold:
- There are a lot of smart people thinking about the very obvious problems of the system, and they are trying to come up with solutions. That's a good thing, even if there are many (powerful) interests who don't want the system to change at all. You can only deny reality for so long.
- There are also many ideas for solutions, some of which are quite clever, others of which seem like blunt force attempts to deal with symptoms rather than actual problems. Also, as was raised by some people in the comments, many of the suggestions could have significant unintended consequences that weren't readily considered. This is important -- for as much as I believe that the system needs fixing (and I have my own suggestions for solutions), thinking through the consequences of any change is an important exercise (though always keeping in mind that defenders of the status quo seem to argue any change will destroy the American economy and probably take apple pie and motherhood with it).
We already explored
the suggestions from Richard Stallman and Mark Lemley in earlier
posts, so we'll look at a few other interesting suggestions.
- There was some interest in using patent fees as a way that the patent office might be able to fix some of the worst problems without requiring a change in the law. James Bessen pointed out that bad patents are a form of pollution and, as such should be taxed as polluters. Christina Mulligan pushed back against attempts at doing the opposite, as urged by some patent system defenders, noting that "Cheaper patent applications mean more – and lower-quality! – patents. Lowering filing fees will make more people more likely to file patents. But if the marginal difference in patent fees is holding inventors back from filing applications, the patent is probably covering a low-value invention."
- Related to this, Brian Love presented some research and a proposal for using higher fees to decimate trolls. Part of his argument is that the data shows that trolls quite frequently become much more active as a patent is close to expiring: "Of all patent suits litigated within the final three years of the asserted patents' term of protection, trolls file more than 70%. Of all companies accused of infringing a patent within three years of its expiration, trolls accuse more than 83%." His suggestion is that shortening the term length of patents would deal with this problem, and would likely hurt only trolls or failing companies that are lashing out at more innovative competitors (he highlights Kodak and Encyclopaedia Britannica). But rather than actually go through the process of shortening patents, he argues just increasing the maintenance fees to keep a patent for the full term. He notes that many other countries already do something like this. The data here was compelling, though the risk is that it would just mean that patent trolls would become more active in earlier years...
- Peter Menell picked up on the point that many have raised that patents aren't at all clear in what they cover. So he thinks that we should force patents to be much clearer in what the claims cover. Specifically, he argues for a form-based system where you have a series of check boxes and pull downs in defining a claim to make it clear what you're actually trying to cover. I like the idea that patents should be much more precise over what they claim, but I'm not sure it's realistic to think that a form would (a) do this well or (b) be properly used.
- Arti Rai pointed out that the software crowd probably screwed up years ago, by not doing what the bioinformatics world did in claiming that you can't get a patent unless you provide the actual working algorithm. This seems like something of a no-brainer. The USPTO has regularly rejected bioinformatics claims on the basis of a lack of "definiteness" for not supplying the algorithm. There's no reason that the same couldn't be done in software. Of course, that would require the USPTO to actually notice this point...
- I thought John Duffy's proposal was one of the most interesting (and, in the past, I've found myself disagreeing with Duffy more often than agreeing with him) in which he argued the most "elegant" solution to the software patent problem that isn't all that far off from my own suggestion: fix the "non-obviousness" standard by noting that multiple parties simultaneously, independently inventing the same thing is a sign of obviousness and should lead to no patents being allowed. Duffy's presentation was the one that set Richard Stallman off for arguing that Stallman's solution was "kludgey" rather than a full solution. On this one, I side with Duffy. Duffy's solution here would likely be a lot more effective that Stallman's because patent lawyers could easily write around Stallman's solution of not allowing patents on "general purpose" computing.
- Samson Vermont highlighted that we should take into account social harm (Word doc). That is, he suggests courts should base remedies on the amount of harm on the public rather than on the harm on the patentee. "More specifically, in cases in which the defendant's infringement clearly makes the world better off, the court should deny the patentee both money damages and injunctive relief." More specifically, he argues that if the patent isn't actually being used to put a product on the market (either by the inventor or a licensee), the accused infringer is an independent inventor and is actually putting a product out there and the "costs to find the patentee's version of the invention beforehand were greater than the defendant's costs to invent it on his own" then courts should reject any awards. As he notes, when all three conditions are met, "it is very hard to come up with plausible reasons to believe that the defendant's infringement is a bad thing."
There were plenty of other presentations, but those were the ones that seemed most interesting and worth thinking about more deeply. As for the biggest waste of time? That award goes to Dan Ravicher, of PubPat, who plays both sides
of the patent troll fence. He started off his presentation by haranguing everyone for not showing enough "respect" for the existing system and various people, and then proceeded to yell at everyone in attendance that they "failed" because they didn't raise their hands fast enough when he mentioned various patent troll lawsuits that he didn't think were that problematic. One of his larger points was sound -- that if you want to convince anyone in the government that the patent system is broken you have to focus entirely on "jobs, jobs, jobs." But there's no reason he had to be completely obnoxious in getting that point across. Many of his other points were specious, at best. However, it has set for me a new "Ravicher Rule": if someone starts off a talk by arguing that everyone needs to be more respectful of everyone else, the probability that they will disrespect pretty much everyone quickly approaches one.
Overall, it was a really great and thought-provoking event. I'm happy that there's a lot of detailed thought going into ways to solve the patent trolling problem, though I'd argue we need to be careful not to just think that this is a "software patent" issue. I think the problems of the system apply equally
elsewhere -- which is why I like system-wide fixes, such as those suggested by Duffy and Vermont.
And, just to address this one point before one of our regular patent lawyer commenters tries to make it in the comments: there is an argument among patent system supporters that there is no such thing as a "software patent" and thus any argument that uses that term is meaningless. This is both slightly true and (more importantly) a distortion of the larger issue. As was discussed at the conference, there is a difference between software and hardware that can't be denied. One involves moving around bits. One doesn't. So it's not difficult to define software differently from hardware. The real problem
is that if we did
carve out software from patentability, it's likely that crafty patent lawyers would quickly figure out how to rewrite patent claims to make them broadly cover the same concepts in a way that could be seen as not being "software." Given all that, I think it's quite legitimate to discuss "patents that cover software" as "software patents," even while I agree that merely targeting "software patents" misses the larger problem.