ESP Wiki is looking for moderators and active contributors!

Difference between revisions of "Software patent quality worse than all other fields"

m (moved Software is too abstract, patent quality is bad to Software is too abstract, software patent quality is terrible: more explicit. Longer, unfortunately, but I like descriptive, clear titles)
(Related pages on {{SITENAME}}: more)
Line 22: Line 22:
 
==Related pages on {{SITENAME}}==
 
==Related pages on {{SITENAME}}==
 
* [[Raising standards is not our goal]]
 
* [[Raising standards is not our goal]]
* [[The disclosure is useless]]
 
 
* [[Silly patents]]
 
* [[Silly patents]]
* [[Software patents are unreadable]]
 
 
* [[How to read patents]]
 
* [[How to read patents]]
 
* [[Why software is different]]
 
* [[Why software is different]]
 +
* [[Software patents produce legal uncertainty]]
 +
* [[Software is too abstract, software patent quality is terrible]]
 +
* [[The disclosure is useless]]
 +
* [[Infringement is unavoidable]]
  
 
==External links==
 
==External links==

Revision as of 20:28, 21 August 2011

Quality problems can happen in any category of patents, but the quality of software patents is particularly bad. This is probably a fundamental problem that can't be avoided in a domain as abstract as software.

The ideas are too abstract

In chemistry, ideas are described concretely, such as Trans-6-[2-(3- or 4-carboxamido- substituted pyrrol-1-yl)alkyl]-4-hydroxypyran-2-ones.[1]

In software, ideas are described as "point of sale location", "material object", or "information manufacturing machine".

Possible reasons

  1. Abstract algorithms can be described in so many ways.
  2. Jargon and lack of tangible components can make a mundane software idea sound technical.
  3. It's impossible for a patent examiner to judge obviousness. Software developers use so many ideas during their work, only a tiny percent ever get submitted to the patent office or otherwise published.

Examples

Related pages on ESP Wiki

External links

References