en.swpat.org is a wiki.   You can edit it.   May contain statements End Software Patents does not endorse.

October 2014: US Supreme Court reining in software patents (Alice v. CLS)!

SitemapCountriesWhy abolish?Law proposalsStudiesCase lawPatent office case lawLawsuits


Patent review by the public

From en.swpat.org
(Redirected from Community patent review)
Jump to: navigation, search

What this article documents is not a solution.
For information of the risks of putting too much work into these, see duds and non-solutions. See also: Abolition is the only solution.

Community patent review is a proposal from Microsoft,[1] IBM, and other large companies to increase the standard of pre-grant evaluation by patent offices. People who are worried about patents could review patent applications themselves, inform the patent office about prior-art, and request reviews of patents that seem to fail the "newness" criteria for patentability. However, raising examination standards wouldn't fix much.

Contents

[edit] Limits to effectiveness

  1. If the patent office has a policy of accepting software patents, then there will often be no grounds for an external reviewer to complain about any particular software patent application.
  2. The patent holder will be given the opportunity to rewrite their patent to avoid the complaint, so unless the complaint completely invalidates the application, the result could be the granting of a stronger patent.
  3. Participating in the review costs time. We thus give our resources to solve a problem that shouldn't exist, and the resources we give will never be acknowledged. This could be resolved by allowing the finder of prior art to receive some of the patent registration fee, thus creating an incentive for people to locate prior art. Furthermore, a disincentive to file patent claims where prior art exists could be created, by levying an additional fee on a patent filer where prior art is found. This way the incentives of the patent filer, and prior art searchers can be aligned with the public interest, meanwhile minimising work for typically under-resourced patent offices.
  4. This can backfire since enhanced review can also be used to invalidate defensive patents.

[edit] Example: peer-to-patent

(This is a modified and updated version of an explanation by Ben Klemens[2])

According to Bessen and Hunt (page 47), about 70 software patents are granted by the USPTO per day.

Meanwhile, the Peer-to-patent project reports that as of May 11th 2008, they have gotten 183 items of prior art submitted on 56 applications.[1] The project opened in June 2007, so in eleven months they have been able to advise about six hours worth of output from the USPTO.

[edit] Successes of peer-to-patent

Peer-to-patent's website was used to gather prior art which lead to Red Hat and Novell's victory against a patent troll in the case Acacia v. Red Hat and Novell (2010, USA). However, the prior art used seems to all have been mentioned by the Groklaw community,[3] so the contribution of the peer-to-patent website is unclear.

[edit] Related pages on en.swpat.org

[edit] External links

[edit] References

  1. http://money.cnn.com/magazines/fortune/fortune_archive/2006/08/21/8383639/index.htm
  2. http://endsoftpatents.org/resources-for-computer-scientists
  3. http://www.groklaw.net/article.php?story=20100513121121635


This wiki is part of the End Software Patents (ESP) campaign (donate). For more information, see:
>> endsoftwarepatents.org (Main ESP website) <<
>> endsoftwarepatents.org/news (News) <<

This wiki is publicly editable. (See: en.swpat.org:About) It's a pool of information, not a statement of ESP's views or policies, so no permission is required. Add your knowledge! (See: Help:How to make a good contribution)