Here's Hoping The Supreme Court Does Not Blow Another Opportunity To Fix The Software Patent Problem
from the ditch-those-patents dept
Four years ago, the Supreme Court had a chance to establish once and for all whether or not software was patentable. The Bilski case got all sorts of attention as various parties lined up to explain why software patents were either evil, innovation-killing monsters or the sole cause of innovation since the cotton gin and everything in between (only slight exaggeration). Rather than actually answer the question everyone was asking, the Supreme Court decided to rule especially narrowly, rejecting the specific patents at stake in the case and saying that the current test used to determine patentability (the so-called "machine-or-transformation" test) need not be the only test for patentability. However, it declined to say what tests should be used, leaving it up to the lower courts to start ruling blindly, making up new tests as they went along. And muddle along blindly they did -- right up to the height of pure absurdism in the CAFC (appeals court that handles patents) ruling in the Alice v. CLS Bank case, in which every single judge disagreed with each other. The ruling was 135 pages of confused mess where all justices only agreed on a single paragraph, which (like Bilski) said this particular patent was invalid, but no one could agree why.In the wake of this, the Supreme Court agreed to hear the appeal, and once again it appears that tons of folks are lining up on the various sides, pushing the Supreme Court to either validate, toss out or at least provide a more clear test on the patentability of "abstract ideas" within the software context. The specific question the Supreme Court is being asked to resolve is:
Whether claims to computer-implemented inventions – including claims to systems and machines, processes, and items of manufacture – are directed to patent-eligible subject matter within the meaning of 35 U.S.C. § 101 as interpreted by this Court.The oral arguments were heard earlier today, and, as per usual, reveal little about what the Supreme Court is really thinking (trying to divine which way the court will land based on oral arguments rarely works out well). The Bilski ruling is mentioned repeatedly, and everyone seems to want to bend over backwards to not outlaw "software patents," but what we really need is for the Supreme Court to issue a clear ruling on what is and what is not patentable in this arena.
If you want to take a look at how we got here, including how the Supreme Court really outlawed software patents decades ago, only to then have the CAFC bring them back (in a big, bad way) while the Supreme Court was looking elsewhere, Tim Lee's final story at the Washington Post has all of the gory details. Jeff John Roberts, over at GigaOm has a nice compact piece on what's at stake directly in this case. Meanwhile, even the NY Times has weighed in with an editorial hoping the Supreme Court sets clear rules against abstract ideas being patentable.
Since the messy Bilski ruling, the Supreme Court has taken slightly more aggressive stances in ruling out controversial areas of patenting, including rejecting medical diagnostic patents and gene patents. While companies in both spaces have been trying to get around those rulings, on the whole, they were much clearer and more useful rulings than the messy Bilski ruling on software patents. While the current Supreme Court often seems gun-shy about establishing clear rules of the road on these kinds of issues, preferring to narrowly tailor rulings, hopefully the final ruling in Alice v. CLS Bank will not be the same mess the Bilski ruling left us with, which begat the CAFC's 135-page mess in Alice.
The Supreme Court had a golden opportunity four years ago to solve a big patent problem... and it blew it. Hopefully, this time it won't miss the opportunity.
Thank you for reading this Techdirt post. With so many things competing for everyone’s attention these days, we really appreciate you giving us your time. We work hard every day to put quality content out there for our community.
Techdirt is one of the few remaining truly independent media outlets. We do not have a giant corporation behind us, and we rely heavily on our community to support us, in an age when advertisers are increasingly uninterested in sponsoring small, independent sites — especially a site like ours that is unwilling to pull punches in its reporting and analysis.
While other websites have resorted to paywalls, registration requirements, and increasingly annoying/intrusive advertising, we have always kept Techdirt open and available to anyone. But in order to continue doing so, we need your support. We offer a variety of ways for our readers to support us, from direct donations to special subscriptions and cool merchandise — and every little bit helps. Thank you.
–The Techdirt Team
Filed Under: bilski, escrow, patents, software patents, supreme court
Companies: alice, cls bank
Reader Comments
Subscribe: RSS
View by: Time | Thread
If not, then I should be able to write a cook book and patent fried chicken recipes.
[ link to this | view in chronology ]
Re:
Because under copyright a different program achieving the same end does not infringe, but under patents it does. Hence managers at the big companies got their lawyers to figure out how to patent software by adding the magic words on a computer. Technically they are not patenting the idea, but a machine that implements the idea; which is a fudge to get round the no patenting of abstract ideas.
[ link to this | view in chronology ]
Re:
In the same way most people do not see the specific colour of the painting, but only what it does for the painting, same goes for source code. It is a fundamental mistake since patenting of source code in obscure language x is equivalent to the source of language y and equivalent to the pure mathematics of numerical machine code.
It is like patenting a specific colour or DNA/RNA-strand, but under the right circumstances you can get away with both, so why not math?
[ link to this | view in chronology ]
Re: Re:
Patents are supposed publicly disclose the detail of how they work. Effectively, they need to be reproduceable from the patent. That's the reason why they're protected.
If you can't reproduce the output from copying the patented methodology, then you shouldn't have a patent.
In software, by the time you've documented the methodology in order for it to be replicated, you've pretty much got down to the code level. Since that is already covered by copyright, there's no need for patents.
[ link to this | view in chronology ]
Re:
[ link to this | view in chronology ]
Re:
The term "process" means process, art or method, and includes a new use of a known process, machine, manufacture, composition of matter, or material.
Ignoring the inane circularity of a "'process' means process", the act was amended to employ the word "process" in the 1930s, back when "information processing" was virtually non-existent. So the term as intended by the legislators of the time obviously only referred to processing associated with mechanics, chemistry, and manufacturing for which granting of patent protection is arguably reasonable (or at least the processes are not abstract).
With the advent of computers, and the ability of machines to "process" information, the term took on the connotation of performing manipulations upon purely abstract concepts -- something that has traditionally been rejected as deserving of patent protection.
Unfortunately there are many misguided folk who fail to grasp that no matter how much you process an abstract concept (such as information), that concept is still going to be abstract.
[ link to this | view in chronology ]
Re: Why such narrow rulings?
But it seems like a trend for the SCOTUS to rule so narrowly as to not make a decision at all, lately. "in re Bilski" is one example, but that GPS tracker decision last year is another. Instead of slapping the FBI upside the head for quibbling about should be a straightforward "Freedom from Search and Seizure" decision, the SCOTUS made it all about trespass.
What's going on here? Is this because only spineless wimps with no record of controversial opinions can make it on the Court these days, or is it because of Bork or can I blame it all on Clarence Thomas' being totally compromised?
[ link to this | view in chronology ]
Re: Re: Why such narrow rulings?
[ link to this | view in chronology ]
Re: Re: Why such narrow rulings?
You're right that how much the Supreme Court does changes with the judges. If you're curious about this look up the term "judicial activism".
[ link to this | view in chronology ]
Re: Re: Re: Why such narrow rulings?
"Judicial activism" just means "I don't like what they decided (even though I haven't read it), but I don't want to sound like QUITE that much of a naked partisan". Do you think the Court was activist when it overturned part of DOMA? What about when it overturned part of the Voting Rights Act? Is the only difference that you disagree with one and not the other? Was Roe v. Wade activism? What about Citizens United?
[ link to this | view in chronology ]
The problem i see
In the unlikely event that the supreme court strikes them down, How long do you think it would be before the likes of IBM, microsoft, et al, go to congress and buy themselves a new law? 2 weeks? perhaps 3?
[ link to this | view in chronology ]
[ link to this | view in chronology ]
software
[ link to this | view in chronology ]