Reading The Bilski Tea Leaves For What The Supreme Court Thinks Of Software Patents
from the there's-still-a-possibility-there dept
Since it's been a week or so since the Bilski ruling, and as more people have had more time to look at and sift through the rulings in greater detail, some are realizing there may actually be a light at the end of the tunnel for those who dislike software patents. Contrary to the claims of the IEEE, the ruling did not, in fact, come out and say that software patents are legit. It sidestepped that question -- in part due to Justice Scalia's decision to opt-out of two sections of Kennedy's majority opinion.Tim Lee does an excellent job delving into just why Scalia may have opted-out of those sections, suggesting that Scalia is not comfortable with software patents, and didn't want to give that part of the ruling precedential powers:
Back in 2007 I noticed that Justice Scalia (along with Stevens and Breyer) was asking questions that suggested skepticism about the patentability of software. Scalia's position in Bilski confirms that impression: Whenever Justice Kennedy waxes poetic about the Information Age, Justice Scalia gets off the bus. The result is an exceptionally narrow holding that doesn't give much comfort to partisans on either side.Larry Downes, in looking over the opinions notes something very similar (as part of a much longer analysis of the ruling), in that Scalia seems to very clearly signal that he does not agree with the court's State Street ruling, which is the ruling that opened the floodgates for all sorts of software to be patented:
As noted, Scalia joined all of Justice Kennedy's opinion other than the two sections expressing concern about the impact "machine-or-transformation" would have on what Kennedy refers to repeatedly as inventions of "The Information Age."Finally, an analysis over at Patently-O by Shubha Ghosh also suggests that the Supreme Court is signalling that it's not a fan of the State Street decision, and thinks it's important for the Federal Circuit to establish a different test for software patents:
There's no way to know why Scalia declined to join those sections (and, therefore, robbed them of precedential status), but one clue can be found in a third concurrence, this one by Justice Breyer, which Scalia joined in part.
...
Scalia joins Part II of Breyer's opinion, which tries to summarize the points on which all nine Justices are, at the end of the day, in agreement. (All nine, of course, voted to affirm the Federal Circuit's rejection of Bilski's application. The only question had to do with the reasoning for that rejection.)
Breyer returns to the cases from which the Federal Circuit derived the "machine-or-transformation" test, and notes that "transformation is the clue to the patentability of a process claim that does not include particular machines." (emphasis in original)
The error of the Federal Circuit, then, was to treat "machine-or-transformation" not as a test, but as "the exclusive test." (emphasis in original) And "machine-or-transformation" is still a far better test, Breyer (with Scalia) goes on, than the much broader statement from State Street ("useful, concrete and tangible result") that started this whole mess.
Here's the kicker. Breyer and Scalia agree that "[t]o the extent that the Federal Circuit's decision in this case rejected [the State Street] approach, nothing in today's decision should be taken as disapproving of that determination."
So, there you have it. Scalia doesn't like State Street and doesn't hate "machine-or-transformation."
Specifically, the Court has now revived the Gottschalk-Parker-Diehr line of cases, which were established before the creation of the Federal Circuit and which the Federal Circuit had distilled over time into the expansive "useful-concrete-tangible" approach to patentable subject matter and then into the "machine or transformation test." In effect, the Supreme Court by reviving its precedent has negated over twenty-five years of the Federal Circuit's attempts at doctrine. This revival opens up possibilities for examiners to rethink the relationships among process, machine, and the physical world. "Dubious" patents may be rejected because the physical phenomenon is trivial or too preemptive of the field. Patent claims might require closer connection to a machine embodiment as opposed to an abstracted, disembodied form. An interesting question to ask is whether the patent at issue in State Street would survive the analysis proposed by Bilski. On the one hand, the asset allocation method at issue is arguably as abstract as the hedging method. On the other hand, the method seems closely tied to a machine to give the process some specific limits.So, what does this mean for folks who are troubled by software patents? Well, Bradley Kuhn has a few suggestions, but I would imagine some folks are out there scouring the country for a potential new test case that really zeroes in on the question of what test should be used to judge whether or not a software is patentable. Right now we have an effectively clean slate, but it doesn't mean that software is, inherently, patentable. It just means the courts still need to determine the appropriate test, and it appears that an important bloc of Supreme Court Justices are at the very least open to a rather strict test on software patentability.
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, patents, scalia, software patents
Reader Comments
Subscribe: RSS
View by: Time | Thread
Web Giants came along without any special laws for them they become what they are because they were left alone to flourish, the road to success is littered with failures, thousands of web projects didn't happen but those that did are strong for now until they get legal crutches. Thousands of software companies came and go.
It is part of the circle of life, they are born and they die, not letting those things die is depriving the business market of renewal and innovation, that comes from the struggle to survive. Taking away the strugle takes away the need to innovate, improve and learn.
Rome took a 1000 years to collapse, the only super power in the world may be done in a 100.
[ link to this | view in chronology ]
oh, and the lead time to get to scotus is, what, 5 to 10 years before a case can make it through all the lower courts and appeals? change will not come from the courts, it will come from the halls of congress.
[ link to this | view in chronology ]
Re:
[ link to this | view in chronology ]
Groklaw concurs and goes a bit further
She focuses more on Justice Stevens than on Justice Scalia but the trail leads to a the same conclusion.
One of the arguments against software patents that PJ has used over the years is that, at the end of the day, all software boils down to Please show me something patentable in software that is not an algorithm. I mean "show me" literally. Show me in the software code something patentable that is not an algorithm, since algorithms are not patentable subject matter. And that's her challenge to the TAMs of the world, who is presumably a TAPJ(?) though that doesn't roll off the tongue quite so nicely, one which, like most others, he hasn't answered yet.
[ link to this | view in chronology ]
Re: Groklaw concurs and goes a bit further
[ link to this | view in chronology ]
Re: Re: Groklaw concurs and goes a bit further
http://www.groklaw.net/article.php?story=20100629014657710
Sheesh!
[ link to this | view in chronology ]
Re: Groklaw concurs and goes a bit further
One may patent a "process"
The definition of a process being "a series of steps to accomplish a specific task."
One may not patent an "algorithm"
The definition of algorithm being "a series of steps to accomplish a specific task."
What's the difference?
[ link to this | view in chronology ]
Re: Re: Groklaw concurs and goes a bit further
Still a process doesn't need to be a mathematical expression. It may be but it doesn't need to be.
Software at machine code level IS a mathematical expression. Otherwise it won't work.
[ link to this | view in chronology ]
Re: Re: Groklaw concurs and goes a bit further
The process can be original and creative. By that I mean that it can involve entirely new ways of doing things that have been previously undefined.
The algorithm is a series of steps that are all part of a realm that has already been defined: math. All the steps do is manipulate a reality that is already known or relatively obvious in that it follows mathematical law. Unless a part of the algorithm literaly BROKE mathematical law and functioned outside of it, it just isn't original. Essentially, it's already known, even if the math hasn't been specifically manipulated in that manner before.
How'd I do?
[ link to this | view in chronology ]
Re: Re: Re: Groklaw concurs and goes a bit further
And very much on the mark.
[ link to this | view in chronology ]
Re: Re: Re: Groklaw concurs and goes a bit further
I program microprocessors, and there's some weird voodoo interaction shite twixt programming, micro-electronics, and the real world. Almost nothing works like the pure mathematics says it should...
[ link to this | view in chronology ]
Re: Re: Re: Groklaw concurs and goes a bit further
This is just priceless
ready for your lobotomy, punk ?
[ link to this | view in chronology ]
Re: Re: Re: Re: Groklaw concurs and goes a bit further
[ link to this | view in chronology ]
Re: Re: Re: Groklaw concurs and goes a bit further
All parts of anything used in a process are already defined: as a part of reality. Unless the process 'breaks' reality and functions outside of reality then it shouldn't be patentable? Right? There is nothing being done today that hasn't been done or thought of previously (even if it wasn't patented or recorded, someone out there has thought about it...) Reality is already known, even if it hasn't been specifically manipulated in that manner before.
[ link to this | view in chronology ]
Re: Re: Re: Re: Groklaw concurs and goes a bit further
But I suppose if you believe in Fredkin style Digital Philosophy, and if you believe that the entire universe is basically one big Turing Complete Machine, then it's all just math anyway....
[ link to this | view in chronology ]
Re: Re: Re: Groklaw concurs and goes a bit further
The process is a series of steps that are all part of a realm that has already been defined: physics. All the steps do is manipulate a reality that is already known or relatively obvious in that it follows physical law. Unless a part of the algorithm literaly BROKE physical law and functioned outside of it, it just isn't original. Essentially, it's already known, even if the physics hasn't been specifically manipulated in that manner before.
Fixed that for you.
Sorry, but you still have not convinced me that there is any difference between an "algorithm" and a "process". Not to mention that, as the comic I linked to mentions, physics is nothing more than applied mathematics.
[ link to this | view in chronology ]
Re: Groklaw concurs and goes a bit further
[ link to this | view in chronology ]
Re: Re: Groklaw concurs and goes a bit further
[ link to this | view in chronology ]
Re: Re: Re: Groklaw concurs and goes a bit further
[ link to this | view in chronology ]
Re: Re: Re: Re: Groklaw concurs and goes a bit further
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Groklaw concurs and goes a bit further
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Groklaw concurs and goes a bit further
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Groklaw concurs and goes a bit further
[ link to this | view in chronology ]
Re: Re: Re: Groklaw concurs and goes a bit further
plain and simple, they didnt rule against those types of patents, and it will take years for another case to make it to scotus. those are not opinions, those are facts.
she is more than welcome to have an opinion, they are like belly buttons (or another area slightly lower and to the rear), everyone has one. but the only facts in the case are the that scotus did not rule against these patents, and there are no other cases currently on the horizon that would change that.
[ link to this | view in chronology ]
Re: Re: Re: Re: Groklaw concurs and goes a bit further
[ link to this | view in chronology ]
They were put there so do something what it was?
- Teach others?
Today patents don't teach anything and it is on purpose because the more specific you are the harder it is to claim damages or that it was infringed upon, besides open source took care of that did it not? People are developing software for free and are teaching others how to do it and patents actually harm people who want to teach others.
- Incentive?
Open source dispelled that myth did it not?
So why do people need patents?
[ link to this | view in chronology ]
call it a day
Just admit that you know jackshit about software, algorithms, patents, court procedures and call it a day
[ link to this | view in chronology ]
Re: call it a day
*I trolled with angry dude*
(PS Just kidding Mike, we like ya 'round here.)
[ link to this | view in chronology ]
Re: call it a day
Or any of the people Mike and PJ cite know noting at all?
Hmmmmmmm
[ link to this | view in chronology ]
Re: Re: call it a day
Sometimes even serious folks with PhDs in science say stupid things like "software is math"
[ link to this | view in chronology ]
Re: Re: Re: call it a day
[ link to this | view in chronology ]
Re: Re: Re: Re: call it a day
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: call it a day
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: call it a day
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: call it a day
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: call it a day
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: call it a day
Does all this about copyrights and TAMs and angry dude trollers mean that people with photographic memories are, by their definition, guilty of piracy and therefore criminals?
If you get to be one with a supercoying machine in your pocket surely it must apply if it's a gelatenous substance located between your ears that you were born with?!
Wonder what the MPAA, RIAA, TAM etc think of that? ;-)
[ link to this | view in chronology ]
Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: call it a day
[ link to this | view in chronology ]
Re: Re: Re: call it a day
You'd have us believe you follow patent and copyright issues like a hawk and haven't heard of Groklaw, PJ (aka Pamela Jones if you must know) and the SCO vs damned near everyone cases?
And sometimes dipshites who haven't a clue what software is will say software isn't math.
[ link to this | view in chronology ]
No tea leaves to be read
Their message: if you just follow the law and the legal precedents from the Judiciary then we won't have to deal with this crap. And, oh, by the way, the machine or transformation test is ok, but if you would just look at what we've said *is not patentable* and used your brains we wouldn't be here.
Of course, the software/business process/mindless junk patent lawyers will hail this as a great ($$$$$) victory.
[ link to this | view in chronology ]
almost beer time, punks
[ link to this | view in chronology ]
Re: almost beer time, punks
[ link to this | view in chronology ]
Re: almost beer time, punks
Break out the Champagne!
[ link to this | view in chronology ]
On the fence
[ link to this | view in chronology ]
Re: On the fence
I'm a programmer and not a litigation wonk, but I think the traditional idea of a patent is a slippery slope... Before software existed it wasn't as obvious and didn't matter much, but now it intuitively (though perhaps not technically/legally) applies to software.
The same type(s) of ingenuity which Edison and Tesla used to harness electrons now produces algorithms which are math technically but works of art psychologically and economically. The motions and parts of a generator loosely correspond to functions and variables, respectively.
That being said, I don't think software should be both copyrightable and patentable; one or the other (or both) should be trimmed back. But it's not immediately obvious which one is more relevant, from an all-around perspective. It's text (copyrightable) that does something (patentable); before software the nearest concept was a magical incantation, and courts don't concern themselves with fictional ideas.
I suppose the best approach would be to determine the most-desirable powers for software licenses to be granted, for the general benefit of society, and match those to copyrights, patents, or a new concept that's somewhere in between.
[ link to this | view in chronology ]