Slashdot Mirror
CA Releases Patents to OSS
simonfairfax writes "ComputerWorld reports that Computer Associates International has released 14 patents to the opensource community, following IBM's lead. From the article: 'CA said it is joining IBM in encouraging other companies to create an industrywide "patent commons" in which patents are pledged royalty-free to further innovation in areas of broad interest to developers and users of IT.'"
Wait a minute... If the open-source community now "owns" patents, what happens when they start using that new version of the GPL that prohibits use by patent owners? They won't be able to use their own code!
:)
Suckers
I'm your huckleberry
Looking through here, it seems like these aren't CA's lame ducks either...
The actual list of patents can be found at CA's website
Show this to your friends and family that don't know what a real hacker is
I read that as "CA Patents OSS"
I must admit that I have been watching this whole "released" patents thing with slight amusement. Doesn't it strikes to anyone that this movement essentially declares to do the same to innovation and market, what original patent system claimed (and actually did, too) to do.
What we have turned this system into, that we now engineer a ways around it now? (but at least it's actually pretty nice to see that needs and deeds of the smart remains the same over the time despite the corporate USA.)
Its a great thing that CA is giving open source these patents to help secure itself, but the long term solution here should be to avoid giving validity to software patents and fighting their existence. There has been success in europe on this front (although not entirely, I believe) and surely not having to deal with the patent minefield would be better than having a collection of defensive patents...
Business Voyeur
This is a nice gesture, but it won't address the real problem, no matter how many companies "donate" patents.
A patent pool could possibly help if it is actively defensive. In other words, it has to be structured like the GPL -- allowing some patent-pool entity to retaliate when a patent abuser like Amazon sues to enforce One-Click BS.
It could work such that by joining the patent pool, you get the right to use all of its patents but in return you have to place all of your own patents in the pool. (Unfortunately, there are many loopholes in this system, like creating multiple corporations to bypass the responsibility provisions... Also, it does nothing to address the "patent factories" who churn out hundreds of patents on basic concepts while selling no actual product.)
Anyway, the ideal solution is to get rid of software patents entirely. There is no reason for them to exist, except to allow people to monopolize ideas and hinder true invention.
That's nice and all, but is there actually any legal assurance that they won't change their mind and sue a developer for patent infringement at a later day? The cynic in me thinks it'd be a great way to get free labor -- promise a royalty free license to a patent and then wait for someone to write some useful code. When it's released, sue them and offer to settle if the developer turns all the code over to your company. It'd probably cost a lot less than actually hiring someone to do something useful with the patent.
I'm trying to teach myself to set people on fire with my mind... Is it hot in here?
This seems a pretty strange list to me: someone knows why they have chosen those 14 patents? They have a specific application/library in mind?
There's a hidden treasure in Python 3.x: __prepare__()
Lots of companies file patents they say are "defensive". That is, they say they won't prevent anyone else from developing the patented invention. They just need to fill the vacuum, getting a patent before someone else files an "offensive" patent which would be used to prevent others from developing that invention. But until the day comes when the "defensive" company changes its tune (maybe after changing ownership), we never can know whether the patent will be used offensively - and then it's too late.
What's wrong with releasing these patents into the public domain? We have a "fourth state", beyond the mysteriously dual states of "offensive" and "defensive" patents, and the vacuum of "no patent (yet)". Why do we need "an industrywide patent commons"? Why don't IBM and CA just release these patents into the public domain? They lose no more, and the "holding company" can't later be abused to control "submarine patents" that surface to catch entrapped users.
I'm sure that IBM's and CA's patent lawyers know more about the public domain than I do. They don't need me to think this up. But since we could get everything they're promising with a "public domain release", and they're not doing it, I suspect foul play.
--
make install -not war
It would be very cool to see another clause saying that organization wishing to take advantage of this patent protection must also license all of their software patents under the same (or compatible) terms.
Rather than taking RMS's short-sighted "no patents at all" approach, the GPL could use patent protection the same way it uses copyright protection to incentivise developers to open-source their software (and patents).
Such an apporach would give open-source software a huge advantage over its proprietary counterpart: not ony would OSS developers get access to a vast selection of source code, but they would have royalty-free access to use certain techniques that would otherwise not be allowed. This could have a very strong viral effect beyond the power that the GPL currently wields.
If RMS could have fought against copyright protection, he would have--after all, "information wants to be free," right? Lacking that option, he used his own copyright protection to force others to willingly give up their own. Software patents are a reality. Rather than fight impotently against the ideal, we ought to harness that protection to further the open-source cause. The earlier it takes hold, the more powerful the move will become.
I rather like the idea of the FSF patenting its more clever ideas to prevent them from being used by closed-source developers. Right now OSS makes it easier to develop open source, the effect would be better if they also made it harder to survive developing closed source software.
"With sufficient thrust, pigs fly just fine. However, this is not necessarily a good idea...."
RFC 1925
What's wrong with releasing these patents into the public domain? We have a "fourth state", beyond the mysteriously dual states of "offensive" and "defensive" patents, and the vacuum of "no patent (yet)". Why do we need "an industrywide patent commons"? Why don't IBM and CA just release these patents into the public domain? They lose no more, and the "holding company" can't later be abused to control "submarine patents" that surface to catch entrapped users.
A very good point. Originally, it used to be that most research at colleges, universities, and any federal or state authorities was - by default - created as a public domain patent. But sadly this is now regarded as IP (Intellectual Property), and zealously guarded by those same institutions that used to have it be free.
Sure, open source could use the revenue - and there will be revenue - from such private patents, but if they were released into the public domain it would free up innovation.
And freeing up innovation and creation is the whole point behind having a patent process in the first place. At least in the USA when they were created as part of the Constitution.
-- Tigger warning: This post may contain tiggers! --
the quote at the bottomb of the /. page:
Is it possible that software is not like anything else, that it is meant to be discarded: that the whole point is to always see it as a soap bubble?
Seems relevant.
A bad idea is a bad idea and should be opposed even if there would be some short term benefits to "do as they do". Starting to use patents would give this particular bad idea legitimacy and would only start another arms race. And we've seen how good that works for solving any problems...
I think it's great that people have the guts, stamina and principles to do what they think is the long term right thing even though it's not the easy path.
Software patents simple is a horrible and flawed idea and so it should never be acknowledged as a viable way forward.
Spine World
I read through the one about detecting that threads/processes have died, and wasn't impressed there either. It takes all that space to declare the following algorithm: ... hell, we wouldn't even know where to look. And does keeping competitors from using this technology have any result on the bottom-line (excluding patent royalties)? "Oh no, they can also find out if a process dies by querying the operating system via a documented interface -- our entire product line is doomed! We'll never be able to make money off our database server software!"
while(1)
{
ask operating system for list of processes / threads
compare to previous results
diff
new things are new
missing things are missing
store list for next pass
wait()
}
It even includes the term "periodically", telling me we're talking about polling for this information, not registering callbacks of any sort to actually trap the events exactly as they happen. And they patented this? "How to use an operating system's API to do exactly what that API was meant for"?
It's not a marketable patent, even. It's not like an entire car engine design, where the patent covers a large chunk of the final product. We can't point to the patent and say "you protected technology that you weren't relying upon to make money!" because it's so little
The software companies are only doing this so software patents aren't eliminated completely. By pretending that their useless patents on XOR are helpful to the Free Software community (and thereby looking like the "good guys"), they keep the "good" patents to themselves. If they didn't give away their worthless ones, people would start questioning the software patenting process, and probably eliminate it.
Don't support this. Vote to abolish software patents completely! If mathematics can't be patented, why can algorithms!?
My other car is first.
> But what if you are writing derived commercial applications?
:)
Assuming that by "commercial applications", you mean, "proprietary, non-free, closed-source, applications," then your situation is unchanged. You have no more rights to use those patents than you did yesterday, but nobody on slashdot gives a rat's ass about you anyway, so, so what?
(Actually, you are, I'm sure, perfectly welcome to negotiate a patent license with CA if you don't like the terms of their generous public donation. But I suppose it's more fun to whine on slashdot.)
Otherwise, the answer is, your commercial applications have to be free/libre/open-source commercial applications. Then there's no problem.
> any BSD or MIT license would be completely subverted
"Completely subverted?" What are you? The hyperbole fairy? Try "somewhat limited" and I might go along with you. I mean, when I've released code under BSD or MIT licenses, I've been assuming that it was so that anyone could benefit freely from the code. Not just people creating proprietary commercial derivatives. If I'd known it was just for propietary commercial derivatives, I probably wouldn't have bothered!
> The only way to clean up this mess is to overhaul the patent system (unlikely) or to release the patents to the public, *without* any restrictions.
Well, either, a) you're the kind of insane BSD fanatic who makes the Stallmanites look like moderates, or b) you're a greedy bastard who just wants other people to give him free money. I won't speculate which. But, needless to say, I disagree with you. Not that I'm not sympathetic to your point of view; but I still disagree.
The point about the impact of this (and IBM's patent grant) on BSD/MIT licenses is an important one, and I'm glad you raised the point. I just wish you hadn't resorted to such histrionics in doing so.
The real problem is that software patents are bad for everyone, except for large corporations that can agree to cross-license patent portfolios. This allows the large corporations to block small companies from even entering the software business and provides a weapon with which to attack OSS projects the corporations don't like.
It doesn't matter how many 'good guys' contribute patents to a patents common, as long as there are companies that are going to use patents as weapons in the marketplace.
Even more importantly, this doesn't address the fundemental problems with using patents on software in the first place. In a world with software patents, it will eventually become almost impossible to write code w/o having a staff of patent lawyers to make sure it isn't infringing. Eventually, the cost just to make sure code isn't infringing will become another barrier to entry for software companies. Patents and software aren't like oil and water, they are like Hydrogen and Oxygen. Sooner or later, they'll blow up in all our faces.
-All that is gold does not glitter - Tolkien
www.ra
What you're saying is true for copyright and the GPL but not for software licenses in general.
2 0050901_decision.pdf
Typical click-through software licenses limit what you can do with software. For example, reverse engineering is not allowed by most proprietary software. When you click, you are forming a contract, and these contracts do hold up in court as can be seen in the recent bnetd related decision.
So what the software vendors cannot control by copyright, they can instead control by contract, at least to the extent that a "breach of contract" civil suit is a threat to the user. For reverse engineering, for example, the liability can be quite significant, even without the kinds of statutory damages that copyright law provides for.
http://www.eff.org/IP/Emulation/Blizzard_v_bnetd/
-- John.