Slashdot Mirror
Supreme Court Throws Out Bilski Patent
ciaran_o_riordan writes "The US Supreme Court has finally decided the Bilski case (PDF). We've known that Bilski's patent would get thrown out; that was clear from the open mockery from the judges during last November's hearing. The big question is, since rejecting a particular patent requires providing a general test and explaining why this patent fails that test, how broad will their test be? Will it try to kill the plague of software patents? And is their test designed well enough to stand up to the army of patent lawyers who'll be making a science (and a career) of minimizing and circumventing it? The judges have created a new test, so this will take some reading before any degree of victory can be declared. The important part is pages 5-16 of the PDF, which is the majority opinion. The End Software Patents campaign is already analyzing the decision, and collecting other analyses. Some background is available at Late-comers guide: What is Bilski anyway?"
More analysis of the decision is available at Patently-O.
Diana Ross was not available for comment's. Rejoicing software developer's liberally apply apostrophe's in the street's but are they celebrating too soon?
My work here is dung.
Dear Mister Language Person: What is the purpose of the apostrophe?
Answer: The apostrophe is used mainly in hand-lettered small business signs to alert the reader than an "S" is coming up at the end of a word, as in: WE DO NOT EXCEPT PERSONAL CHECK'S, or: SUPREME'S THROW OUT BILSKI PATENT. Another important grammar concept to bear in mind when creating hand- lettered small-business signs is that you should put quotation marks around random words for decoration, as in "TRY" OUR HOT DOG'S, or even TRY "OUR" HOT DOG'S.
-- Dave Barry, "Tips for Writer's"
punted.
Bastards. Bilski is invalid, machine-or-transformation is thrown out, but the court explicitly provides no further guidance either way.
Let's make a Patent that Patents the system for which Patent Lawyers & Patent Registers Circumvent Common Sense and are awarded Patents. That way anyone who files one of these ridiculous patents are infringing upon my patent. Anyone who defends the patent is also infringing upon my patent.
I'll see you in court Bitches. (That is step 6 of my process)
The Software Freedom Law Center has a great response up. From SFLC chairman Eben Moglen: "The confusion and uncertainty behind today's ruling guarantees that the issues involved in Bilski v. Kappos will have to return to the Supreme Court after much money has been wasted and much innovation obstructed."
(I hope they'll be providing a deeper analysis later on; the above came out like ten minutes after the decision, so obviously it's just based on the summary of the decision.)
-Karl Fogel
http://www.red-bean.com/kfogel
Supreme's Throw Out Bilski Patent
How many time's [sic] do I have to sic Bob on you?
Free Martian Whores!
This is Slashdot. Like 4chan, we have a collective consciousness. No explanation needed. Bilski, what is it? I have a new tagline:
Slashdot. We Know.
This supreme court is stacking up to being the best one ever!
The judges have created a new test...
No, the judges said that the "machine or transformation" test that the Federal Circuit used to reject Bilski wasn't the exclusive test, but merely an important tool... And then they left it at that, and didn't specify a new test.
The important parts to take away here are that this decision carefully tiptoed away from software, and did affirm that some business methods are patentable.
They've basically declined to create a new test. The "majority" opinion, in its strongest parts, which leaned more in favor of business-method patents, only got 4 votes (Scalia didn't join those parts). The main concurring opinion (by Stevens), which leaned more strongly against business-method patents, also only got 4 votes. Scalia joined a separate opinion by Breyer which emphasized the common points between the two opinions, but leaned slightly against business-method patents. It agreed with the majority that the "machine or transformation test" wasn't the sole test, but still thought it was the main useful one. That opinion also ended up with a list of examples of ridiculous business-method patents that are definitely not legit, so it doesn't seem Scalia would actually uphold most specific business-method patents that came across his desk.
10 PRINT CHR$(205.5+RND(1)); : GOTO 10
While Bilski lost, the Supreme Court did not throw out software or method patents. The Supreme Court actually re-opened the door just a bit after the Federal Circuit had left it cracked.
The actual majority opinion is only 16 pages long, and really doesn't say much. They more or less like the "machine or transformation" test that the Federal Circuit had come up with... wherein a method patent must tie any abstract ideas to a "particular" machine or transformation of matter, such that the abstract idea may be combined with other machines or transformations not protected by the patent. However, the Supreme Court now says that while this test may get the job done most of the time, it is not necessarily the only possible test (and they don't say what the other tests might include.
Most important for software patent watchers, the Supreme Court completely ignored In re Alappat and the impact of "Beauregard claims" on the Federal Circuit "machine or transformation" test. That older Alappat decision opened the door for patentee to write claims for software as being articles of manufacter. This "Bearegard" format is basically a sneaky trick... saying that you haven't invented software on a hard drive (which should be analyzed as a method), but rather you've invented a hard drive that has software on it (which should NOT be treated as a method). This is how most software still gets in the door, as the PTO gives it a wink and a nudge doesn't treat it as being "software" at all! This was the issue that software patentees were watching mostly closely, and Supreme Court was completely silent and left the status quo untouched.
Nice headline, but it does not reflect the total picture. This opinion is NOT a victory whatsoever for the anti-software patent crowd.
Contractions Motherfucker, do you speak them?
I still cannot find the droids I am looking for...
Most important for software patent watchers, the Supreme Court completely ignored In re Alappat and the impact of "Beauregard claims" on the Federal Circuit "machine or transformation" test. That older Alappat decision opened the door for patentee to write claims for software as being articles of manufacter. This "Bearegard" format is basically a sneaky trick... saying that you haven't invented software on a hard drive (which should be analyzed as a method), but rather you've invented a hard drive that has software on it (which should NOT be treated as a method). This is how most software still gets in the door, as the PTO gives it a wink and a nudge doesn't treat it as being "software" at all! This was the issue that software patentees were watching mostly closely, and Supreme Court was completely silent and left the status quo untouched.
While I agree with your other paragraphs, I disagree here for two reasons... Most software claims are not written as Beauregard claims, but as either method or system claims (or both), cause your second clause - that the PTO gives them a wink and a nudge - is incorrect. The PTO most certainly applies the machine-or-transformation test to Beauregard claims, and I've received several application rejections that cite the Fed. Circ's decision in Bilski against them. So, since we still have had to address that test, there's no reason to write a claim as a Beauregard claim when a method or system would work equally well and be arguably broader.
No. 08-964. Argued November 9, 2009--Decided June 28, 2010
Which is about the same as saying ( Justice Potter Stewart, concurring opinion in Jacobellis v. Ohio 378 U.S. 184 (1964)),
So, can I continue getting patents by adding "on the internet" to common sense operations?
You misunderstand the point of that phrase. It's a technique called claim differentiation and shows up typically in a dependent claim, the purpose being to expand the independent claim from which it depends. For example, say my independent claim is a new forward error connection scheme that involves receiving packets from a network, processing them using my revolutionary new error correction system and appending some sort of advanced hash to them [note: I personally haven't invented it yet, so please don't criticize me by saying "but error correction and hashes are known". This is just for example], and then transmitting the appended packets over the network. Then, in a dependent claim, I say, "The method of claim 1, wherein the network is the internet." Because the two claims, by definition, cover different things, the addition of the dependent claim means that the networks in the independent claim include the internet, but also include other networks - local networks, private networks, metropolitan area networks, wireless networks, wired networks, token ring networks, etc. It's purely useful in a litigation sense so that someone can't say "well, you were thinking of the internet when you said 'network' so when I do it over my corporate intranet, it's different and I'm not infringing."
Here are some quotes from my analysis (I'm the founder and former director of the NoSoftwarePatents campaign):
Again, here's the full text.
You'g. I'o wha'nt.
The stories and info posted here are artistic works of fiction and falsehood.
Only fools would take it as fact.
not necessarily the only possible test (and they don't say what the other tests might include.
You just made all Lisp programmers very, very nervous.
Is also worth reading. Basically, while this is not a hands down win for opponents of software (or business method) patents, the upholding of the older cases (Flook, Diehr, etc.) could give some guidance on future cases that may help them rule out abstract ideas and algorithms. Villa also talks a bit about how the lower courts may see this and how he thinks they may be handling future patent cases.
So that's how klingon was invented...
While Bilski lost, the Supreme Court did not throw out software or method patents.
If anything they suggested software and method patents have a place in "the Information Age", saying: "The machine-or-transformation test may well provide a sufficient basis for evaluating processes similar to those in the Industrial Age—for example, inventions grounded in a physical or other tangible form. But there are reasons to doubt whether the test should be the sole criterion for determining the patentability of inventions in the Information Age. As numerous amicus briefs argue, the machine-or-transformation test would create uncertainty as to the patentability of software, advanced diagnostic medicine techniques, and inventions based on linear programming, data compression, and the manipulation of digital signals."
What they say in the last sentence is actually false: it would not "create uncertainty" but rather almost certainly rule out patentability. This is the court giving a wink and a nudge to the new slavery: ownership of ways of organizing human beings.
Patents in their up-until-recently form were intended as protection for ways of organizaing brute matter, not living things and not in particular not human beings. Patenting business processes and ways of thinking (which in the Age of Functional Programming is transparently all that software is: mathematical functions that can be represented in their entirety as thoughts) is nothing but a "form of tyranny over the human mind."
Business process patents and patents on ways of thinking restrict humans in ways that if they were implemented by any other means would be considered obviously acts of tyranny.
The good thing about the decision is that it suggests the scope of such tyrannical patents is likely to be viewed as narrow, and the minority concurring decision has much stronger language on the meaning of "process" that leaves the door open to sanity and liberty carrying the day in the end.
Blasphemy is a human right. Blasphemophobia kills.
Translation: Congress, do your fucking job.
The world's burning. Moped Jesus spotted on I50. Details at 11.
you will find out that even greengrocers' apostrophes are not always wrong: they date from an age when new fruit and vegetables were appearing, and their customer needed to know that there was a difference between potato's and asparagus.
You know, if you cannot tell the difference between potato and asparagus then you might have problems that even an apostrophe cannot solve...
So... essentially the court accepted a case and then wasted everyone's time doing the USPTO's job, and declared the patent invalid in this specific case because it wasn't patentable material... Something the USPTO should have done in the first place...
No new precedent, no new tests, no new rules... So everything will stay exactly as it is, and the USPTO will continue to approve bogus patents just like this one... Great! I love America!