|
A database of the monopolies on programming problems, which the European Patent Office has granted against the letter and spirit of the existing laws, and about which it is unsufficiently informing the public, delivering only chunks of graphical data hidden behind input masks. The FFII software patent workgroup is trying to single out the software patents, make them better accessible and show their effects on software development. |
|
|
A patent description consists in
The claims say what you are not allowed to do. Each claim defines one class of prohibited objects. The description helps to interpret the meaning of the claims. It is supposed to provide sufficient instructions to enable the person skilled in the art to reimplement the "invention" without engaging in further inventive activity. However, EPO software patent descriptions generally fail to provide a reference implementation, and the hard and part is usually left to the programmer. Thus even from the point of view of enablement doubt could be casted on the validity of most EPO software patents. Patent descriptions and claims use a lot of strange talk about "allocation a block of space for a variable in a memory device" etc. This may just serve to make the "invention" look "technical", but also to prepare lines of retreat for possible litigation. In any case, a less legally interested reader will have to learn to treat it as noise.
|
|