StackExchange, Google Team Up With USPTO To Help Crowdsource Prior Art Discovery
from the this-is-a-good-thing dept
I've been a big fan of StackExchange, for a while, as a very cool platform for getting expert insight into a variety of (mostly, but not entirely, technical) questions. The platform is so useful that, last week, Google even announced that it was pushing its own YouTube API developer support efforts off of its own Google Groups platform and over to Stack Overflow (the original StackExchange site). But that appears to be just one area in which the two companies are collaborating. As they announced today, StackExchange and Google are working together on AskPatents.com, a site dedicated to better crowdsourcing prior art.And it's not just StackExchange and Google working together: they've teamed up with the USPTO to make it easier for good prior art to be submitted to the USPTO to (hopefully) invalidate bad patents. While we were incredibly underwhelmed by the America Invents Act, which was last year's attempt at patent reform, it has (finally) made it much easier to allow third parties to submit prior art which may be helpful to examiners during the ~18 hours they spend in reviewing each patent. There was the famed Peer-to-Patent program, which I was quite skeptical about, but this seems to take that to another level, thanks in part to the useful setup of StackExchange's system that helps float good ideas to the top.
But where this gets much more powerful is through integration in two key spots. First up, this will be integrated into Google's patent pages. Recently, Google launched its prior art finder, which tried to help people find prior art through automated searches -- but you can now also click through directly to the AskPatents site by clicking a "discuss" button that will be shown on each patent page, which will take you straight to the StackExchange page. Neat. The second integration may be even more powerful. As people find useful prior art and it bubbles to the top, StackExchange's system will make it easy to then directly submit it to the USPTO. Clicking a button will take you to an already filled out USPTO form, where a bit of additional info can be added and submitted.
StackExchange founder Joel Spolsky sees this as an opportunity to help stamp out bad patents: "Collectively, we’re building a crowd-sourced worldwide detective agency to track down and obliterate bogus applications. Over time, we hope that the Patent Stack Exchange will mitigate the problems caused by rampant patent trolling. It’s not a complete fix, but it’s a good start."
There are still tremendous structural problems with the patent system. And, at best, a system like this just helps to prevent some of the bigger mistakes, rather than attacking any of the fundamental problems. But, given just how damaging absolutely ridiculous patents are these days, anything that helps stop bad patents has to be seen as a good thing.
Thank you for reading this Techdirt post. With so many things competing for everyone’s attention these days, we really appreciate you giving us your time. We work hard every day to put quality content out there for our community.
Techdirt is one of the few remaining truly independent media outlets. We do not have a giant corporation behind us, and we rely heavily on our community to support us, in an age when advertisers are increasingly uninterested in sponsoring small, independent sites — especially a site like ours that is unwilling to pull punches in its reporting and analysis.
While other websites have resorted to paywalls, registration requirements, and increasingly annoying/intrusive advertising, we have always kept Techdirt open and available to anyone. But in order to continue doing so, we need your support. We offer a variety of ways for our readers to support us, from direct donations to special subscriptions and cool merchandise — and every little bit helps. Thank you.
–The Techdirt Team
Filed Under: crowdsourcing, patents, prior art, uspto
Companies: google, stackexchange
Reader Comments
Subscribe: RSS
View by: Time | Thread
[ link to this | view in chronology ]
Re:
[ link to this | view in chronology ]
Re: Re:
[ link to this | view in chronology ]
Re:
[ link to this | view in chronology ]
Re: Re:
http://superuser.com/questions/252239/how-can-i-batch-rename-files-in-bash
As you can see, there is more than one way to solve this particular problem, hence, you get more than one answer. You can judge the validity of each of the answers by its score (the large number on the left) and by the comments underneath it. A green "tick" denotes that a particular answer was considered the "best" by the question submitter.
Having your answers voted up and marked as "best" gives you reputation points, which are used as measure of how "trusted" you are, and also grant you special privileges on the site.
It is all rather simple if you take the time to understand it.
[ link to this | view in chronology ]
Re: Re: Re:
[ link to this | view in chronology ]
Re:
Even taking this to be true, that just means this site is better than the other ones. At StackExchange, questions get answered.
[ link to this | view in chronology ]
Re: Re:
[ link to this | view in chronology ]
Almost a good idea...
[ link to this | view in chronology ]
Re: Almost a good idea...
[ link to this | view in chronology ]
Re: Almost a good idea...
[ link to this | view in chronology ]
[ link to this | view in chronology ]
Re: Snarfunkle
OMG, you should patent that!
;-P
[ link to this | view in chronology ]
Re:
Um, are you referencing something? Because most of the touch-screen patents expired in the 90's. If you're referencing something in particular, perhaps you should consider that what was actually patented is much more complicated then you're letting on.
[ link to this | view in chronology ]
Perhaps for now that's true, but it also potentially helps build a mountain of evidence about those problems which can be referenced by critics of the current system. In my experience every discussion with people who haven't taken a close look for themselves pretty much requires you to begin with a mountain of explanation and evidence too big for them to get through before they tune out.
On the other hand if you could simply point them to a bunch of submissions like this it would be both simpler to understand and more convincing. You and I may not see evidence which comes from the USPTO process more relevant, but I think most people would. Most of those same people would dismiss an economics paper with what we see as clear and convincing arguments as simply one person's opinion.
That's understandable considering most of what the public is exposed to in that field is really political punditry in disguise. It has as much in common with the study of economics as Chicken McNuggets do with traditional southern fried chicken.
[ link to this | view in chronology ]
[ link to this | view in chronology ]
Maybe the USPTO should consider changing their rubber stamp that says PATENT GRANTED to a rubber stamp that says PATENT DENIED.
Denying should be the default. There needs to be a very good case for a patent to be granted. There needs to be incentives to prevent improper patent grants. There needs to be significant costs imposed after improper patent grants.
[ link to this | view in chronology ]
Re:
If you think the USPTO rubber stamps anything, you are gravely mistaken.
Denying should be the default. There needs to be a very good case for a patent to be granted. There needs to be incentives to prevent improper patent grants. There needs to be significant costs imposed after improper patent grants.
Rejection IS the default, numb nuts. A majority of patent applications get rejected on the first go-round. Your pontification evinces your lack of understanding of the examination process.
[ link to this | view in chronology ]
Re: Re:
Ah, that is correct. But as shown previously, a very large majority of those is approved on the second go-round.
So yeah, it's rubber-stamping. But they introduce an artificial rate of failure to make it seem less rubber-stamp-y.
[ link to this | view in chronology ]
Re: Re: Re:
Really? Show me.
So yeah, it's rubber-stamping. But they introduce an artificial rate of failure to make it seem less rubber-stamp-y.
Hardly. You have no idea what goes on during examination, as you fail to admit that almost every one of those applications gets amended to narrow the scope of the originally-filed claims in order to get around prior art. That's not rubber-stamping; that's doing one's job.
[ link to this | view in chronology ]
Re: Re: Re: Re:
[ link to this | view in chronology ]
Re: Re: Re: Re: Re:
[ link to this | view in chronology ]
Re: Re: Re:
Wilton is correct in noting that your understanding of how applications are examined is missing much relevant information that cuts the other way.
[ link to this | view in chronology ]
Re: Re:
So you see, both sides would like a higher bar for patents. Only the courts in the middle disagree.
[ link to this | view in chronology ]
Re: Re: Re:
I saw one of them, and the Examiner said that s/he gets pressure from industry and the patent bar. That's not surprising: they have an interest in getting patents. What the Examiner did NOT say is that s/he gets pressure from his/her employer, the USPTO.
The Examiner also mentioned that "It's just a tough job and sometimes bad patents get issued and good patent applications get rejected." I would agree: sometimes, shit happens.
If anything, examiners may feel "pressured" to allow claims only because they were formerly pressured to reject. In the past (i.e., under John Dudas), Notices of Allowance were subject to higher-level review, but final rejections were not. Thus, in order to avoid scrutiny, examiners would just reject-reject-reject. Now, under Director David Kappos, both NOAs and Final Rejections get scrutinized. Thus, examiner's have been encouraged to interview applicants so that they can come to a faster understanding of what each side thinks is patentable and come to an agreement.
[ link to this | view in chronology ]
Re: Re: Re: Re:
[ link to this | view in chronology ]
Re: Re: Re: Re: Re:
[ link to this | view in chronology ]
Re: Re:
[ link to this | view in chronology ]
Re:
But then the offices got incentives to grant patents, for instance by making appeals against the patent office denying something possible.
And along come some brain-dead judges which accept a bookshelf full of Moby Dick as a Moby Dick Support Device, and who believe the lawyers arguing math isn't math if it runs on a computer, and you got a pretty good mess.
And of course, add a lot of politicians who are firmly indoctrinated that patents are good, are somehow "acceptable monopolies" and not some mercantilist ploy.
[ link to this | view in chronology ]
Re:
Thus, the current practice is substantially "patent Denied".
What you rarely read here is that this places the applicant in the position of having to defend why the claims recited in the application are allowable over the cited prior art, in most cases requiring that the claims be amended to add limitations necessary to properly distinguish the claims from the prior art.
Thus, your comment reflects little more than what has long been established practice before the USPTO.
[ link to this | view in chronology ]
Queue the trolls...
[/sarcmode=off]
This is a step in the right direction... The question is will it be used to invalidate existing patents, a reactive action, or prevent bad patents going forward, a proactive action? Perhaps both, but the cynic in me says it will be neither. People will compile massive piles of evidence against a particular patent, but the USPTO and/or the courts will simply ignore it as usual...
[ link to this | view in chronology ]
These kinds of programs are doomed to failure due to apathy vs the number of applications.
If, on the other hand, we offered a bounty for each anticipatory reference then perhaps people would care. But then people would just game the system by getting their buddies to submit easily anticipated claims and collecting bounty after bounty.
Perhaps if we offered a mandatory applicant funded bounty for each anticipatory reference. That might do the trick.
[ link to this | view in chronology ]
Nice!
[ link to this | view in chronology ]
[ link to this | view in chronology ]