Microsoft's Internal Advice About Patents
BigPoppaT writes "Eric Brechner writes a best practices blog called Hard Code for Microsoft under the name I.M. Wright. His most recent post sounds like an endorsement of open source development (and does end with a call for Microsoft developers to participate in the shared source community). But even better is his advice regarding patents: 'When using existing libraries, services, tools, and methods from outside Microsoft, we must be respectful of licenses, copyrights, and patents. Generally, you want to carefully research licenses and copyrights (your contact in Legal and Corporate Affairs can help), and never search, view, or speculate about patents. I was confused by this guidance till I wrote and reviewed one of my own patents. The legal claims section--the only section that counts--was indecipherable by anyone but a patent attorney. Ignorance is bliss and strongly recommended when it comes to patents.' Interesting advice from inside Microsoft. I wonder if Ballmer would agree that ignorance should be 'strongly recommended when it comes to patents'?"
The reason you never want to search, is that you could find prior art. If you find prior art, filing for the patent would place you in an inextricable position. If the patent is approved, and you subsequently try to litigate to "protect" this new patent of yours, the records of your fact-checking can (and will) be subpoenaed, at which point you will not only lose the case, but will likely be subject to a counter-suit.
If you don't search, you've got a lot more room to maneuver in court.
I have something like 20 patents in my own name, and if they could I think that our Legal department would have me forget them too.
One does wonder, though, how they are supposed to "advance science and the useful arts" by publication if the publication is supposed to be write-only.
Lacking <sarcasm> tags,
Ironically, the original purpose of patent was to get them published to help others learn new techniques and ideas and expand on them.
Willful violation invokes statutory damages:
35 USC 284
When that doesn't apply, then you have to consider provisional damages:
35 USC 154.(d)(1)(B) Provisional damages:
The intent of willful ignorance is to insulate the company against statutory and provisional damages. As an engineer, this protects you, as well:
35 USC 271.(b):
-- Terry