The EU directive on computer-implemented inventions, 2002–2005
The proposed directive on computer-implemented inventions aimed to harmonize national patent laws and practices within the European Union. It concerned inventions implemented through computers, networks or other programmable equipment, rather than copyright in a program's code. Wikipedia’s account of the proposed directive records its changing texts, the arguments around them and the rejection that ended the legislative process.
A proposal to harmonize patent law and a patent office's existing practice were different things. The European Patent Office operated under the European Patent Convention and was separate from the EU institutions considering the directive. The dispute concerned what common rules would mean for the scope of patentability, as well as whether they would clarify existing practices.
The Commission proposal
The European Commission initiated the proposal on 20 February 2002, according to the directive reference article. The original draft sought to codify and harmonize national rules and the practice of granting patents for computer-implemented inventions that met specified criteria. It also addressed the exclusion of business methods as such. These were features of a proposed measure, rather than a law that had already taken effect.
The phrase technical contribution was central to the draft. The reference article describes debate over its meaning and how that meaning affected the boundary between patentable inventions and excluded subject matter. A common word in the debate did not establish agreement on the legal test. The content of the rule, rather than the mere presence of software in an invention, remained disputed.
What supporters and opponents argued
Supporters presented the measure as a way to put existing patent-office case law into a harmonized legal framework. Wikipedia records their argument that the original proposal did not extend the scope of patentability and that purely software-implemented business methods would remain excluded. On that view, technical contribution was a limit on eligibility rather than a route to patenting every program.
Opponents argued that the proposal could extend patentability rather than simply harmonize it. The reference records their view that ideas should remain outside patent protection and that copyright already protected their expression in code. Their objection concerned the effects of the proposed boundary on software development and competition, rather than a denial that code could receive copyright protection.
The same reference account of the debate records disagreement over the later Council text from both directions. Critics considered its technical-character requirement too open to interpretation; proponents also identified ambiguities that they thought undermined harmonization. These were arguments about the proposal's scope. They are distinct from a finding that either side's prediction was established as fact.
Parliament's first reading and the Council text
On 24 September 2003, Parliament approved a substantially amended text, as the directive article’s legislative history records. Its changes drew a distinction between abstract information processing and particular physical processes and included a rule concerning patents and interoperability. The reference describes these amendments as placing significant limits on software patentability compared with the original proposal.
The Council agreed an alternative version in an advisory vote on 18 May 2004 and formally approved the resolution on 7 March 2005, according to the same legislative account. That version permitted patents for computer-implemented inventions with technical character and overturned most of Parliament's amendments. The source describes the text being returned to Parliament for consideration.
Under the legislative procedure described by the reference, Parliament and the Council had to approve identical terms for the proposal to become law. Agreement on the general subject was therefore not enough. The differences between the texts concerned the actual conditions for patentability and the treatment of interoperability, which were substantive parts of the legislative decision.
Rejection and its meaning
On 6 July 2005, Parliament rejected the proposal with 648 votes for rejection, 14 against and 18 abstentions, as Wikipedia’s account of the final vote states. The rejection ended the legislative process, and the proposed directive did not become law in any form. The vote concerned the proposal before Parliament, rather than an individual patent application or patent's validity.
The reference attributes the broad rejection to different reasons among the parties: proponents of software patents feared a text that would narrow protection, while opponents rejected the principle. A common vote consequently did not imply a common account of the desired patent rules. The outcome can be stated precisely without treating it as a victory for a single substantive position.
The law left in place
Wikipedia’s European Patent Convention account explains that the exclusion of computer programs applies to programs as such, rather than every invention containing software. It distinguishes the question of technical character from novelty and inventive step. Rejection of the directive did not itself remove that existing framework or decide the eligibility of every software-related invention.
Wikipedia’s software-patent overview describes differing jurisdictional standards for granting patents involving software. Those differences help explain why harmonization was a separate policy question from granting or enforcing a patent. The legal background page examines European and U.S. tests, while the intellectual-property page distinguishes patents from copyright and licensing. The Europe policy page covers the wider public-software context.