this blogger was intrigued by the sort of concepts that someone starting to work as a patent expert might want to learn. The condensed URL in the Tweet resolved to a page on the EPO website at http://www.epo.org/searching/essentials/about.html which conveyed, among other things, the following information:If you're just starting to work as a patent expert you might want to learn about these basic concepts: http://buzz.mw/b5sn3_f
Yes, well, I suppose it might do just that, given a chance. But if we are honest about it, this basic concept is not as helpful as one might like it to be. Business start-ups, novices and people who believe that there is a one-to-one correlation between searchable patent information and things that will infringe other people's patent rights are perpetually surprised by the fact that, at any given time, there are a lot of patent applications that have been filed but not yet published -- and which are not therefore easy to access, even in these days of WikiLeaks and electronic surveillance. Avoiding infringing other people's patent rights is thus a bit like avoiding things that drop on to your head from a great height: you are sometimes quite unaware of them till they hit you.
- Avoid infringing other people’s patent rights
Before you put a new product on the market or offer a new service, you need to make sure that you will not be infringing someone else’s patent. Patent information will help you here, too.
Ideal for drafting patents? |
Now here's a challenge for readers. Taking the rubric above
what words might you more usefully substitute for the bit that goes
- Avoid infringing other people’s patent rights
Before you put a new product on the market or offer a new service, you need to make sure that you will not be infringing someone else’s patent. Patent information will help you here, too.See if you can manage it in 186 characters (the length of the advice above) or less.
If I may, I shall mark myself out as a genuine patent attorney, and suggest that your last line should be
ReplyDelete"See if you can manage it in 186 characters (the length of the advice above) or fewer."
You have a valid point, I think, but is that not the problem with all simplifications? Something is going to have to get missed out, else you have not simplified the issue - the question is whether the missing bits will come back to bite the reader later, and in IP they often do. It does worry me slightly that it is impossible* to present a simple, uncomplicated guideline about anything in the field of IP that does not have any caveats at all. Have we let the system get too complex?
*usually...