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."

17 of 209 comments (clear)

  1. I Would Like To Suggest "Accountability" by Press2ToContinue · · Score: 4, Interesting

    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
    1. Re:I Would Like To Suggest "Accountability" by RobertLTux · · Score: 5, Insightful

      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
    2. Re:I Would Like To Suggest "Accountability" by Hentes · · Score: 5, Insightful

      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.

    3. Re:I Would Like To Suggest "Accountability" by spire3661 · · Score: 5, Insightful

      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
    4. Re:I Would Like To Suggest "Accountability" by Anonymous Coward · · Score: 5, Interesting

      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.

    5. Re:I Would Like To Suggest "Accountability" by Shetan · · Score: 4, Informative

      Doesn't the U.S. Federal Government have Sovereign Immunity?

    6. Re:I Would Like To Suggest "Accountability" by StripedCow · · Score: 4, Interesting

      What I would suggest is the following. Currently, the USPTO gets paid for every patent which they validate. This is so obviously perverse that it actually hurts.
      Now instead of letting that money flow into the hands of the USPTO, it should go somewhere else, perhaps it should go into education.
      This, imho, would already be a huge improvement.

      Let's take it one step further. Let the patent office PAY for each patent they validate. A second government could then pay them back based on the societal impact of the patents they approved (measured, say, 5 years after validation).

      Thus, with this two-tier model, lack of societal impact means a loss for the USPTO.

      This means that, under this model, the USPTO will not so easily approve simple things such as "one click shopping" because they might lose on it on account of a lack of social impact. Similarly, patent trolling will be actively barred by the patent office (no product means no social impact). However, a patent for a new medicine may be approved.

      --
      If Pandora's box is destined to be opened, *I* want to be the one to open it.
  2. Ban them! by eksith · · Score: 5, Insightful

    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.
    1. Re:Ban them! by jedidiah · · Score: 4, Informative

      Computer programs are already treated as copyrightable works. So there would be no new unintended consequences.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    2. Re:Ban them! by Ikonoclasm · · Score: 5, Insightful

      The code and algorithms are already copyrighted. Every creative work in the US is automatically copyrighted, so that concern is moot.

      Secondly, algorithms can't be patented. The law explicitly forbids the patenting of math. You can only patent an implementation of the math.

      Strictly speaking, software should be unpatentable. Software is, at its most fundamental level, pure math. However, much like gene patents, the US courts have decided to conveniently ignore the law where it states that Nature can't be patented (math and genes fall under Nature) in order to allow industry to prosper. Unfortunately, by granting individuals temporary monopolies, the USPTO has insured that those industries have become legal minefields that are stagnating out of fear of litigation.

    3. Re:Ban them! by WaywardGeek · · Score: 4, Insightful

      Copyrights and trade secrets protected the software industry just fine before the USPTO opened the flood gates on software patents in the early 90's. They should stick to the original intent of the constitution, and protect the free flow of ideas by banning patents on mathematical algorithms (which includes software, IMO). They should not overturn the patents they've granted - that would harm the companies that filed them - but going forward, patents should cover something more than what can be executed in any mainstream computer language. If I can violate your patent simply by writing C code, it should not be patentable.

      Software patents have resulted in:
      The Open Invention Network
      Peer to Patent
      Oracle suing Google over Java
      37 Android related patent suits
      Nearly killing RIM
      Linux patent suits ...

      I'm afraid we're at the point where the anti-software-patent people warned we'd be. Small companies live in terror of being sued over any software they write. Big companies waste billions of dollars in court. Coders like me intentionally "code dumb", to avoid accidentally using a patented software idea. It's a terrible waste, and it makes me very sad to see America throwing away it's software innovation lead in this way. Thank God software patents weren't around when we wrote so much of the software that still powers the world. If they were, we'd all still be renting time on IBM mainframes. Just imagine a world where Donald Knuth patented all his ideas.

      --
      Celebrate failure, and then learn from it - Nolan Bushnell
    4. Re:Ban them! by WaywardGeek · · Score: 4, Informative

      Requiring source code wouldn't do much to discourage software patents.

      I'm listed as an inventor on 22 patents so far. Several of them are software patents. I didn't file any originally, until a competitor patented a key software algorithm we'd used for years at a previous company - an algorithm we could not function without. Now I encourage that we patent all company-critical software ideas. Anyway, I've been filing them since the early '90s. My early patents all included full source code, and one has many thousands of lines from our commercial product - enough to actual run the algorithm on real designs. If you have a new logic optimization idea, have you fully disclosed how to implement it if you haven't included a netlist parser? Early software patents included full source code, which gradually was reduced until now a bit of pseudo code in the patent text is generally enough. The old requirement for source code didn't seem to slow patent applications.

      Every patent lawyer knows that you can't violate a patent in your head. The same is true if you write an idea down on paper. You also can't violate a patent by writing it down in Notepad on a computer, or even if you save it, and share it with friends. However, if your idea is a sequence of steps a computer could execute, and you "run" it, chance are high that you've just violated somebody's patent. Being a software developer in America is a bit like being an illegal immigrant. You just keep quite, keep your head down, and hope that nobody bothers looking at what you're doing too closely.

      --
      Celebrate failure, and then learn from it - Nolan Bushnell
  3. Keep It Simple Stupid by presidenteloco · · Score: 5, Insightful

    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?
  4. NYC Feb 27 - I'll try to make it - Slashdot meet? by MetalliQaZ · · Score: 5, Interesting

    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"
  5. show us one good software patent by johntromp · · Score: 5, Insightful

    Has the USPTO presented specific examples of what they consider to be excellent software patents? That should help focus discussion...

  6. Horse has bolted by Joce640k · · Score: 4, Insightful

    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...
  7. Re:Arrogance by fritsd · · Score: 4, Insightful

    I haven't heard a single valid argument for why software is any different than any other discipline.

    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

    "Software Patents
    Here are some of the articles Groklaw has published on software patents, particularly in support of the claim that software is mathematics and hence unpatentable subject matter."

    --
    To be, or not to be: isn't that quite logical, Slashdot Beta?