Are Companies Scanning Open Source Commit Logs And Patenting What They Find?

from the prior-art? dept

It’s funny how often we hear patent system supporters tell us that if you haven’t actually gotten a patent for your invention, it’s perfectly reasonable for someone else to go and patent it instead. The idea of presenting an idea for the public domain or for open source purposes seems foreign to them. Recently, I’ve seen two examples of questionable patent applications that appeared to take content that was put out publicly, and tried to turn them into patents. The first, found via Dave Farber’s IP list is a patent which an open source developer suggests almost identically matches code that he committed to an open source project. The guy who wrote that post has since backed down a bit on his original claims that the patent was clearly “copied” from his open source commits, but still notes that the patent application in question is ridiculous.

Then there’s a similar story, found via Slashdot of a guy who coded an open source library for Windows in 2001 (inspired by a Bruce Perens project from 12 years earlier) and just discovered that IBM appears to have patented the same technology — even mentioning this guy’s own blog post in the references section.

Whether or not these two patents are examples of various companies trying to patent open source technologies as they’re being developed, it does highlight yet another problem with the patent system as it is set up today. Even if there does appear to be clear prior art, it’s not as if the Patent Office seems willing, capable or interested in actually understanding how these patents are simply copying what’s already being done elsewhere.

Filed Under: , ,

Rate this comment as insightful
Rate this comment as funny
You have rated this comment as insightful
You have rated this comment as funny
Flag this comment as abusive/trolling/spam
You have flagged this comment
The first word has already been claimed
The last word has already been claimed
Insightful Lightbulb icon Funny Laughing icon Abusive/trolling/spam Flag icon Insightful badge Lightbulb icon Funny badge Laughing icon Comments icon

Comments on “Are Companies Scanning Open Source Commit Logs And Patenting What They Find?”

Subscribe: RSS Leave a comment
Andrew F (profile) says:

USPTO is looking at prior art

Read the Slashdot comments. It looks like the prior art reference was found and raised by the USPTO, not by IBM. They ultimately granted the patent after IBM narrowed their claims such that it was an “improvement” on the open-source tech.

That’s probably more of an issue than the prior art. At what point does an “improvement” become obvious? The interesting scenario would be if companies monitored open-source commit logs, predicted where the technology was heading, and patented it in advance. That’d be a good test-case for an independent invention defense.

kyle clements (profile) says:

Re: USPTO is looking at prior art

“That’s probably more of an issue than the prior art. At what point does an “improvement” become obvious?”

Maybe that’s why Gillette skipped over a 4-blade design.
Schick got a patent on 4-blades, so Gillette had to do the unexpected…jump straight to 5.

I am so patenting a 6 blade design…mwahahaha!

I’ve discovered one mind-bogglingly simple little thing that is not patented. It’s kind of cool, and I’m not going to patent it.
What worries me is the idea that someone else might come along, scoop up the idea, and prevent me from using it.

Someone should invent a crowd-sourced patent prior-art tool, where people can submit evidence and have bad patents easily revoked.

Anonymous Coward says:

Re: USPTO is looking at prior art

I think an issue is if IBM had not referenced the blog, would the USPTO have caught the prior art and another question to be asked is how often do those who want patents typically reference where they stole an idea if they stole it and how easy is it for our broken USPTO to locate such prior art and how motivated are they to do so?

It’s hard for me to imagine that patent trolls, in particular, are really capable, experienced, or knowledgeable enough in any industry to come up with anything original and useful on their own and it’s easy to imagine that these technologically inexperienced people could easily steal ideas from technologically experienced people from industries that actually engineer stuff, people who would consider such ideas obvious because they are skilled in the art (whereas patent trolls are only skilled in the art of extortion).

Anonymous Coward says:

Re: USPTO is looking at prior art

“They ultimately granted the patent after IBM narrowed their claims such that it was an “improvement” on the open-source tech.”

This basically looks like an attempt to patent anything that hasn’t been already patented or anything that has no prior art.

The assumption the USPTO seems to be making is that, if it hasn’t already been patent and there is no prior art, it’s patent worthy. I find such an assumption to be dubious at best. The goal of the USPTO shouldn’t be to grant as many patents as it can, it should be to promote the progress.

Anonymous Coward says:

Re: Re: USPTO is looking at prior art

Basically corporations have sorta taken a “patent the gaps” philosophy.

Make patents as broad as possible so that it covers everything, get feedback to figure out where the USPTO won’t grant patents, and patent the gaps that they will allow patents for.

Seems like something more likely to promote extortion than innovation. This shouldn’t be how the patent system works.

The patent system should work to promote the progress and perhaps to protect peoples R&D investments to encourage R&D, patents should typically have R&D value behind them, but apparently none of them do because no one gets patents to commit R&D behind an idea or to implement it, they just get patents to become the gatekeepers of as much as they could, which hardly promotes the progress.

Anonymous Coward says:

Re: Re: Re: USPTO is looking at prior art

and, honestly, I don’t necessarily blame IBM. If IBM doesn’t get these patents then some patent troll probably will, and they could end up suing IBM for infringement. IBM can also use these patents to counter sue someone who sues them for infringement. So these patents could be acquired for defensive purposes as well, IBM habitually knows that it should acquire as many patents as it can for defensive purposes to help alleviate future problems or the potential for future problems. Again, not how the patent system should work but unfortunately that’s how it does work.

Jason says:

Re: Walling in the progress?

@Mike Masnick, I’m with Andrew F, here. If you read further in the Slashdot comments, there’s a great discussion of how it’s not likely that this was a copy-to-patent scenario, but something far more convoluted and troubling.

It seems that, at least for software, the current patent system creates quite nearly the worst possible outcome for “promoting the progress.” Rather than mining commit logs for things to copy and patent it seems that instead companies scour the documentation of prior art to do everything they can to wall that innovation in.

Almost like an antibody in your bloodstream, they work to conceive of every possible microinnovation to fill in the gaps in every contour of an application of prior art, and THEN THEY PATENT THE GAPS. This essentially begins to squeeze out future innovation in related applications because in order for anyone else to progress further, they would have to pay to make use of possibly several patented microapps.

The extremely troubling thing is that the slashdotters in the know on this talk about it like this is simply the norm, and “of course you wouldn’t fight to invalidate just to re-open the playing field (as Tsiodras seems to want to do in your scenario above) because it costs way too much and where’s the money in it when you do?

To conceive of the terrible problem with this, imagine saying that you were trying to “promote the progress” of traffic by converting every vehicle into a Tron-esque lightcycle.

Just as in the Tron game, there seems to be extreme incentive to race to cover new ground, but in reality the structure of the game is such that the best strategy is to race ahead only to twist and turn and trap everyone else so that they are forced to turn a corner, drive suddenly into one of your walls and implode.

Mike, this seems to me to be the driving force behind the trend you’ve highlighted as patent thickets. How did we decide to artificially impose zero-sum rules on what is not only a non-zero sum game, but one of compounded aggregate gains?

Jason says:

Re: a different model for patents

Karl, I read your blog post on this, and I love the concept, but I wonder (and I offer this not as resistance, but as the very challenge before you/us on this): how can this collaborative process serve to overcome the systemic problem I pointed to above?

Because, considering the idea, it still seems vulnerable to a large corporation (or several of them) striving to wall-in your groups’ new ideas with scores of patents of related microapps?

How do you make your work thicket-proof?


Re: Re: Code is invention.

Code is an implementation of some algorithm. Thus, it can be the working model of some “patentable invention”.

Inevitably, a company like IBM has gotten a patent for things that might occur in any number of personal shell scripts.

This is inevitable when the PTO allows patenting the trivial.

Ultimately that leads to companies like IBM effectively stealing from every programmer competent in current technology by depriving them the right to use the product of their own intellect.

Andrew D. Todd (user link) says:

Benefits of the First To File System

The “First to File” system of patent priority offers a solution. Despite its name, the “First to File” system is actually a modified “first to publish” system, similar to that used in pure science. That is, it works something like the following:

1. If you were not the first to publish, and you were not the source of the first-publisher’s information, you may not have a patent. STOP.

2. If you were not the first to publish, and you were the source of the first-publisher’s information (ie. though a breach of confidence or something like that), you have to file for a patent within a year after they have published. If you prefer, you can just produce evidence that the first-publisher got the information from you, and the matter goes into the public domain.

3. If you were the first to publish, and you developed the information independently, you have a year after publication to file for a patent, otherwise it goes into the public domain.

Only if none of the competing parties has published does filing date become decisive. If there is any likelihood that anyone else is working along the same lines, this system rewards the act of publishing your lab notebook every day, via the internet, and figuring after the fact whether it is worth anything.

Add Your Comment

Your email address will not be published. Required fields are marked *

Have a Techdirt Account? Sign in now. Want one? Register here

Comment Options:

Make this the or (get credits or sign in to see balance) what's this?

What's this?

Techdirt community members with Techdirt Credits can spotlight a comment as either the "First Word" or "Last Word" on a particular comment thread. Credits can be purchased at the Techdirt Insider Shop »

Follow Techdirt

Techdirt Daily Newsletter

Techdirt Deals
Techdirt Insider Discord
The latest chatter on the Techdirt Insider Discord channel...