[DE Deutsch] [FR Francais] [Translate] [original] [translatable text] [Readers' Comments]

Google
CECtableEICTA

EU Software Patent Directive: Parliament's vs Council's Version

In September 2003 the European Parliament amended a proposal from the European Commission for patentability of software in such a way that it became a proposal that clearly disallows software patents. The EU Council of Ministers and the European Commission subsequently disregarded the European Parliament's Amendments and reached "political agreement" in May 2004 in favor of a text that goes even further than the previous text of the Commission in imposing US-style unlimited patentability, but shrouds this in a veil of convoluted wording, characterised by multiple negations and other misleading syntactic devices. Below you can find out yourself by carefully reading the core provisions of the proposed EU directive "on the patentability of computer-implemented inventions" which we have collected in a table, together with short explanations of the implications. At the end we add pointers to the originals from the Parliament and Council websites as well as to related analyses and news reports.
  1. Table
  2. Local copy

1. table

CEC 2004-05-18ImplicationsEuropean Parliament 2003-09-24Implications
Recital 17
The provisions of this Directive are without prejudice to the application of Articles 81 and 82 of the Treaty, in particular where a dominant supplier refuses to allow the use of a patented technique which is needed for the sole purpose of ensuring conversion of the conventions used in two different computer systems or networks so as to allow communication and exchange of data content between them.
A patent holder is entitled to block interoperability as much as he wants, as long as he doesn't violate antitrust law. Patent law itself imposes no limits. Moreover, even if anti-trust law is violated, it is very unlikely that there will be any effective legal remedy, given the complexity of the concerned procedures, as shown in the EU vs Microsoft case, where the Samba project's freedom to use Microsoft's standards was not assured. This recital is a new repressive measure against software developpers and users taken by the Council in 2004. The Commission had at least left room for interpretation here. See also Article 6 and 6a.Recital 17
This Directive should be without prejudice to the application of the competition rules, in particular Articles 81 and 82 of the Treaty.
 
Article 1
Scope
This Directive lays down rules for the patentability of computer-implemented inventions.
   
Article 2a
(a) "computer-implemented invention" means any invention the performance of which involves the use of a computer, computer network or other programmable apparatus, the invention having one or more features which are realised wholly or partly by means of a computer program or computer programs;
A "computer-implemented invention" is any process that runs under computer control, including general purpose data processing processes (= computer programs), mechanical processes, chemical processes and anything whatsoever if only the claimant choses to incorporate computer features in the claim. Thus it is up to the patent attorney to decide whether the directive applies to his claims or not.Article 2a
'computer-implemented invention' means any invention within the meaning of the European Patent Convention the performance of which involves the use of a computer, computer network or other programmable apparatus and having in its implementations one or more non-technical features which are realised wholly or partly by a computer program or computer programs, besides the technical features that any invention must contribute;
A "computer-implemented invention" is a non-computing process (e.g. chemical process) that runs under computer control. It might have been better to call this a "computer-aided invention" or "computerised invention". Computers alone can "implement" only computing processes (= computer programs), which are not patentable inventions according to Art 52 EPC.
Article 2b
(b) "technical contribution" means a contribution to the state of the art in a field of technology which is new and not obvious to a person skilled in the art. The technical contribution shall be assessed by consideration of the difference between the state of the art and the scope of the patent claim considered as a whole, which must comprise technical features, irrespective of whether or not these are accompanied by non-technical features.
"technical contribution" is a contribution in a field of technology which is not obvious, but which can be entirely non-technical itself (the "claim as a whole" must contain technical features, but the technical contribution itself does not). Thanks to the insertion of the word "new" upon request of the German delegation, the technical contribution seems to have become subject to a novelty test, just like the "invention", of which it was originally a synonym. Thereby the Council seems to be departing from EPO practise and moving toward the Parliament's view. However, the Council's "technical contribution" may consist only of non-technical features: it is enough if the "claim as a whole" contains technical features.Article 2b
"technical contribution", also called "invention", means a contribution to the state of the art in a technical field. The technical character of the contribution is one of the four requirements for patentability. Additionally, to deserve a patent, the technical contribution has to be new, non-obvious, and susceptible of industrial application. The use of natural forces to control physical effects beyond the digital representation of information belongs to a technical field. The processing, handling, and presentation of information do not belong to a technical field, even where technical devices are employed for such purposes.
"technical contribution" is the same as an invention: "what you invent is your technical contribution to the state of the art". Thereby the Parliament clearly departs from the recent counter-intuitive usages of the EPO and returns to the traditional usage of the term. Moreover, the Parliament explains the term "technical" both by definition and by a negative example, thereby also clarifying the application of Art 27 TRIPs in European patent law. Moroever, the "technical contribution" must, according to the Parliament, consist solely of technical features, as explained in Art 4(3).
  Article 2ba
(ba) 'technical field' means an industrial application domain requiring the use of controllable forces of nature to achieve predictable results. 'Technical' means 'belonging to a technical field'.
For the Parliament, the term "technical" means something. For the Council it does not. An alternative phrasing could have been "technology = applied natural science".
  Article 2bb
'industry' within the meaning of patent law means the automated production of material goods;
A clarification of another key terms used in Art 27 TRIPs and in the directive proposal. The Parliament returns to a traditional definition that is found implicitely and explicitely in various national patent laws in Europe and in Art 52(4) EPC, but has been largely forgotton or diluted at the EPO.
Article 3
- Deleted -
Leave the magic words from TRIPs undefined, so that they can continue to be used to push for extension of patentability.Article 3a
Member States shall ensure that data processing is not considered to be a field of technology within the meaning of patent law, and that innovations in the field of data processing are not considered to be inventions within the meaning of patent law.
Data processing has nothing to do with the machinery used for it. The latter is patentable, the former not. This is a clear and simple negative definition of a key term used in the TRIPs treaty. It is achieved by a straightforward semantic transformation of Art 52(2) EPC.
 Article 2b ff.: The "technical contribution" may consist solely of non-technical featuresArticle 4(3)
The significant extent of the technical contribution shall be assessed by consideration of the difference between all of the technical features included in the scope of the patent claim considered as a whole and the state of the art, irrespective of whether or not such features are accompanied by non-technical features.
The "technical contribution" must consist of technical features.
  Article 4.3a
3a. In determining whether a given computer-implemented invention makes a technical contribution, the following test shall be used: whether it constitutes a new teaching on cause-effect relations in the use of controllable forces of nature and has an industrial application in the strict sense of the expression, in terms of both method and result.
Another definition of "technical contribution" aka "invention" on the basis of the terms "technical" and "industrial" with their traditional clearly delimiting meanings.
Article 4.A
A computer program as such cannot constitute a patentable invention.
A computer-implemented invention shall not be regarded as making a technical contribution merely because it involves the use of a computer, network or other programmable apparatus. Accordingly, inventions involving computer programs, whether expressed as source code, as object code or in any other form, which implement business, mathematical or other methods and do not produce any technical effects beyond the normal physical interactions between a program and the computer, network or other programmable apparatus in which it is run shall not be patentable.
This article is based on a JURI amendment (= amendment from the people who also run the Council's working party) that made it through the EP Plenary Session only because it is meaningless and therefore harmless. The Council's additions however make this amendment harmful. They use the wording of Art 52 EPC and insinuate that a "program as such" is only the "expression" side of this program, i.e. narrow copyright-style claims that nobody would write into a patent anyway. This interpretation does not conform to the usual requirements of interpretation of laws and is not currently in use at the patent courts. It deprives Art 52 EPC of all limiting meaning.Article 4.A
A computer-implemented invention shall not be regarded as making a technical contribution merely because it involves the use of a computer, network or other programmable apparatus. Accordingly, inventions involving computer programs which implement business, mathematical or other methods and do not produce any technical effects beyond the normal physical interactions between a program and the computer, network or other programmable apparatus in which it is run shall not be patentable.
The EP's version was brought into JURI (Legal Affairs Committee) by Arlene McCarthy in spring of 2003. Like most of the JURI amendments, it was inspired and probably drafted by circle around the Council's Patent Working Party. Unlike many of the JURI amendments, this one made its way into the final plenary decision of September 2003. This is because it is unclear and therefore harmless in a context where it co-exists with clearer provisions. Nobody except perhaps some authoritative EPO Board of Appeal knows what "normal physical interaction between a program and a computer" could be. The term means as much as "normal physical interaction between a recipe and a cook": nothing or whatever the EPO may want it to mean.
  Article 4.B
Member States shall ensure that computer-implemented solutions to technical problems are not considered to be patentable inventions merely because they improve efficiency in the use of resources within the data processing system.
Another negative definition of "technical contribution" that really excludes something. It is equivalent to Art 3a and based on the German Federal Patent Court's Error Search decision of 2002 which held that any business method would become patentable if the court were to follow the EPO's doctrine of viewing "improvements in computing efficiency" as technical contributions.
Article 5(1)
Member States shall ensure that a computer-implemented invention may be claimed as a product, that is as a programmed computer, a programmed computer network or other programmed apparatus, or as a process carried out by such a computer, computer network or apparatus through the execution of software.
The article implies that a claim to a computer running software or to a computing process running on general purpose computing equipment (= a computer program) is permissible.Article 5(1)
Member States shall ensure that a computer-implemented invention may be claimed only as a product, that is as a programmed device, or as a technical production process.
FFII's proposal for this had been: Member States shall ensure that a computerised invention may be claimed as a product, that is a set of devices connected to a data processing system, or as a process carried out by such devices.
Article 5(2)
A claim to a computer program, either on its own or on a carrier, shall not be allowed unless that program would, when loaded and executed in a computer, programmed computer network or other programmable apparatus, put into force a product or process claimed in the same patent application in accordance with paragraph 1.
You can get a monopoly on a certain kind of computer program on its own "only" if you also asked for a monopoly on this kind of computer program executing on a computer. The practical result is that not only the usage of such computer programs, but also their publication and distribution is forbidden. Together with the Council's Art 4A, this provision reinterprets Art 52 EPC to make it meaningless: only a narrow claim to a particular textual expression of a program is construed to be directed to that program "as such", whereas a broad claim to a whole class of "programs on their own" is not directed to these programs as such.Article 5.1b
1b. Member States shall ensure that the production, handling, processing, distribution and publication of information, in whatever form, can never constitute direct or indirect infringement of a patent, even when a technical apparatus is used for that purpose.
Program claims are not permissible, nor is it permissible to obtain a monopoly on publication and distribution by other forms of claims. The Parliament concretises Art 10 of the European Convention on Human Rights, which mandates freedom of publication. During the JURI vote of 2003-06-17, this amendment was not put to vote because the equivalent of the Council's Art 5(2) had already been approved, and these two were considered mutually exclusive by the rapporteur Arlene McCarthy. However the Parliament's plenary session scrapped Art 5(2) and voted for 5.1b instead.
 No objections against the EPO's practise of granting patents on problem specifications where not even one implementation example is disclosed in a verifiable way.Article 5.1d
1d. Member States shall ensure that whenever a patent claim names features that imply the use of a computer program, a well-functioning and well documented reference implementation of such a program shall be published as a part of description without any restricting licensing terms.
The patent system should take its disclosure function seriously. If patents are a "monopoly in return for disclosure" deal, then programming logic is on the disclosure side of that deal.
Article 6
The rights conferred by patents granted for inventions within the scope of this Directive shall not affect acts permitted under Articles 5 and 6 of Directive 91/250/EEC on the legal protection of computer programs by copyright, in particular under the provisions thereof in respect of decompilation and interoperability.
entirely impractical and only exeptional restriction of patent priviledges. Reverse engineering and decompilation may not be forbidden by using patents (this is a tautology: patents simply cannot be used to forbid those things, they fall entirely under copyright law: patents are about usage of something, not about studying it).Article 6
The rights conferred by patents granted for inventions within the scope of this Directive shall not affect acts permitted under Articles 5 and 6 of Directive 91/250/EEC on the legal protection of computer programs by copyright, in particular under the provisions thereof in respect of decompilation and interoperability.
The Parliament also left this meaningless text from the Commission's proposal untouched but supplemented it with Art 6a, which the Council rejects.
 Use of patented techniques for interoperation is a patent infringement. Exceptions for the benefit of interoperability can be made only in rare cases after lengthy and unpracticable legal procedings. See also Recital 17.Article 6a
Member States shall ensure that, wherever the use of a patented technique is needed for a significant purpose such as ensuring conversion of the conventions used in two different computer systems or networks so as to allow communication and exchange of data content between them, such use is not considered to be a patent infringement.
The right to interoperate limits the right of the patent holder to enforce his patent. As long as software patents stay invalid, this clause should never need to be used, but it is a useful clarification of Art 30 TRIPs nevertheless.
[ EU Council 2004 Proposal on Software Patents | EU Software Patent Directive: Parliament's vs Council's Version | EICTA ]
http://swpat.ffii.org/papers/europarl0309/cons0401/tab/index.en.html
© 2004/10/21 (2004/08/24) Workgroup
translated by 2004/10/21