Tag Archives: defensive publications

KDE Frameworks Book Sprint at the Randa Meeting 2014

A couple of weeks before the KDE Randa Meeting of 2014, the meeting’s organizer Mario Fux suggested to have a book sprint to help developers adopt the newly released KDE 5 Frameworks. In the Open Source spirit, the idea was not to start from scratch, but rather to collect the various bits and pieces of documentation that exist in different places in one location that offers itself more to a developer than before. Valorie Zimmermann stepped up to organize it (many thanks!), and a number of people volunteered to take part. After a week the project completely changed its orientation and struggled and found and also newly defined its place as a part of KDE’s documentation efforts. And it produced an initial version of the book, which is currently circulated on people’s ebook readers around here. Continue reading

Qt Project and Defensive Publications

Open Source communities are amazingly innovative. Linux Defenders encourages them to document their ideas in the form of defensive publications, so that this body of knowledge becomes relevant prior art for later patent applications and patent invalidations. The Qt community is especially relevant for defensive publications for two reasons – it is highly innovative, and Qt’s functionality covers pretty much all topics that are relevant in software engineering today. At the Qt Contributor Summit that is currently on its way in Bilbao, Spain, Armijn Hemel and me started a process to make defensive publications a routine part of the Qt release process.Akademy 2013 and Qt Contributor Summit poster

Continue reading

Defensive Publications at Embedded World 2013

Embedded World has started today in Nürnberg, Germany. I am here with Open Invention Network to spread the idea of defensive publications and OIN’s non-aggression community of companies in the Open Source sphere. Highly innovative companies present here, and many of them face the same dilemma — if the innovators decide not to patent their inventions, they run the risk that another party applies for a patent of the same invention later. The decision not to patent could be for ethical reasons because they understand that software patents are harmful, or for business or many other reasons. The problem stays the same, there is a threat that patents are awarded even though similar solutions already existed.

There are many software patents out there that experts consider obvious, not inventive or trivial. All of those three are reasons that the patent should have been rejected. Especially important for complex but non-inventive ones, the patent examiner did not discover relevant prior art when scrutinising the patent application. The state of the art was not documented and accessible in a way that supported a good decision. Defensive publications are one answer to this problem. They offer a cheap and fast way to document inventions. Also, defensive publications are available for areas that legally should not be patentable, like software as such.

Through linuxdefenders.org, companies and research institutions, but also individual developers can submit defensive publications relevant to Linux and Open Source in general. Linux Defenders is backed by Open Invention Network on it’s mission to prevent bad software patents. We want to support developers and inventors to document their ideas as explicit prior art. Our goal is to ensure freedom to operate for the innovators in Open Source. If you are interested, worried about your invention or have any questions, you can find Armijn Hemel and me in hall 5, booth 341. Or ping me on Twitter @mirkoboehm.

Mirko Boehm
Google+