Slashdot Mirror
USPTO Asks For Input On Software Patents
New submitter MouseTheLuckyDog writes "The patent office is reviewing its policy on software patents and is asking for feedback (PDF). Groklaw reports that the USPTO will be hosting a pair of roundtable sessions in February, during which the public will have the ability to attend and put forth their viewpoints. From the article: 'It's obvious the USPTO realizes there is serious unhappiness among software developers, and they'd like to improve things. Software developers are the folks most immediately and directly affected by the software patents the USPTO issues, and it's getting to the point that no one can code anything without potentially getting sued. I don't wish to be cynical, though, as that's a useless thing. So maybe we should look at it as an opportunity to at least be heard. It's progress that they even thought about having a dialogue with developers, if you look at it that way.' If you can make it to Silicon Valley on February 12 or New York City on February 27, go and make your voice heard."
A program/software/instructions for a computer, whatever you call them, should be covered under copyright, not a patent. Algorithms should be treated as works for art. Functional (or imperative or whatever) art, but creative works nonetheless.
The end.
If computers were people, I'd be a misanthrope.
what i would suggest is pure software patents be BANNED (and all currently active software patents voided)
now if software is some part of an actual physical product (ie something that would go THUD is dropped) and is an intergral part of said physical product then you can have a patent on the entire setup.
also there should be a rule of "must infringe on all parts" for a patent to be violated (dropping out clauses that don't apply ie claim for water use when the infringement is land use if there is a land use clause)
Any person using FTFY or editing my postings agrees to a US$50.00 charge
No software or algorithm patents.
If you really want to keep something exclusive, keep it hidden, call it a trade secret, and sue anyone who leaks it.
Unless you are Einstein, someone else will think of it fairly soon anyway, because it's obvious to those at the leading edge of whateever specialty, so keeping it a secret may be bad social form but is not really harmful.
Where are we going and why are we in a handbasket?
Perhaps Slashdotters in the areas around these meetings would like to get together to plan, practice, and eventually travel to these meetings? Beers/Sodas after the meetings are suggested.
"Here Lies Philip J. Fry, named for his uncle, to carry on his spirit"
Has the USPTO presented specific examples of what they consider to be excellent software patents? That should help focus discussion...
now if software is some part of an actual physical product (ie something that would go THUD is dropped) and is an intergral part of said physical product then you can have a patent on the entire setup.
I never understood this argument. If the software is purpose-built for your hardware, then there's no use in copying it without said hardware. Here in Europe a similar precedent gets misused to push all kinds of software patents. Getting a patent on the hardware part only should be enough.
If this were true,the entire American Populace could sue Congress for extending copyright on works ex post facto. Public domain status is payment for a limited monopoly. Once Congress changed the rules, WE THE PEOPLE lost a good chunk of the social bargain. The door swings both ways.
Good-bye
The problem is that there is no single person whose fault the bad patent is. Consider if A (arbitrarily wealthy) and B (not) independently invent and locally produce X, but only A files for it, unaware of B. B resolves not to apply for a patent. Patent examiner C, also unaware of B, grants it. Company D hires B and begins producing Y, a variant of X that 'infringes'. After a few years, A's patent is granted and he (now a fairly large player) becomes aware of D (a very large player) and (because Y was released after he applied for the patent on X) sues. D, due to their ace-in-the-hole of B, cheerfully goes to court.
As far as A is concerned, he invented something, patented it, and is producing it.
As far as B is concerned, he invented something, but didn't bother patenting it. Doesn't matter, as his prior art should be enough to protect him against infringement claims.
As far as D is concerned, they are safe because of B's guarantee he won't patent it.
So then A sues D, after a long battle the patent gets invalidated, so who is to blame? Not A, he invented and patented the damn thing legally. Surely not B, he's taking the Benjamin Franklin (I think) approach. If B isn't to blame, I can't see a real reason that D is. Do you seriously expect C to scour the entire country himself to find B?
The correct answer would seem to be that if A and B came up with the invention, the patent should be invalid on grounds of obviousness, not prior art. But just because Newton and Liebnitz both wrote about calculus doesn't make their advances obvious. If math were patentable, and Liebnitz invalidated Newton's patent on integration, would you hold C responsible for not considering calculus obvious? Nobody in my example, I believe, "deserves" to lose a few billion. Various parties were simply unaware of each other.