IBM's Supreme Court Brief Says That Patents Drive Free Software
H4x0r Jim Duggan writes "For the Supreme Court's upcoming review of the Bilski decision, IBM has submitted an amicus brief claiming that software patents 'fueled the explosive growth of open source software development' (!) (p38 of linked PDF). EndSoftwarePatents, for its own amicus brief, is looking for help building a list of free software harmed by software patents, and a list of companies that distribute free software and are taxed by patent royalties."
software patents 'fueled the explosive growth of open source software development
I guess we know which side IBM is on. Too bad.
The following phrases are among the few common uses of the word "patent"
as an adjective:
"That is patent nonsense."
"That is a patent lie."
Where are we going and why are we in a handbasket?
that IBM is an altruistic company? Of course their comments will be self-serving as the number one patent submitter for years. They have mastered the game of patenting everything and they are not about to let that mountain of assets go.
Patents drive them straight into the ground.
Want to improve your Karma? Instead of "Post Anonymously", try the "Post Humously" option.
Pirate it.
Piracy is not theft.
If you want to say "a legal copy", then sure.
Thanks to patents, there are numerous alternatives to the MP3 format.
Thanks to that GIF patent (now expired), there is PNG.
So yes, patents drive development by "encouraging" people to re-invent a different, maybe better, wheel.
I'm not against *all* patents. Some algorithms have a serious amount of R&D and ingenuity behind them.
The problem is the BLINDINGLY OBVIOUS and TRIVIAL things that are being awarded patents.
Examples:
A special comparison operator for pointers: http://appft1.uspto.gov/netacgi/nph-Parser?Sect1=PTO1&Sect2=HITOFF&d=PG01&p=1&u=%2Fnetahtml%2FPTO%2Fsrchnum.html&r=1&f=G&l=50&s1=%2220040230959%22.PGNR.&OS=DN/20040230959&RS=DN/20040230959
Encoding of floating point numbers as non-negative integers: http://appft1.uspto.gov/netacgi/nph-Parser?Sect1=PTO1&Sect2=HITOFF&d=PG01&p=1&u=%2Fnetahtml%2FPTO%2Fsrchnum.html&r=1&f=G&l=50&s1=%2220050023524%22.PGNR.&OS=DN/20050023524&RS=DN/20050023524
Policy change notification: http://patft.uspto.gov/netacgi/nph-Parser?Sect1=PTO1&Sect2=HITOFF&d=PALL&p=1&u=%2Fnetahtml%2FPTO%2Fsrchnum.htm&r=1&f=G&l=50&s1=7,269,853.PN.&OS=PN/7,269,853&RS=PN/7,269,853
There's zillions of them and I'm pretty sure that every line of code being written today violates at least one. It's the equivalent of allowing copyright of individual English words.
No sig today...
Would libpng have been written, if not for the LZW patent? How about all of xiph's codecs? We wouldn't have Vorbis if it weren't for the MP3 patents.
All that's really left to debate is whether this project, that project, etc all add up to something that counts as "explosive growth." And at that point, it's just not an interesting question.
Saying patents fuel software development (both free and proprietary, since both types are actually harmed by patents) may be a distortion, because it (misleadingly) implies that the patents help the overall situation, but on its face, the statement is literally true. Patents force people to work around patents. It's economically inefficient (just as hurricanes fuel the construction industry) and therefore probably not desirable, but it really does happen.
As copyright owner of this comment, I authorize everyone to defeat any technological measure which limits access to it.
TFA says:
patent protection has promoted the free sharing of source code [...] which has fueled the explosive growth of open source software development.
Here's the quoted footnote from the Amicus brief:
See, e.g., In re Alappat, 33 F.3d 1526, 1571 (Fed. Cir. 1994) (Newman, J., concurring). Given the reality that software source code is human readable, and object code can be reverse engineered, it is difficult for software developers to resort to secrecy. Thus, without patent protection, the incentives to innovate in the field of software are significantly reduced. Patent protection has promoted the free sharing of source code on a patentee's terms -- which has fueled the explosive growth of open source software development.
The emphasis on "on a patentee's terms" is mine, and the phrase omitted from TFA is vital to the meaning of the sentence as a whole. I believe Adobe's release of the Portable Document Format specification is a case in point. Adobe made the specification available with the stipulation that it not be used to develop products that compete with Adobe's products. The open specification allowed the development of all kinds of open source tools (as well as closed-source tools) that make PDF much more useful to everyone, yet Adobe is protected from having its development investment and future business stolen.
"Who controls the past controls the future. Who controls the present controls the past." -- George Orwell
They actively employ people to use open source, and foster it's development, and yet they are supporting patents? Am I missing something in that general concept?
I mean what about employing people to support open office and lotus symphony and all that, which is all expressly supported by IBM?
There could be aspects of the Vorbis codec that are patented, but no one knows as no one (for good reason) is looking. VP3 was written well before it became Theora, and unfortunately is in the bad position of being inefficient.
But let's consider what we don't have because of patents? How about wavelet compression, and the adoption of JPEG2000? Completely ground to a halt as one company holds a slew of patents over it.
Yes, patents force people to work around them. They're stuck reinventing the wheel, poorly, and remain at risk of patent suits. The problem with software patents is they're either so stupidly simple that everyone runs over them (and strive to remain ignorant of having done so, to lessen any possible damages) or are so vague that they cover huge swaths, denying entire fields and crippling compatibility.
Obviously EndSoftwarePatents needs specific examples of how companies are being hurt. So far I don't see any examples posted here. It depends on what is meant by "harmed". Does this mean they have lost a court case? Perhaps the best example is IBM's own court expenses in the case brought against them by SCO. No, that was alleged copyright infringement, not patents. I guess a proper example is how the vfat filesystem in Linux has to dance around with short and long filenames. That's not on the list yet.
With copyrights, people loose productivity all the time by having to actively avoid looking at certain pieces of code for examples or ideas of good implementation. But with patents it's more of a sinister fear that any idea you come up with might be illegal to distribute, or "speak", because someone else might have patented it. You can't do anything about that other than live in fear, since there's no process in place to automatically avoid patent infringement. Maybe existing patent law could be argued as impinging on free speech! Okay I've rambled enough already.
IBM's brief does not define "open source." The open source references in the brief are not supported by much in the way of reasoning or argument.
Here's what I think IBM is saying:
If we get a patent, we don't have to keep our source code secret any more--we can now disclose our code to everybody. That's open source!! The source becomes open when we put it in our patent materials! We still have a monopoly (because of the patent), and we can sell our monopoly product any way we want. But now the stuff is OPEN!! That's good for development . . ..
IBM is technically correct in using the term "open source" in this manner. "Open source" means different things to different people. It obviously means one thing to IBM and its lawyers and a different thing another to Stallman and the FreeBSD crowd.
IBM wants a world where it can lock up the use of its software completely (via patent), except for when it CHOOSES to open source it.
This bugs me. It seems to me that if I buy a computer, I ought to be able to freely express myself via algorithms that I independently discover. For example, if I discover a unique algorithm that enables me to very effectively conduct political speech with my computer, IBM shouldn't be able to foreclose me from using my computer (a communication device) in that manner.
They wouldn't need to be written if not for those software patents. Instead, those developers would have spent their time writing something new. Very good example of how patents have retarded growth.
Isn't this reasoning similar to the Broken Window Fallacy?
If MP3 didn't have patents, we wouldn't have ogg, true. Which means the talent used to REINVENT THE WHEEL in the ogg codecs would have instead been used to improve the patent-free MP3 instead (or to work on other projects).
No sig for the moment.
Instead of exclusively considering prior art, we should give the public a chance to respond to every patent application by being given a description of the device, and have an opportunity to develop an invention to the device.
This would break the patent system. The goal is not to reward people who solve seemingly intractable problems. The goal is to foster innovation by providing those who innovate with a lock in their inventions. Innovation is often accomplished in small steps. The paper clip was just a way of using wire to hold papers together. Given its description, you could make a paper clip, but the insight and innovation were rewarded with a patent.
When we discuss software patents, there's a new kind of problem. Software is, inherently, an expression of mathematics. Patenting math is tough to accept because you can't change the way math relates to the real world, so you're essentially patenting a piece of the known universe... which doesn't make a lot of sense.
Public key crypto is about the only thing I can see as a defense of patenting software. Here, you're patenting, not the math, but the application of the math to a specific problem domain to perform a task.
But the question is, how do you move from that to a patent system that can discern the difference and make the right call? Fundamentally, I think you need a review system which is populated by real academics and professionals or it simply can't work.
EndSoftwarePatents, for its own amicus brief, is looking for help building a list of free software harmed by software patents, and a list of companies that distribute free software and are taxed by patent royalties."
Essentially, their argument hinges on the preamble of Art. 1, sec 8, clause 8 - "To promote the Progress of... useful Arts," and the claim that if software patents stifle innovation, then they're unconstitutional. Problem is, we're not dealing with a fundamental right or an equal protection argument, so the Court will use a rational basis test - could Congress have had a rational basis for passing 35 USC 101 and not excluding software patents? If so, it's constitutional. And the Court always defers to Congress on stuff like that. Asking the Supreme Court to add a software exclusion into Title 35 on a constitutionality argument would be asking them to be "activist judges". And that just isn't going to work.
Want to change the patent statute? Lobby Congress. They have full authority to do anything. There's not even a Constitutional requirement that patents exist - the clause merely gives Congress the power to enact patents, if they want to. But they don't have to. They could outlaw all patents tomorrow and that would be Constitutional (caveat - may have a due process issue for the next 20 years over people who filed for patents already, but that's a separate issue).
Just because one person defined a term doesn't mean that all people have to use the term in that way--especially lawyers writing legal briefs. Lawyers twist meaning. That's what's going on here. IBM wants to enlist the cachet of "open source" in aid of its argument. It's as simple as that.
Think about who the IBM lawyer is writing for: The lawyer is writing for the US Supreme Court. Do you think that the Supreme Court will accept the doctrine that the Slashdot meaning of "open source" is the meaning that the Supreme Court must adopt? The definition of "open source" is flat-out fair game right now, and if you assume otherwise you're just a zealot or fanboi.
I'm suggesting that IBM is using the term in a manner different from that used by the FSF/FreeBSD people. The FSF/FreeBSD people need to take that context into account when they frame their argument against IBM's argument.
I seem to remember in the early days of the web, there was a graphics format called GIF. Somebody like Unisys held a patent on the format, but initially didn't seem to care that most Web users didn't realize there was a patent. Then, one day, Unisys woke up, changed their attitude and announced that licenses would be needed from now on - several thousand dollars? Almost overnight, PNG was born. So, I guess in a sense, IBM has a point - patents lead to open source development. However, they neglect to mention that in cases like ReportLab (makes a Free/Paid Support PDF generator library in Python) a sudden change in licensing policy might result in innovation at the expense of existing innovators.
Patents are a valuable part of a thriving commercial system, and there are obvious benefits from patent law. But I think there are also significant benefits from patent-free zones. The trick is to figure out how to maintain the balance to ensure fairness, and enable benefits from both patented innovation and patent-free innovation.
Lemme fix that for ya:
If not for the LZW patent, libpng would never have been needed to be developed. Were it not for the MP3 patents, we wouldn't have needed Vorbis.
Necessity might be the mother of all invention, but in this case it was artificial necessity. The inventions were only necessary to get around the brick walls created by the patents. Tear down the unnatural brick walls, and the innovation could have focused on incrementally improving those existing techniques instead rather than essentially reinventing the wheel just to bypass them.