Ask Slashdot: Reducing Software Patent Life-Spans?
seattle_coder writes "Many have advocated for the elimination of software patents. The arguments generally are that software patents are handed out too easily, and that they're too difficult and expensive to fight. Some say that patents just plain don't make sense for software, which is such a dynamic technology. Given that the standard patent lifetime is 20 years, and software changes so rapidly, is the life-span the problem for software patents? Would reducing the software patent lifetime to 5 years or even less be the thing to do?"
No, because the process to get a patent can easily stretch five years. Also that doesn't solve some of the other fundamental problems with software patents, such as software being math.
We shouldn't be able to patent software for the same reason we can't patent mathematics. Copyright protection is sufficient and suitable for software.
the one that's holding all the cards isn't going to ask for a new hand. the broken patent system serves the interests of large corporations, and they'll fight tooth and nail against any changes that is against their interest. in summary - dream on.
ELOI, ELOI, LAMA SABACHTHANI!?
is the life-span the problem for software patents?
No, the problem is that software is an algorithm and shouldn't be subject to patent law anyways. It's like trying to patent a mathematical formula.
sysadmins and parents of newborns get the same amount of sleep.
I dunno about patents so much. I think used properly they are useful. Unfortunately they are more often used to stifle innovation than they are to encourage it like they were intended to do!
My main worry is copyright. I think copyright law needs dramatic alteration! To me a Rudyard Kipling work that has been out-of-copyright for some time and bastardized by Disney to create "The Jungle Book" is more worthy of protection that a 20 year old computer game like "Tai-Chi Tortoise"
The first has a great deal of artistic merit, and will be recided in its original form for hundreds of years. The second will be in copyright for many years, despite the fact it has slipped from memory already!
There should be some distinction between a work that has potential monetary worth 75 years after its creation, and something that has no worth 5 years after creation.
Yes, the lifespan of patents is a big problem.
But in software, things change so rapidly that patent protection for even five years is an eternity: by then, it is game over.
The fundamental problem with software patents is that companies patent simple ideas. The Amazon one-click purchase patent is a prime example. These kinds of ideas should be considered "obvious" by the USPTO, but unfortunately these kinds of things are routinely patented. The result is that there is a minefield of patents around every simple idea, every basic thing that one can do in software. Anyone who wants to create a startup company around a software product is at great risk, and instead of investing their time and energy into product development they now have to invest it in legal research. That is not a very good state of affairs for an industry that thrives on innovation.
If patents are to be allowed to exist for software, the bar for what is not obvious should be much, much, much higher than it currently seems to be.
Just stop granting random patents because the people who decide on 'em can't understand what's written in a paper.
Let real tech people judge and - eventually - grant a *limited* patent, but stop giving away things because people can't read a proposal..
Making them 3 years would solve many many problems.
But, the TRIPS agreement says patents have to last 20 years.
However, the TRIPS agreement doesn't say that software has to be patentable. So countries could declare that software isn't patentable, and then create some new legal thingy called "petents", and say that petents last 3 years and that software innovations can be petented.
This would be hard work because some countries (USA for example) push the idea that TRIPS requires software patents.
http://en.swpat.org/wiki/TRIPS
Really, shortening the duration would be as much work, and there's always the risk that the monopolists will find some other nasty clause to stick in to make 3-year petents really harmful.
Let's just go for abolition. It will take time, but it's the only practical solution.
http://en.swpat.org/wiki/Why_abolish_software_patents
Expert in software patents or patent law? Contribute to the ESP wiki!
Anyone who has ever programmed just a little knows that programmers invent algorithms every day and reuse somebody else's algorithm every minute. It is just a greed-fuelled idiocy to patent random bits of what programmers invent as part of their work. It is like patenting a mathematical proof or a law of physics.
Then there is another matter: when are two algorithms identical? When the code is exactly the same, including the naming of variables? No matter the variable naming? When they generate the same machine code on some machine? When they compute the same results (but this is undecidable formally)?
Software patents are a stupidity to make lawyers richer and to make the life of developers more miserable.
There's numerous reasons why patents on software are invalid. The most difficult to understand for a non-technical person might be that it can be reduced to math, which is already not patentable; so be allowing patents on software you are allowing patents on math. And demonstrating this in court for any scenario could be somewhat difficult.
But the simpler answer (from the start) should have been that you are not supposed to be able to patent an idea; you must patent an invention (implementation). In software it's either source code (covered by copyright) or it's an idea (not patentable).
The simple question from the patent examiner or judge for a software patent is a request to see the implementation. Since there's no implementation in "a way to navigate the web using a touch interface" it should get tossed. On the other hand, the specific implementation could (I suppose) be patented, but since the implementation is already covered by copyright, why bother with the (inferior) patent...?
If you think imaginary property and real property are the same, when does your house become public domain?
..is NOT to reward someone who invested nothing other than a few neuronal sparks coming up with an idea, but to reward someone who risked a significant investment in time, money, and materials to be able to recoup that investment plus make a profit in exchange for sharing the fruits of that investment with everyone.
The VAST majority of software and business-method related patents are nothing that someone competent with ordinary skill in the field could not come up with as a common-sense solution to a specific problem, WITHOUT said investment OR risk.
That said, the problem is that bringing the original intent of patents back into the system is not in the best interests of those who decide who gets elected (it isn't the voters, natch) and, thus, will not happen without a revolution of some kind which circumvents their control.
Even civil disobedience won't get us very far because, ultimately, most people could care less that they are controlled like sheep, and believe that their masters are the "good guys" and can "do no wrong". As a result, get used to it until the system explodes and has to be replaced by something else, hopefully better, but such is not guaranteed. It is the time-honored tradition of the human race since time immemorial to let the decay of civilization outrun our ability to contain or mitigate it, to ultimately consume and destroy us.
I just wish it would hurry the hell up so we can start anew.
-SS "Teach the ignorant, care for the dumb, and punish the stupid."
Instead of looking at this with that same crappy "algorithms and software are math" (apologies, but it hasn't worked before, and it certainly won't now (unless we maaaaybe reduce EVERYTHING to 100% pure mathematics)) view, let's start looking for new ways of explaining it to the masses - they don't get it. The fault is not entirely their own cause of their ignorance, we haven't properly educated them. What do you do when people don't get the idea in political situations?
Protest.
Civil Disobedience.
Lobbying.
I'm pretty sure if 1000+ hackers showed up on the doorstep of the whitehouse equipped with laptops running as much patent-violating software as they could possibly muster - that'd be a pretty good start. The only question is who has the gull to show up? Who has the balls to write that code? So far, the one thing the hacker community (and other code-centred groups yes) seems to lack is some kind of motivating factor. Perhaps, and this is just a thought, the right to code what we please?
I'm almost tempted to organize something of these lines myself, problem is I can already smell the -1 rating this is going to earn for "stating the obvious" or "trolling". Can't say I didn't try.
Cheers, DH.
The real issue is that patenting has moved from protecting the method of solving a problem into solving a particular problem.
For instance, I cannot patent mowing a lawn. I can patent a lawn mowing machine, even one that exactly copies the pattern created by another lawn mower that also runs on gas and uses a rotary blade to do it. As long as my lawn mowing machine is different enough to merit the patent, I think it's fair so someone doesn't come along and copy my machine.
Now people are patenting ideas. So when Amazon patents "one click shopping" and I write open source software with different libraries to complete the same task, they claim patent infringement, which is nonsense. They should be able to patent a particular method, which is really just their code, not an end result. Even then it's redundant, as it's already protected by copyright.
Large corporations do not want patent law sane, because it's their multi-million dollar playground, and they can crush innovation and startups by simply filing a few law suits. The first nation with decent infrastructure to fix their system or abandon it will lead the way into the 21st century.
tl;dr: The ability to patent end results instead of particular methods is why the current patent system is a failure.
(speaking for myself), I feel that the biggest problem is when a collection of intellectual property is bundled into a standard (such as H.264), but despite the valiant efforts of standards development organizations to require their participants to document their participant's intellectual property in a standard, you can't really ensure that "submarine patents" by non-participants are not accidently infringed upon, and frankly even the SDOs don't have any real police power over participants that either on purpose or accidently don't disclose IP.
I feel that some organization (perhaps ANSI, or just the PTO) should be responsible for designating the most valuable standards (such as "national standards") for "mandatory IP declaration". This would start a process where within a set time (1-2 years), all intellectual property owners would have to "put up or shut up", i.e. declare that their intellectual property is covered by the national standard. If they don't declare during the limited time period, they forfeit their right to sue for infringement on implementation of the national standard.
Real businesses do not generally have a problem licensing known intellectual property protected by patent. It is the unknown that is the bigger risk, and makes adoptions of new standards slower (I've personally seen this at a previous position).
People need to start patenting dumb software ideas; not just the great ones.
How many $obnoxious_sound or $picOfTheDay apps do we really need? Some dumb schmuck needs to claim those ideas and put a limit on entrants to that cesspool.
Generally, I am against software patents, however I do believe that there are some software innovations that should be patentable. My feeling is that they should be held to much higher standards of innovation, non-obviousness, and utility than current software patents are. I say this as the holder of a software patent related to adaptive systems that allows compiled applications to alter the structure and behavior of application classes at run time without writing code or recompiling the application source code. I honestly believe that the innovations I invented (and are in use by most semiconductor and similar high-tech manufacturing enterprises to enable them to tailor off-the-shelf manufacturing software to their particular enterprise without writing and integrating new code) meet the same standards required of physical devices and such. That said, most of the software patents I have read about, or studied in detail, are totally bogus and should have been laughed out of the Patent and Trademark Office. Period of time for software patents? 10 years max in my opinion. 20 years is absurd. As stated elsewhere in these comments, software innovations occur too rapidly to lock up some concept for that much time.
Sometimes, real fast is almost as good as real-time.
I am already working for "software" patent reform. I live in Minnesota, and this morning I visited with Senator Franken's office, discussing "software" patent reform. Sen. Franken is also the Chair of the Senate Subcommittee on Privacy, Technology and the Law, so this is a topic he's paying attention to.
The America Invents Act is already in progress, so the reality is that Congress won't have the appetite to pick up the patent topic again in the next few years. So I'm afraid that the window has closed to get a law to enact "software" patent reform. Temporarily, anyway. This is unfortunate, since AIA doesn't really address any issues related to "software" patents or patent trolls.
However, it is possible to have a procedural change made with the USPTO. So I'm working that angle now.
To do that, we need to build popular support, enough voices that the Subcommittee will hear. As cheesy as it sounds, that means we need your help to contact your Senator's office and voice your opinion. Seriously, call their office, write them a letter (handwritten carries the most impact, but typed will do), or visit them in their office. Ask your Senator to push for "software" patent reform. Have some examples of "software" patents handy, and feel free to make a suggestion for how to fix the system. I think the citizen review method is a workable option. I've been discussing this topic with Sen. Franken's office for a while now, so if you don't have a particular suggestion to offer, ask your Senator to see what Sen. Franken is up to. I'm not kidding, they do listen to that. You can reference Katie Topinka, in Sen. Franken's Minnesota office, as the staffer who's closest to this. I'm working with her on this (and hopefully she won't mind me mentioning her name.)
If you live in Minnesota, New York, Rhode Island, Connecticut, Oklahoma, Utah, or South Carolina, note that your Senator is already on the Subcommittee for Privacy, Technology and the Law. This is a topic they will listen to.
The best advice I have heard in politics is that it's your politician's job to listen to you and to take that back to Washington to get it done. I'm lucky that my Senator actually does this. That's why if you don't feel your Senator will listen to you on "software" patent reform, you need to send them to Sen. Franken, because he will work on this. And Senators do talk to one another, even across the aisle.