Patent Pools and Pledges - Panacea or Placebo?
I've been wary of those patent pledges and pools from the beginning. There's an awful lot of dishonesty in these all-too-obvious attempts to curry favor with the community and reassure customers. While the jury is still out on some of those projects, none of them has so far delivered a single compelling reason for me to believe that they're really going to be more than a placebo. Some make it sound like these pools are a bulletproof vest for open source, but it's more like you have a coin in your pocket and hope that a bullet will be deflected by it. Too bad the coin isn't even in a place where someone would usually shoot you.
While I do agree that open source should protect itself as best as possible within the legal framework that exists, cheap PR plays are not a substitute for a real solution. The pledges that I've seen so far had all sorts of shortcomings:
- Some pledged patents are of little or no value. Among IBM's 500 patents "contributed" in January, there were some that had nothing to do withsoftware, and many were up for renewal soon, with no guarantee that they'd actually be renewed.
- The pledges typically just relate to particular open source licenses (sometimes rarely-used ones) or projects, such as the Linux kernel (which is only a small part of a standard Linux configuration).
- Some pledges are revocable or haveloopholes such as vague conditions under which the patent holder can sue you anyhow.
- So far the quantities of patents involved have been negligible compared to the total number of issued software patents, and even to the number held by the "generous donors." Even in the long run, there'll be hundreds of thousands of software patents in the world that aren't subject to any pledge. In his speeches, Richard Stallman likens software patents to mines in a park: If there are 90,000 mines in the park instead of 100,000, it's still far from being a safe place to walk.
Even if you don't look the gift-horse in the mouth, there are fundamental problems that even the best pledges can't solve:
- You can't practically go about your programming job by always looking up a patent pledge database whether it contains just the algorithms you need. I don't think any programmer would seriously do that! And even if algorithms A and B are covered by patents in a pool, there may be a patent C that covers your particular combination of A and B, and that patent C may not be in the pool.
- Pledges which exclusively relate to open source aren't too valuable. Software under the BSD license is used in closed-source projects all the time. A project like PostgreSQL, which already felt forced to replace a caching algorithm due to an IBM patent, couldn't just base its development decisions on open source considerations alone. Then there are dual-licensing models for GPL software (MySQL is a well-known example) and companies that sell closed source software to finance their open source development efforts.
- These pledges are only made by organizations that don't intend to sue open source projects anyway. Patent holders who are potentially hostile, be it for strategic or purely financial motivations, won't pledge anything. It's nice to firm up the commitment of your allies not to act against you, but it doesn't reduce the number of enemies.
- If a company promises not to sue open source projects over a certain set of patents, it still doesn't mean that those patents can be used by open source projects for retaliatory purposes. However, the patent game is one of mutually assured destruction, like in the Cold War. If NATO hadn't had a single nuclear weapon, and the Soviet Union had promised not to use something like 5% of its nuclear arsenal, then we probably wouldn't live in freedom now.
- Companies usually can't even make their patents available for the purpose of building a counterthreat because those patents are already subject to existing cross-licensing agreements. If a new entity (such as the Open Invention Network) started acquiring unencumbered patents, then one day they might be able to grant a license to a company like Microsoft in exchange for a covenant not to sue Linux with its own patents. That could indeed make a major difference (even if only for Linux), yet it wouldn't help against trolls that have no products of their own. And a strategic aggressor could secretly arrange for such a troll to do the job.
No matter how you look at it, the only way to reliably solve the problem is at the political level: through legislation that excludes pure program logic from the scope of patentable subject matter. Sure, there's no shortage of people out there who say this can't be done, but they're all wrong. We've been toldmany times that the European software patent directive would come one way or the other -- until we got the European Parliament to reject it by a landslide of 648-32. The German Bundestag and Spanish Senado unanimously backed our central demands. The new German government has just vowed to counter, at the international level, "the trend to seal off markets, among other things by means of patent law." The time is ripe for legislative action.
Some members of the legal profession claim that software patents are an unalterable fate because theyhave a vested interest in sustaining the system. It's a tall order, but definitely possible, to change the legislative framework in our favor. In every parliamentary democracy.
Especially in the field of software, the patent regime no longer serves the public interest. In a perfect democracy, software patents would already be history. In the suboptimal democracies in which we live, there are special interests that oppose changes. Those have influence and deep pockets, but at the end of the day the most valuable currency in politics is voter popularity.
If all the companies who have pledged patents to open source, or who have contributed to those pools, decided to seriously campaign for legislation that abolishes software patents, then the problem could be solved for good. As long as they don't do that, they're not for real. Some may even have a hidden agenda of creating patent pools to gain effective control over the open source universe. We've got to watch out.
Florian founded the NoSoftwarePatents.com campaign. For his political efforts against software patents, he has been named as one of the "top 50 most influential people in intellectual property" according to Managing Intellectual Property magazine and is a candidate for the title of European of the Year.
my brain...
Won't touch it - too much "P" in the headline
"However, the patent game is one of mutually assured destruction, like in the Cold War. If NATO hadn't had a single nuclear weapon, and the Soviet Union had promised not to use something like 5% of its nuclear arsenal, then we probably wouldn't live in freedom now."
The topic title taught us terminology.
Patent MAD seems like the only way to get to be a big company these days. With the dot com boom over, what else could possibly take a small company and make it competitive with a giant like ebay.com? Skype got bought out by who else? Ebay.com
A giant like eBay with their mountains of patented software stands to make a fortune every time someone else tries to write some of their own software to sell something on the Internet.
Saskboy's blog is good. 9 out of 10 dentists agree.
Not to say it's a PR "stunt" or "trick", but it makes certain vendors conspicuous by their absence from these groups. If you've got a town where there's a big organization pledging to protect the environment, but the biggest company in the town isn't signing on, it leaves an impression.
My turnips listen for the soft cry of your love
It appears that there is prior art preventing this patent.
Companies usually can't even make their patents available for the purpose of building a counterthreat because those patents are already subject to existing cross-licensing agreements. If a new entity (such as the Open Invention Network) started acquiring unencumbered patents, then one day they might be able to grant a license to a company like Microsoft in exchange for a covenant not to sue Linux with its own patents. That could indeed make a major difference (even if only for Linux), yet it wouldn't help against trolls that have no products of their own. And a strategic aggressor could secretly arrange for such a troll to do the job.
The problems with intellectual property of all sorts (copyrights, patents, trade marks, service marks) stem from a fundamental belief that competition is the most efficient mechanism for progress. This belief means that government's role is to protect players from excessive competition by granting intellectual property monopolies. Unfortunately, this has the side effect of strengthening the cultural forces against collaboration. Open source software development, which is fundamentally a collaborative model (collaborate to build code, collaborate to share code, etc.), is showing that such a model can be successful. However, given the competitive intellectual property culture, open source models are extremely vulnerable. My thought: over the course of the next few decades, the software world will become a proving ground to demonstrate that collaborative economic models are superior to competitive economic models. However, the vested interests in the competitive model will only very slowly come around to embracing the collaborative model.
Helping with organizational effectiveness is our job.
If your company gets sued because someone successfuly patented the double click which is used in your Linux servers, because the patent is so friggin' ridiculous, couldn't you sue the patent office? Take contracts, for example: If you were running a jetskiing operation and you had people sign a ten page fine print agreement basically saying not to sue for any reason, and for kicks you removed the throttle spring so they can't slow down (not using any bomb like in that movie), contracts may not hold up. And I'm not talking just contracts that include something illegal to be entirely void, just contracts that cross the line of reality a bit too far. Apply that to patents, and you got a viable case. Right? Any precedents one way or the other?
Always avoid alliteration. Artificial amateurs aren't at all amazing.
Just me wondering, how well do patents work in general?
FT...A...C[ommentary]: "And even if algorithms A and B are covered by patents in a pool, there may be a patent C that covers your particular combination of A and B, and that patent C may not be in the pool."
1) Wouldn't prior art mean that C isn't legal unless the person/company holds patents A and B (in other words, couldn't patent holders A (inclusive) or B go after patent holder C for infringment?)
2) In closed source, how can it be determined (legally) that someone is infringing on another's patented algorithm?
If the later can only be determined in free software, then doesn't that mean that a strict patent enforcement system wouldn't benefit anyone but closed source programmers?
That being said, I don't know a thing about patents, and they kinda scare me (I picture a patent-boogeyman when I think about it) or is that what they are supposed to do?
Am I open minded towards open source, or closed minded towards closed source?
The points that are most valuable (IMHO):
- "Some pledged patents are of little or no value." Right. Primarily, IBM (and others) gain some PR joy by releasing these patents either shortly before they expire, or namelessly in a group so the statistic (more than 500!) sounds better.
- "So far the quantities of patents involved have been negligible compared to the total number of issued software patents, and even to the number held by the "generous donors."
...Richard Stallman likens software patents to mines in a park: If there are 90,000 mines in the park instead of 100,000, it's still far from being a safe place to walk." Right. Of course, it begs the question: how many of the 90,000 are actually dangerous? Sure, there are zillions of software patents out there, but how many of them are actually desirable to anyone else?
The real question is, how do you reward software ingenuity and creativity if you cannot patent something? Is it enough to make money? That's somewhat meaningless in the OSS community, where fame/notoriety/goodwill may be more important..
.
$nice = $webHosting + $domainNames + $sslCerts
In a perfect democracy, software patents would already be history.
What could be the reasoning behind this statement? If a perfect democracy means that the issue would be put up to a vote, with the majority opinion carrying the day, I'm not quite as sure as you that software patents would be history. Consider all those people who have a vested interest in maintaining the status quo - we know how they would vote. Now consider the software developers themselves (a tiny demographic) - I would guess that most would vote to abolish software patents, but some (maybe even many) would vote to keep them in place (after all, they write code and may not want others to use it freely). That leaves the big blob of people who know nothing about the issue. How would they vote? I would suggest they would be easily swayed by "campaign" advertising. Now, who has the money to run the campaign - the ones with the vested interest or the software developers?
Now perhaps you believe that a perfect democracy does not leave room for campaigning or advertising to sway opinions. If that were the case, given the large unwashed mass's lack of understanding of the issue one would have to assume their vote would split 50/50. So, in the end I don't see a perfect democracy changing anything.
The more you regulate a company, the worse its products become.
I hope software patents stay around for a while, in the USA that is, simply for the fine job they are doing in discrediting the entire concept of patents. A few more years of this madness and it will be ripe for abolition.
Seems to me that a patent pool that accepts patents under a license obligating the pool not to enforce the patent, and offering anyone a free, unrestricted license to use the patent, is harmless. It's also indistinguishable from "public domain" in operation, but has the valuable bonus of an interested party which can actively fight others who try to privatize the patented IP. The public domain is a great legal principle, but the economics fail to protect the public - "tragedy of the commons".
Funding the "public patent" pool is a challenge, but a sufficiently diversified and pushy pool with lots of profitable licenses can probably pressure "association members" for enough money to operate. Or sell "value added services", like IP legal advice and "IP market info", like licensing activity. Maybe just a virtual organization, cheap in normal operation, that pulls dues from licensees only when they vote to challenge a rival IP claim to their free patent. If legal, possibly after the fact, when someone licenses a patent that had meanwhile been conflicted by a new, private patent. The economics of that operation might see a "reverse claim jumping" industry, where people spot unlicensed public patents in conflict with newer private patents. They license the public patent, then fund the suit against the private rival, which seizes the private income for the pool, compensating the new public licensee.
The power of this way of thinking, a real libertarian method for fighting private IP hoarders, offers a lot of new operations in the public interest, entirely consistent with private capitalism, while excluding monopolism. Let the good times roll!
--
make install -not war
This year, we've seen a variety of initiatives by companies that "donated" patents to "protect" open source, and organizations like the OSDL and the Open Invention Network now try to pool such patent pledges.
Wouldn't it be more effective, then, to divert our focus away from spreading publicity for these pro-OSS patent groups, and to try to persuade these companies to release their patents into the public domain for all to use (or in the case where the corporation does not wish for commercial reuse of their patents, to license them under a GPL-style license)? Like the poster, I'd be wary of trusting anyone that simply said "we promise we won't sue".
Of course, this assumes that the PTO/courts/etc. agree that the public domain release constitutes prior art.
But it does bring the issue out for more open debate. Given the WIPO's attempts to dissuade public debate, that can't be a bad thing.
... because they have all these limitations applied by the 'donators'.
... and then some action whould have need to be taken, otherwise GPL spreads like bird flu.
One single nasty patent (think EOLAS, think Forgent) may be enough. Just license it only to software that is licensed under the GPL, and enforce that using a horde of lawyers
What about adding a clause like this to both LGPL 3 and GPL 3:
By using this software you agree never to initiate a software patent lawsuit against any person or company. If you do initiate such a lawsuit, the license fee is $1M per year, retroactively, and you are defined as "aggressive". There is one exception to this rule: Anyone may initiate software patent lawsuits against others who are aggressive.
This has the effect of even making life difficult for litigation companies: As more and more software includes at least LGPL code, over time they would have to run their companies without the use of software of any type.
How would you sue an open source project for patent violation? Suppose there was patented code found in the kernel, who do the litigants go after? Linus? The author of the code?
-Scott
My other sig is a Glock
I think some kind of patent pool is necessary, but I want to see it run by the open source types. We should have a foundation which patents methods used in open source software as they come out, then places them in a defensive pool like the ones the corporations use. The licence could be viral: use may use these patents in any project which is open-source, and if you grant the same licence to everyone to use all your software patents. It's a stopgap, but until we get the laws fixed, we need something to prevent innovations developed by the community from being patented after the fact by big companies. I know that means there would be prior art, but since when has that been any impediment to a patent? Microsoft knows that many obvious things, like organizing photos in chronological order, are patentable, and will patent them untill open-source software is crushed. We have to fight back both within the existing legal system, and by changing it.
SW patents do mean shit in China and in 15-20 years they will be dictating terms because they will have most of the wealth.
All that needs to happen is for one critical app to be created in China that many corps want/need but couldn't create due to SW patents. When that app is sold/licensed/bartered around the world, all the SW patents in the world won't stop it.
Don't believe me, look at the Blackberry Patent suit. In the US, even if RIM looses, the US government will still be *allowed* to buy and used blackberries in the US. Patents means nothing if the need/want is there.
Obama's legacy: (N)othing (S)ecure (A)nywhere and (T)error (S)imulation (A)dministration
"When cross-licensing or pooling arrangements are mechanisms to accomplish naked price fixing or market division, they are subject to challenge under the per se rule. See United States v. New Wrinkle, Inc., 342 U.S. 371 (1952) (price fixing)"; Antitrust Guidelines for the Licensing of Intellectual Property, U.S. Department of Justice and the Federal Trade Commission (1995)
"[T]he right to exclude others from profiting by the patented invention" is "the essence" of the patent grant." Dawson Chem. Co. v. Rohm & Haas Co., 448 U.S. 176, 215 (1980)
Waiving the right to exclude is the equivalent of fixing the price at "no charge". Pooling patents at "no charge" is price fixing.
"That would be no more permissible than a contract between a copyright owner and one who has no copyright, or a contract between two copyright owners or patentees, to restrain the competitive distribution of the copyrighted or patented articles in the open market. Interstate Circuit, Inc., v. United States, supra, 306 U.S. page 230, 59 S.Ct. page 476. As stated in Standard Sanitary Mfg. Co. v. United States, supra, 226 U.S. page 49, 33 S.Ct. page 15, rights conferred by patents 'do not give any more than other rights a universal license against positive prohibitions. The Sherman law is a limitation of rights, rights which may be pushed to evil consequences, and therefore restrained.' "; UNITED STATES v. MASONITE CORPORATION, 316 U.S. 265 (1942)
BTW: I meant don't mean shit.
Obama's legacy: (N)othing (S)ecure (A)nywhere and (T)error (S)imulation (A)dministration
This is a favorite topic on ./ and I agree, as most everyone does on the broad issues.
But, I'm personally tired of the hand-wringing, rah-rah, something-must-be-done, generally lacking in any sort of content items like this. Here are some options:
1. Slashdot makes a new category: Things most viewers agree on. You can put the Evil Empire, Linux is Great and Patents are Bad stories just like this one in this category. It will be a popular category.
2. Do something. How about learning how to avoid patent entanglement? If your method is different than the patent, then when the lawyers come knocking, can you turn them away? Not like Kryptonite to Superman, but they will have to back down. How about learning how to defeat a patent? How about a little local anti-patent advocacy?
3. How about a patent map? There are plenty of smart programmers here, come up with a way to make a patent directory. It's nowhere near easy, but I'm sure there's quite a few people smart enough to get *something* going.
C'mon people do something about it.
http://www.maxineudall.com/2010/02/should-economists-be-sued-for-malpractice.html
Let me provide you a couple of scenarios.
Scenario one: I'm writing software. I come up with a brilliant idea and put it in my software. When I release it, someone pops up with a patent and says I have to pay royalties.
Scenario two: I'm writing software. I come up with a brilliant idea and put it in my software. When I release it, someone else steals my idea for their own software and releases a competing product.
Both of these scenarios are clearly wrong, but no patent plan thus far has dealt with any way to prevent both cases. Overuse of software patents creates the first scenario, while lack of software patents creates the second.
What most bothers me is that the people screaming "no software patents" are never going to have one ANYWAY. They are not brilliant original thinkers, they are primarily wage slaves and open source advocates; they want the ability to grab and use *anything* that looks like it might fit when they have to build something. There is nothing wrong with that; brilliant original thinkers are rare, and while we would all like to believe that group includes us, we are all probably wrong.
But some of us really do have a significant potential to create something that takes a long time to invent, but not much time at all to copy. I have a product in development right now that is absolutely revolutionary; nothing out there is even remotely close to it, and I think my target market is going to just go insane wanting it once they see how great it is. (I could be wrong, and... as I mentioned above... I probably am.) But once you see the product, you know exactly how it works. If you have a reasonable competence in the appropriate field, you could build it yourself. I spent four years making it out of nothing, but it would take a competitor maybe a month to bootleg it.
That's why patents exist. A patent is designed to protect *exactly* this situation. The problem is that they are not being used this way.
My solution to the problem is simple: patents should cost a percentage of what they earn the owner. Not a huge percentage; something tiny. The patent owner could simply list all of his licensees and the gross revenue they generated, and pay (say) 20% of his most profitable year over the life of the patent. Each year, he simply calculates his 20% and subtracts what he's already paid.
Essentially, the protection of the patent gives the company which owns it a certain monopoly power, which inevitably raises the market price. Since the company will therefore make more money over the life of the patent, the government should charge some of that revenue back. Over the twenty years that patent is in force, you'll pay between one and twenty percent of your revenue, depending on how lasting and enduring your idea is. If you have a novel little flash-in-the-pan idea, you pay closer to twenty. If you have a brilliant and useful idea, you pay closer to one. This gives the inventor a form of automatic patent fee relief when his invention is truly of lasting value to the world.
Filing fees can stay, so people don't file patents for no good reason, but we should probably reduce them enough for people to *afford* a patent. Between the search and the application and the filing fee and all the attorney fees along the way, getting a patent COSTS, and I'm not exactly struggling. The old man in the basement with a fantastic idea can't even *begin* to think about getting a patent, and that's just plain wrong.
Add to this a burden on patent holders to demonstrate probable intent to infringe before prosecuting infringement... and the patent system is pretty much fixed. I don't think that's a massive change. I don't think anyone who really deserves a patent on something will complain about it.
What we really want from the patent system is protection for useful inventions from inventors, not for endless strings of crap from major corporations. Make the endless strings of crap pay more, and the corporations will be less interested in patenting them. Place a r
Microsoft cheerleader, blue flag waving, you got a problem with that?
There are some really good reforms that could take place, short of giving up the goal of abolishing the patent system altogether. A list of a few is given at this post on China's entry into tighter patent law. My favorite? The Independent Invention Defense.
In a representative democracy, the elected representatives of the people should represent the interests of their electorate. On a specialized issue such as IP policy, that would include conclusions from the results of independent research as well as listening to a representative selection of the people affected by a measure, not just to the lobbyists of a few large corporations and the industry associations that they effectively control.
I need to add an explicit disclaimer to the licenses in my open source project about who is responsible for licensing any patents my stuff will likely end up infringing. So the answer to your question is it won't be me. Since the patents in question are applied for or owned by IBM, it will be interesting to see if IBM will sue for patent infringement by an open source project.
...thoughts typed out in code are not?
You can copy each other's software and modify it as you please as long as you share the wealth / credit - but this is something that is inherently contradictory to hard-core capitalism. In a system where you have lawyers representing lawyers over who owns what and when, it is really hard to get around patents and the greed that inevetibly comes with them. (see http://www.thecorporation.com/ or http://www.rottentomatoes.com/m/corporation/) Patent pools may only lead to more litigation about how they were used or abused.
From the Creative Commons licensing restrictions under 4C:
If you distribute, publicly display, publicly perform, or publicly digitally perform the Work or any Derivative Works or Collective Works, You must keep intact all copyright notices for the Work and give the Original Author credit reasonable to the medium or means You are utilizing by conveying the name (or pseudonym if applicable) of the Original Author if supplied; the title of the Work if supplied; in the case of a Derivative Work, a credit identifying the use of the Work in the Derivative Work (e.g., "French translation of the Work by Original Author," or "Screenplay based on original Work by Original Author"). Such credit may be implemented in any reasonable manner; provided, however, that in the case of a Derivative Work or Collective Work, at a minimum such credit will appear where any other comparable authorship credit appears and in a manner at least as prominent as such other comparable authorship credit.
Stifling innovation is not what the IT world needs or wants. Would I even be able to write this posting if someone had patented comment fields, html code and text-boxes? The internet is a perfect example of why you should not patent everything, simply because it will lead to the greater good of the community. After all, if you are worth billions of dollars and have acheived many things in your life, why do you need to keep making tons of money by patenting anything with a potential profit? It is the ruthless capitalism game you are playing, the rules that dictate how you MUST play it, and the mind-set it creates while playing the game.
He who knows best knows how little he knows. - Thomas Jefferson
"[...]the Linux kernel (which is only a small part of a standard Linux configuration)."
... the mind reels.
Certainly, the Human brain is only a small part of a standard Human configuration.
Kinda reminds me of a Jack Handy quote: "The face of a child can say it all, especially the mouth part of the face.
Yet I still can't grasp what exactly is wrong with software patents.
Why should software companies be unallowed to protect their means and methods of innovation? Obvious patents are always wrong and unfortunately are granted every day. This is a major malfunction of the USPTO that must be addressed. However, the design of a large software system is hardly a simple algorithm. Every industry recognizes that processes, recipies, and systems may be patented. So what is it that makes software any different?
I understand that it is the dream of the "open" movement to turn IT into a service industry, however I believe this would have unfortunate consequences for both producers and consumers. Without the ability to shield innovation through patents, the software industry would have less reason to research and advance, and less means to support its constituents. It is admirable that developers worldwide embrace the open source ethos. But it is reckless to assume that all developers share those ideals.
I have read ESR's Cathedral and Stallman's Software Should Not Have Owners and find them optimistic at best. Mr. Muller is cast from the same mold. From NoSoftwarePatents.com: This is why obvious things (such as simple algorithms) should not be patentable. Software is indeed "written," however software systems follow a larger vision. The turning of a screw is not patentable, but a method of connecting parts (turn by turn by turn) to create a greater whole is.
I know this post is anathema to the local mindset, but I hope to get one or two serious responses =/.
It doesn't change the fact that software patents (and, probably, most of the recent non software patents, as well) need to go the way of arbitrary search and siezure and star-chamber trials -- but it still helps.
Free Software: Like love, it grows best when given away.
Nowadays most patent offices around the world are already "self funded", so the fees do already go back to the patent office. And the proprietor of a patent already has to pay maintenance fees to keep it valid. But this is part of the problem, since it invariably leads to lower and lower standards.
A look at the USPTO fee listUSPTO Fee Schedule explains the underlying math.
The basic application fee for a patent is $300, but you also have to pay a "search fee" of $500 and an "examination fee" of $200, making it a total of $1000 for making an application. But in order to collect that money, the patent office has to do quite a lot of work: set up a file, do an initial formal examination, perform a novelty search, and quite often engage in correspondence with the applicant to sort out various issues. It seems reasonable to assume that initial applications "as such" do not cover their own costs for the patent office.
But once a patent has been granted, nice things start to happen to the patent office's profitability calculations.
At the moment the patent is granted, the proprietor has to pay $1400 in "issuance fee". Then, in order to keep his patent valid, he has to pay maintenance fees at regular intervals. $900 is due at 3.5 years after it was granted, $2,300 due at 7.5 years, and $3,800 due at 11.5 years.
For a patent that is renewed throughout its full term, the post-allowance and maintenance fees add up to $8,400, compared to the $1000 for the initial application.
And the renewal fees are the good part of the patent office business, since the PTO doesn't actually have to do anything for the money, except make a note in the file that the fee has been paid. So for those patent offices around the world that are funded in whole or in part by the fees they collect, there is a direct incentive to let the standards slip to the lowest level they can possibly get away with.
The result can be seen at a patent office near you.
(This post is essentially a repost of a reply I made in another patent discussion a couple of days ago, with some minor changes in the numbers, as I had missed some of the fees in the original post. But the logic remains exactly the same.)
Christian Engström, Former Member of the European Parliament 2009-2014 for The Pirate Party, Sweden
I'd be more inclined to compare an operating system kernel to the brainstem or spinal cord rather than the whole brain. Low-level functions and all that.
...when you're writing a game...tweak the difficulty of "Easy" to something [your mother] can cope with. -- onion2k
Just get OSS into critical areas of the economy, such as DOD (already there), energy, and communications infrastructures. Also get it into some critical level at major companies (Apache?).
This is the non-political solution. Let these companies and government bodies fight the battle for you. They won't want to remove OSS in favor of less-reliable and more costly closed software.
Follow the money!
The patent system is intrinsically unfair, and "wrong" (for some appropriate definition of "wrong" that does not mean "right"). It stimulates both unhealthy individual thought as well as destructice social and economic activity.
How hard is it to make a working model of a one-click order?
This is why I think you need to have some tie between the effort required to develop a patent and the royalties you can achieve.
This sig has been temporarily disconnected or is no longer in service
This message is directed to Florian Mueller, hopefully a more reasonable individual then most the /. anti-patent zealots.
Your comment about IBMs patents is borderline FUD. While some of the patents may have nothing to do with software, those that do and are up for "renewal" (in the US you just pay your maintenance fee at 3, 7, and 11 years post grant) are usually only renewed if the continued protection is sought. In this case, by turning over those patents and not paying fees, they become fully public; however, most people in the public don't understand this system and simple add 20 yrs to the filing date and forget about it. This shows those patents are clearly available for individuals to use.
Another comment is the one about being limited to only certain licenses or as you say specific projects like Linux. Now clarify something for me, does that mean that individuals can then only release code under certain licenses? If so, which ones? Why is this really bad if the license limitations prevent people from using restrictive licenses. Ones specific to project (ie the Linux Kernel) may only really apply to those one things, and may not have much or any scope outside said project(s).
You bring up the combination patent idea where A and B are in the system, but your combination exists as Patent C. If there exists the proper measures as set out by SCOTUS and CAFC that A and B could be combined for C the patent can invalidated in court. If it cannot be invalidated, then you might actually have a problem...but in most cases an invalidation can be done unless combining A and B would be totally unheard of.
You mention that this doesn't reduce the number of enemies you might face. However, having your own patents at hand is good in the event of a court case, because you have your own protection there against their threats, particularly if you can show that their patent is either invalid or that your creation is along the lines of this patent and not theirs. It is also good because companies change regimes. Just because IBM is friendly with Open Source now does not mean they will be in 10 or 15 years.
The troll is a seriously problem, but the key to the troll is they are out to make a lot of money. The fact is that in the software world open-source does not necessarily have the money. There are bigger and better targets worth much more money. Large companies like Microsoft, Adobe, Sun, Google, etc. are far juicier targets then Redhat, Novell, etc. IBM is a nice big target, but in many peoples minds almost too big. Microsoft has been too quick to settle in the past (possibly because they know they will lose) with various cases (with maybe the exception of EOLAS). However, IBM is fighting SCO tooth and nail and not just sending them on their way to get rid of the pest. When IBM wins this case, they will be much less tempting targets because people will understand that IBM is not going anywhere. Oh and IBM has one of the biggest (actually it might be the biggest) patent portfolio in the US.
I think software patents are not all the gross evil that everyone sees them, and that certain well written ones are just fine especially in cases where a hardware or software implementation of a process can be used with equal efficiency. I do believe the problem with the US system lies in the fact that the addition was not made by lawmakers or the Patent Office, but by a panel of judges known as SCOTUS, actually the USPTO has tried their best to limit software patents and more particularly business method patents as best as they can without overstepping the SCOTUS ruling.
I just hope that you have a bit more of an open-mind then the zealots I see speaking most frequently on this topic, and have enough since to understand the need for rational debate and discussion and not just one-sided bashing.
"Some days you just can't get rid of a bomb."
The real question is, how do you reward software ingenuity and creativity if you cannot patent something? Is it enough to make money?
Perhaps this question would be better directed to Corel, Adobe, Apple, Microsoft, or any other entity that has been very well rewarded for its ingenuity and creativity with respect to software. Did patents get them where they are? This is precisely why this patent circus is so rediculous - the current success of various companies isn't even based on patents that protect their so-called "IP". Create something that people like, that they can use, and make it available at a reasonable cost, and they will most likely buy it.
The fact that Company A may have a better marketing team, a better implementation, more investment capital, smarter employees, or whatever, is NOT the jurisdiction of patents - but this is exactly the effect that why will have - they will eliminate competitive forces that can offer a better product.
Patent reform as proposed by arkanes:
[x] Yes
[ ] No
#2, #3 and #7 would solve a lot of problems...
"To promote the Progress of Science and useful Arts, by securing for limited Times to Authors and Inventors the exclusive Right to their respective Writings and Discoveries"
The United States Constitution (Article I, Section 8).
Patent is not the right to make and sell a product,
but the right to exclude others from using patented invention
for a limited period of time.
Invention is not the same thing as actual final product.
And there is no money mentioned anywhere in this formula:
Don't you get it, idiot ?
SCOTUS did not legalize software patents. If Diamond v. Diehr and prior rulings were followed, we would not have software patents today.
Ok, I don't really know for sure, but I think I've seen somewhere that there is a principle in law, based upon the constitutional right to due process, I believe, I'm not sure. Anyhow, the gist of it is, you can't sign away your constitutional rights. And, the right to sue is considered, I believe, a constitutional right. There are some exceptions, apparently - like the fairly standard 'arbitration' clauses, where you have to agree to that you will take grievances to an arbitrator of some sort.
But in this case, the license agreement would be purporting to have more authority, I think, than it legally would be allowed to. If someone wants to sue a third party, using non-free software, over infringement of their product, would this prohibit them from excersing their legal rights? Ok, if you have no idea what I just said, here's a more spelled out example.
Tom gets GPL'ed software from Joe, which includes the clause proposed by the parent poster. Tom also rights software, that's completely different from Joe's software, and distributes it under the Tom EULA (his legal right to do), and Tom has a software patent on his software also. Mike sees Tom's software, and decides to clone it, stepping on his patent. Tom now decides to sue Mike - does he now owe Joe $1M dollars/yr?
Possibly, but I don't think that the courts would really uphold this. IANAL.
Of course the computer programs Directive (91/250/EEC) states reverse engineering for the purpose of making software interoperable as being explicitly allowed.
But I know of no EU laws (or case law) forbidding reverse engineering of software, and I ought to know.
In 2002, when the EU commission proposed the software patent directive, they wrote: "The proposal therefore reflects concerns that if 'isolated' computer programs could be patented, this would blur the distinction between the scope of copyright and patent protection, and that if enforced, patents including such claims could be used to prevent "reverse engineering" and other activities considered legitimate in respect of computer programs already protected under copyright law.".
If you know of any EU law (or case law) that forbids reverse engineering of software in Europe, please let me know.
you can't sign away your constitutional rights. And, the right to sue is considered, I believe, a constitutional right.
But agreeing to this clause in the GPL wouldn't be signing away that right. You'd still have the right to sue, but there would simply be an additional cost if you chose to do it and had already agreed not to.
Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.