Slashdot Mirror


EFF Proposes a Working Code Requirement For Software Patents

Juha Saarinen sends news that the Electronic Frontier Foundation has proposed a fix for software patents in general and patent trolls in particular: requiring applicants to provide specifics about their solution. They say the applications should include working code, or at least "detailed, line-by-line notations explaining how their code works." "And if they do get a patent, they should be limited to the invention they claimed. We think software patents are bad news, and incredibly harmful to our society and economy. We wish we didn’t have to deal with them at all. But by fixing the functional claiming problem, and limiting patentees to a narrow invention that they actually came up with, we would also limit the amount of harm those patents could cause. The Patent Office does not (yet) have the power to get rid of software patents entirely, but it can fix the functional claiming problem."

7 of 130 comments (clear)

  1. Incidentally by Anonymous Coward · · Score: 5, Insightful

    This would also allow people who did license the patent to use the code rather than having to re-invent it themselves from scratch, or for that matter people coming along when it had expired...

    Hang on isn't that half the point of the patent system? To grant a monopoly on an invention for a limited time in return for providing sufficient information in sufficient detail such that said invention can be replicated when the patent expires?

    1. Re:Incidentally by DickBreath · · Score: 5, Insightful

      In the case of software 're-invent it themselves' is equivalent to 're-implement it themselves'.

      If I can re-implement it without any reference to the patent, and possibly without even knowing that the patent ever existed in the first place, then we're talking about something so obvious that it should not be eligible for patent protection.

      --

      I'll see your senator, and I'll raise you two judges.
  2. Once you have working code . . . by DickBreath · · Score: 4, Insightful

    The question could be asked, why isn't Copyright protection sufficient for your code?

    If someone else independently can implement code that does the same thing, then it is obvious it should not be eligible for a patent.

    --

    I'll see your senator, and I'll raise you two judges.
  3. Solutions, not problems by Qzukk · · Score: 4, Insightful

    The majority of the software patents I've seen are simply a statement of a problem, not a solution. They do nothing to promote the progress of science, and as such should not be considered valid patents, and the laws should be changed to make them not valid patents.

    Following the EFF's proposition would be a good way to make sure that your patent states a solution and promotes the progress of science.

    --
    If I have been able to see further than others, it is because I bought a pair of binoculars.
  4. Doesn't "slay" trolls entirely by stevejf · · Score: 3, Insightful

    This doesn't necessarily do away with patent assertion entities (trolls). Many PAEs are not actually the original inventors/assignees of the patents, but rather buy them later on and begin filing infringement lawsuits. This requirement would, however, reduce the number of startups-turned-trolls who filed and were granted patents but never followed through with development. It also might make the provisional application system more useful, allowing start-ups to file provisionals to establish priority, but also requiring them to develop a working prototype before granting a utility patent.

  5. Re:Interface patents by ZombieBraintrust · · Score: 3, Insightful

    Thats is the point. It brings attention to the patent examiner that the solution is trivial. More patents will be rejected for obviousness.

  6. Re:What about complex software? by DickBreath · · Score: 3, Insightful

    I am skeptical that a new advanced idea or new or improved algorithm that advances the state of the art would take man-decades to turn into working example code. Are there in fact, any such examples of this?

    It sounds like you're talking something you would work an entire career on from the time you're young until the time you're old to have something working. ("man-decades") Even if we're talking 2 man-decades == 20 man years, that was done as 20 people for 1 year, it does not seem unreasonable to have a working model. That had been true for non software inventions. I remain skeptical it would take 20 people a year to build a simplistic working model of even an advanced idea. The working model doesn't have to be the most efficient implementation of the idea. It just has to illustrate an advance in the state of the art.

    Yes, I know you are identifying a possible problem caused by the proposed requirement of working code. But the EFF proposal is to fix a much more serious and widespread problem that is real and not hypothetical.

    --

    I'll see your senator, and I'll raise you two judges.