Hacker News Reader

Comment by throwawaykf05 | Hacker News Reader

A slightly more humorous take on the same thing:

http://www.danshapiro.com/blog/2010/09/how-to-read-a-patent-...

Former patent examiner here. This is the truth. Only thing I'd add is, read the claims broadly. Anything that could possibly be meant by the words in the claim.

If it's broad enough to contemplate what you're doing, look through the spec, correspondence (the "file wrapper"), and general knowledge at the time for arguments to restrict interpretation of scope. Also, talk to a lawyer :(

edit: linked to this in another comment, and it also belongs here: "Broadest Reasonable Interpretation" http://www.uspto.gov/web/offices/pac/mpep/s2111.html

Would you say it's more or less impossible to write your own patent claim? I.e. is there some book or some resources that could teach you to do it or is the knowledge required too big?

Mostly impossible. There is a fairly useful book - the USPTO's "Manual of Patent Examining Procedure" (or MPEP). Official - http://www.uspto.gov/web/offices/pac/mpep/ My copy - http://adlervermillion.com/MPEP/

Its a huge book though, and not worth reading it unless you want to work with patents every day (as a patent agent, patent examiner, patent lawyer).

Also, its a reference book, not really something you can read start-to-finish.

Of course it's possible for anyone to write a patent claim. However, it's unlikely that the claim you write will be of any value.

I went to law school, passed the patent bar, and worked at the patent office. Even I wouldn't want to write my own claims. There are too many technicalities to deal with in the process. At the very least find a patent agent to do it (agents can draft and manage an application; attorneys can do that plus opine on validity etc.).

Kind of like reading research papers:

1) Read the abstract 2) Read the conclusion 3) If any questions or doubts remain, read the middle.

wow. that is better than my version.

Reply on news.ycombinator.com