ESP Wiki is looking for moderators and active contributors!

Difference between revisions of "Raising examination standards"

(Related pages on {{SITENAME}}: merged in all useful content from Raising standards is not our goal)
(Slight benefit: Raising standards may reduce a small part of the problem, so it's not a negative change)
(26 intermediate revisions by 5 users not shown)
Line 1: Line 1:
{{dud}}(Note: [[Risks of supporting partial solutions]])
+
{{dud}}{{navbox}}
 +
Raising examination standards would reduce the total number of [[software patents]] granted, but given that most patent problems involve multiple patents, and given that one patent is enough to block development, a reduction would not solve many problems.
  
When people talk about '''patent reform''', they are usually referring to proposals to '''raise examination standards''' by making the criteria stricter or tougher, and increasing the resources available to patent examiners.
+
==Standards example: MPEG==
  
The result would be to reduce the number of software patents granted.  This would be helpful, but it wouldn't solve the problemIt only takes one software patent to destroy a small business or ruin an interoperability standard.
+
[[MPEG LA]] represents a pool of over 1,000 patents which it claims are essential for an implementation of the H.264 video format.<ref>http://lwn.net/Articles/371751/</ref> Many of these are duplicates (one for each country), so maybe there are 100 patents (each with around 20 claims).
  
When encouraging the raising of patent examination standards, it's very important that your work is not misunderstood as showing support for "high quality" software patents.  Always phrase your support like: "''Raising the standards is a step in the right direction, but even 'high quality' software patents are harmful to society.  The right thing to do is get rid of software patents entirely''".
+
If the numbers of these patents are reduced by 10%, 50%, or even 95%, it will allow free formats to adopt the features claimed in these patents. But there will still be no change to the fact that implementing the original format requires permission from MPEG LA.
 +
 
 +
A format like MPEG that is covered by a large number of interlocking patents is a worst case scenario.
 +
Some other formats are covered by only one or a few patents, and busting those patents would allow the format to be used freely.
 +
 
 +
==Slight benefit==
 +
 
 +
The result would be to reduce the ''number'' of [[software patents]] granted.  This should reduce the problems caused by [[patent trolls]].
 +
 
 +
When encouraging the raising of patent examination standards, it's very important that your work is not misunderstood as showing support for "high quality" software patents.  Always phrase your support like: "''Raising standards may reduce a small part of the problem, so it's not a negative change, but even 'high quality' software patents are harmful to society.  The right thing to do is get rid of software patents entirely''".
 +
 
 +
==What effects do the USPTO's 2010 KSR guidelines have?==
 +
 
 +
In September 2010, the [[USPTO]] published a ''2010 KSR Guidelines Update''.<ref>http://edocket.access.gpo.gov/2010/pdf/2010-21646.pdf</ref>  There is disagreement over what effects these guidelines have.
 +
 
 +
One disagreement is over whether they have any effect at all.  Patently-O's Dennis Crouch comments:<ref>http://www.patentlyo.com/patent/2010/09/uspto-guidelines-for-determining-obviousness.html</ref>
 +
 
 +
<blockquote>
 +
The 18–page guidelines do not have the force of law, but will impact how examiners judge obviousness in practice.
 +
</blockquote>
 +
 
 +
The second disagreement is about ''what'' effects they will have.  On one hand, there's Intellectual Property Expert Group (ipeg), which published an article about how these guidelines make the obviousness tests easier to pass.<ref>http://www.ipeg.eu/blog/?p=1742</ref>  On the other hand, there was broad disagreement with this claim when the story was discussed on Slashdot.<ref>http://yro.slashdot.org/firehose.pl?op=view&type=story&sid=10/11/07/1248226</ref>
 +
 
 +
Ipeg's article described the change thusly:
 +
 
 +
<blockquote>
 +
According to the 2007 Guidelines, however, in addition to TSM there came into being with KSR six other tests for obviousness.  These tests gave the examiners six new ways to reject claims and so help achieve the reduction in the patent allowance rate which was such an important goal for the PTO under its then-Director, Jon Dudas.<br />
 +
[...]<br />
 +
In the 2010 Guidelines, however, only two of the new tests for obviousness appear to survive.<ref>http://www.ipeg.eu/blog/?p=1742</ref>
 +
</blockquote>
 +
 
 +
The article concludes that these new guidelines are in line with making the tests easier to pass:
 +
 
 +
<blockquote>
 +
This is in line with the general trend of the PTO under Director Kappos to [...] and give applicants greater opportunities to obtain allowance of claims.
 +
</blockquote>
  
 
==Related pages on {{SITENAME}}==
 
==Related pages on {{SITENAME}}==
 +
 
* [[Duds and non-solutions]]
 
* [[Duds and non-solutions]]
 
* [[Quality of software patents is particularly bad]]
 
* [[Quality of software patents is particularly bad]]
 +
* [[Patent standards here are higher than in the USA]] - a myth for most countries
 +
* [[Patent review by the public]]
 +
* [[RSA patent]]
 
* (USA) [[The Patent Reform Act]]
 
* (USA) [[The Patent Reform Act]]
 +
* [[Applicants paying for patent review]]
  
 
==External links==
 
==External links==
* gnu.org: [http://www.gnu.org/philosophy/patent-reform-is-not-enough.html Patent Reform Is Not Enough]
+
* [http://www.gnu.org/philosophy/patent-reform-is-not-enough.html Patent Reform Is Not Enough], '''gnu.org'''
 +
 
 +
==References==
 +
{{reflist}}
  
  
{{page footer}}
+
{{footer}}
 
[[Category:Minor ways to also fight software patents]]
 
[[Category:Minor ways to also fight software patents]]
 
[[Category:non-solutions]]
 
[[Category:non-solutions]]

Revision as of 01:09, 16 June 2012

Red alert.png What this entry documents is not a solution.
This practice may be ineffective or useless in the long term.
ESP's position is that abolition of software patents is the only solution.


Raising examination standards would reduce the total number of software patents granted, but given that most patent problems involve multiple patents, and given that one patent is enough to block development, a reduction would not solve many problems.

Standards example: MPEG

MPEG LA represents a pool of over 1,000 patents which it claims are essential for an implementation of the H.264 video format.[1] Many of these are duplicates (one for each country), so maybe there are 100 patents (each with around 20 claims).

If the numbers of these patents are reduced by 10%, 50%, or even 95%, it will allow free formats to adopt the features claimed in these patents. But there will still be no change to the fact that implementing the original format requires permission from MPEG LA.

A format like MPEG that is covered by a large number of interlocking patents is a worst case scenario. Some other formats are covered by only one or a few patents, and busting those patents would allow the format to be used freely.

Slight benefit

The result would be to reduce the number of software patents granted. This should reduce the problems caused by patent trolls.

When encouraging the raising of patent examination standards, it's very important that your work is not misunderstood as showing support for "high quality" software patents. Always phrase your support like: "Raising standards may reduce a small part of the problem, so it's not a negative change, but even 'high quality' software patents are harmful to society. The right thing to do is get rid of software patents entirely".

What effects do the USPTO's 2010 KSR guidelines have?

In September 2010, the USPTO published a 2010 KSR Guidelines Update.[2] There is disagreement over what effects these guidelines have.

One disagreement is over whether they have any effect at all. Patently-O's Dennis Crouch comments:[3]

The 18–page guidelines do not have the force of law, but will impact how examiners judge obviousness in practice.

The second disagreement is about what effects they will have. On one hand, there's Intellectual Property Expert Group (ipeg), which published an article about how these guidelines make the obviousness tests easier to pass.[4] On the other hand, there was broad disagreement with this claim when the story was discussed on Slashdot.[5]

Ipeg's article described the change thusly:

According to the 2007 Guidelines, however, in addition to TSM there came into being with KSR six other tests for obviousness. These tests gave the examiners six new ways to reject claims and so help achieve the reduction in the patent allowance rate which was such an important goal for the PTO under its then-Director, Jon Dudas.
[...]
In the 2010 Guidelines, however, only two of the new tests for obviousness appear to survive.[6]

The article concludes that these new guidelines are in line with making the tests easier to pass:

This is in line with the general trend of the PTO under Director Kappos to [...] and give applicants greater opportunities to obtain allowance of claims.

Related pages on ESP Wiki

External links

References