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."
I would like to see a new law on the books: "wrongfully or negligently issuing a patent", to be applied as follows:
In the case where a patent is declared invalid, I would like to see the issuing patent office and/or examiner held responsible for damages done....
And to reimburse the patent applicant for:
1) the fees charged for granting the patent
2) legal fees incurred by the patent holder in attempting to defend the patent before it is struck down
And to reimburse any party who is financially damaged by the patent office having wrongfully issued a patent, such as
3) to any company which licensed the patent: any license fees paid out to use the patent
4) to any company which was sued for infringing on the patent: court costs and damages
Patents are applied for in good faith. If the recipient can be irreparably damaged due to negligence or other actions which wrong the recipient, shouldn't there be legal recourse?
Do you think the USPTO might hold "inventiveness" and the "obviousness" tests, and the search for prior art to a much higher standard? Do you think they might have the motivation to remedy any weaknesses in the system and keep on doing so?
Accountability anyone?
Sent from my ENIAC
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.
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...
they'd like to improve things...
Too late for that, the damage is done. The patents they already issued are enough to destroy the software industry for the next 15 years at least.
No sig today...
Really? Oh.
Here are a whole bunch of them, each one carefully reasoned out and commented on:
http://www.groklaw.net/staticpages/index.php?page=Patents2
To be, or not to be: isn't that quite logical, Slashdot Beta?