| |||||||||||||
LFCS 2012: The Linux System DefinitionLFCS 2012: The Linux System DefinitionPosted Apr 20, 2012 10:56 UTC (Fri) by wookey (subscriber, #5501)Parent article: LFCS 2012: The Linux System Definition
Does anyone have more details on this defensive publication process? I'm (on behalf of emdebian) an OIN member and didn't know/had forgotten. In principle timely defensive publication is a complete antidote to patents, but of course many of us don't do it, or don't do it in a way the patent office is likely to notice. So this seems like a really useful idea if it was just possible to get people to pass on every trivial idea they had today, and OIN could keep up writing them all up. You almost want something like a bug reporting system.
The problem it has is that, like the 'peer to patent' system, there is little incentive for developers to actually spend time on it. Actually the incentive is huge of course - defeating the whole shitty-patents nonsense that is the bane of everyone's lives, but it's so diffuse that very few of us (apoproximately none so far as I can tell) are actually spending time on peer to patent or filing 'please write this up' requests with OIN.
Has anyone here actually participated?
(Log in to post comments)
LFCS 2012: The Linux System Definition Posted Apr 20, 2012 15:59 UTC (Fri) by armijn (subscriber, #3653) [Link]
Yes, I have. It is actually really simple to write a defensive publication.
You can see various examples of how defensive publications are written at ip.com. Basically it comes down to this: one or two pages, and at least one diagram to describe interaction between components, dataflow, and so on. It does not take that long to write it (about an hour or less for people with some experience).
Very soon Open Invention Network will travel to several conferences (Akademy, GUADEC, COSCUP are planned) to provide hands on assistance with writing defensive publications.
|
|||||||||||||