Patenting Open Source Software
dp619 writes "The tactic of patenting open source software to guard against patent trolls and the weaponization of corporate patent portfolios is gaining momentum in the FOSS community. Organizations including the Open Innovation Network, Google and Red Hat have built defensive patent portfolios (the latter two are defending their product lines). This approach has limitations. Penn State law professor Clark Asay writes in an Outercurve Foundation blog examining the trend, 'Patenting FOSS may help in some cases, but the nature of FOSS development itself may mean that patenting some collaboratively developed inventions is inherently more difficult, if not impossible, in many others. Consequently, strategies for mitigating patent risk that rely on FOSS communities patenting their technologies include inherent limitations. It's not entirely clear how best to reform patent law in order to better reconcile it with alternative models of innovation. But in the meantime, FOSS still presents certain advantages that, while dimmed by the prospect of patent suits, remain significant.'"
Reforming patent law would be simple, software should simply not be patentable. You can copyright it sure, but no patents.
I think it is probably a bad idea to rely on the expensive patent process to protect open source. Isn't it better to make the software available and visible so that it can be clearly established that it is prior art, i.e. already known by all, when someone tries to patent drawing rectangles on the screen, or whatever? I'm probably ignorant, but what's wrong with that approach? Is it less certain to succeed in a court, or is it possible to patent something that someone else has already done and explained how to do?
Why patent open source software - can it not be registered somewhere with a date stamp to prove it is prior-art?
I can envision a world in which the USPTO just rubber stamps everything coming in as an application and letting the courts determine which are valid or invalid. Wait, we have that system now.
Harrison's Postulate - "For every action there is an equal and opposite criticism"
Okay, then ask the same patent question about open source hardware.
Some people die at 25 and aren't buried until 75. -Benjamin Franklin
Read Stallman's 'Free Software, Free Society' or this well-written piece by Tom Wolfe on Patents: http://ikhider.com/wp-content/uploads/2013/02/Land-of-Wizards-by-Tom-Wolfe.zip Our patent system was originally conceived as a way to encourage creativity and inventiveness, but now relegated to whomsoever has the deepest pockets for lawyers. A corporation can take someone's idea and claim it as their own and win in a lawsuit simply because their law team is bigger. The patent system needs a serious overhaul.
"SO we bide our time, waiting for a purer kick to bloom and the future is still bleak, uncertain and beautiful" -GSYBE
the nature of FOSS development itself may mean that patenting some collaboratively developed inventions is inherently more difficult, if not impossible, in many others.
... and...
For starters, because of the collaborative, incremental nature of FOSS development, in many cases it would be difficult to determine who from any given community qualifies as a joint inventor. Only those that contribute significant material to the inventive concept embodied in the patent’s claims are considered joint inventors; those that merely implement the invention or that contribute only “prior art” material are not.
... are both entirely true. As the article notes, in order for a patent to be enforceable, all of the inventors have to be properly named on the patent - no extra inventors, and no leaving anyone out - and they all need to either assign the patent to a common entity, or agree to jointly participate in any lawsuit:
For instance, enforcing jointly owned patents in a court of law requires the unanimous consent of all joint owners.
So, yes, it would be difficult, if not nigh-impossible, to enforce these FOSS patents.
Let me repeat that...
Enforce these Free and Open Source Software patents.
There seems to be some fundamental confusion about purpose. And who are you going to enforce them against? The trolls, as the summary suggests? But they're trolls because they don't make any products, and if they don't make anything, then they can't infringe. So, what, in the name of "defending against patent trolls", Free OSS foundations are going to start suing manufacturers such as Microsoft, Google, Apple, or Red Hat?
All of that said, there is a very good reason the FOSS community should be filing patents - patent Examiners look to their own databases first for prior art. If FOSS inventors file patent applications, let them be published, and then abandon the application to the public domain, that will add to the set of available prior art and make it more difficult for trolls to get patents. And since you never intend for such applications to issue, they can be drafted and filed very cheaply: throw in your source code, your comments or flow charts or functional specs, slap a single claim on the end, and you're good enough to publish.
You don't need to patient open source software to protect it from patent trolls. you just write it and release it to the public. it then becomes prior art which invalidates any later patents.
I don't understand why patenting FOSS offers an advantage over its use as prior art. Is it a "mutually assured destruction" model, where e.g. Google wants patents to assert defensively? Or is it cheaper in the long run to have an explicit patent on something, rather than having to defensively assert it as prior art, if the patent office swing-and-a-misses it and grants an illegitimate patent to some other company?
"Ahh! I see you're in that indeterminate Schrodinger state where - oh, uh
It's not entirely clear how best to reform patent law in order to better reconcile it with alternative models of innovation.
I'm not the only sentient being here right? I mean, OK, what's the aim of patents? To give incentivize folks to release technology and ideas into the public domain with monopoly protections. FLOSS should be exempt from patents because it directly meets the goal of patents without desiring any damn monopoly at all.
Oh? What's that? How will businesses compete with the fully open software if they can't sue developers over patent infringements? PROBLEM FUCKING SOLVED.
Holding patents is a defensive measure in the following ways:
1. It places art in the public record which may later be claimed as prior art. Of course other publication may also server the same purpose.
2. The patent office eats it's own dog food, that is prior art in the form of patents seems more likely to be searched and cited than the general literature.
3, Patents in a particular field may discourage a competitor from filing patents or even working on the same problem.
4. Patents in a field may trigger mutually beneficial cross licensing opportunities rather than lawsuits.
5. Patents in a field may provide counter-suit fodder or also M.A.D. style deterrence that is sort of an informal mutual cross-license that is cheaper than an actual shit storm of lawsuits.
Isn't all software maths, and therefore not patentable, or does that not apply to open source software?
Get the programmers to write the code for peanuts.. then pay boatloads of money to the lawyers. Call it "open source". I personally like to hire programmers, sell software, and avoid lawyers.
Tax the corporations to fund it (just fine a miserable part of what they're regularly caught laundering every year). And then charge the corporaions (not people) copyright if they use it. When it steps into their doors, or money from it does. Let the charming taxmen care for that delightful task.
"Commons" patents necessarily belong to the people. Like drinking fountains do, in civilized coutries. Free to use, not to sell, rent, block, and so on. Except for the jerk that tries to back up a water truck to fill it (DoS). Inviolable, un-sellable, untransferable, etc. Much more difficult stuff is done all over the place, in standard practice.
Is there a need to patient FOSS? Can't it invalidate patents due to prior art, or did the first to file change all that?
You cannot solve a problem with the same mind that created it. Right now, the patent offices (on both sides of the Pond) are the problem. If prior art does not stop patent attacks, nothing will. Funding the enemy is the worst solution possible.
Nae king! Nae laird! Nae yurrupiean pressedent! We willna be fooled again!
When it comes to protecting FOSS openness it seems that patents are an imperfect tool to say the least. A patent is a legal lock. Typically one does not open doors with a lock only. It is possible, of course. But, ideally, what you want is a door knob, too. The Creative Commons has done wonders for copyright IMHO. What about a family of similar staged protective instruments in the place of traditional patents? It seems Congress might have to get involved (Spaghetti Monster preserve us!), but perhaps via executive action the Patent Office could simply lend its imprimatur to new legal devices that guarantee openness. Could the EFF advocate for such a framework? The idea of defending openness seems very prudent in the current environment. However with the wrong kind of patent protections the FOSS community might wind up on its own doorstep locked out of the very house it built.
"No fear. No envy. No meanness." Liam Clancy
This is risky because a white hat is only benign until bought by a black hat.
Why patent it at all? Even if what you have should not be patentable, but your country somehow allows for software to be patentable, why patent it at all?
Imagine that you make something available and you do not patent it. Somebody else sees it and patents it. Good for him. He just wasted a fuckton of money for something that can be easily proved as having previous art, BECAUSE it is open source.
If you want those patents to defend against other patents, beware of the following:
1) You need a LOT of money.
2) You are now fighting in the mud with the pigs. Only to realize after a while that the pig likes it.
Don't fight for your country, if your country does not fight for you.
So, if you can't beat 'em, join 'em?
What should open source programmers do in parts of the world without software patents?
I wasn't aware that OIN was patenting anything, rather that they were just a group that you could join and donate existing patents to or draw from in order to protect yourself when sued over patents - e.g. a patent pool for self defense. Members were required to not sue each other over any patents in the pool. Or did I miss something?
Truth is like the sun. You can shut it out for a time, but it ain't goin' away. - Elvis Presley (source: imdb.com)
> What should open source programmers do in parts of the world without software patents?
Nothing. If there are no software patents you can't be sued for infringement, right?