Software Patents > Archive > Quotations
| ||||
| Archive | Net Mirror | Data Medium | Printables | Quotations |
The chief blue suit orchestrated the presentation of the seven patents IBM claimed were infringed, the most prominent of which was IBM's notorious "fat lines" patent: To turn a thin line on a computer screen into a broad line, you go up and down an equal distance from the ends of the thin line and then connect the four points. You probably learned this technique for turning a line into a rectangle in seventh-grade geometry, and, doubtless, you believe it was devised by Euclid or some such 3,000-year-old thinker. Not according to the examiners of the USPTO, who awarded IBM a patent on the process.
After IBM's presentation, our turn came. As the Big Blue crew looked on (without a flicker of emotion), my colleagues--all of whom had both engineering and law degrees--took to the whiteboard with markers, methodically illustrating, dissecting, and demolishing IBM's claims. We used phrases like: "You must be kidding," and "You ought to be ashamed." But the IBM team showed no emotion, save outright indifference. Confidently, we proclaimed our conclusion: Only one of the seven IBM patents would be deemed valid by a court, and no rational court would find that Sun's technology infringed even that one.
An awkward silence ensued. The blue suits did not even confer among themselves. They just sat there, stonelike. Finally, the chief suit responded. "OK," he said, "maybe you don't infringe these seven patents. But we have 10,000 U.S. patents. Do you really want us to go back to Armonk [IBM headquarters in New York] and find seven patents you do infringe? Or do you want to make this easy and just pay us $20 million?" After a modest bit of negotiation, Sun cut IBM a check, and the blue suits went to the next company on their hit list.
In corporate America, this type of shakedown is repeated weekly. The patent as stimulant to invention has long since given way to the patent as blunt instrument for establishing an innovation stranglehold.
Physical machinery isn't so predictable, because physical objects are quirky. If a program says to count the numbers from one to a thousand, it will do exactly that. If you build the counter out of machinery, a belt might slip and count the number 58 twice, or a truck might go by outside and you'll skip 572. These problems make designing reliable physical machinery very hard.
When we programmers put a while statement inside an if statement, we don't have to worry about whether the while statement will run such a long time that it will burn out the if statement, or that it will rub against the if statement and wear it out. We don't have to worry that it will vibrate at the wrong speed and the if statement will resonate and crack. We don't have to worry about physical replacement of the broken if statement. We don't have to worry about whether the if statement can deliver enough current to the while statement without a voltage drop. There are many problems of hardware design that we don't have to worry about.
The result is that software is far easier to design, per component, than hardware. This is why designers today use software rather than hardware wherever they can. This is also why teams of a few people often develop computer programs of tremendous complexity.
People naively say to me, "If your program is innovative, then won't you get the patent?" This question assumes that one product goes with one patent.
In some fields, such as pharmaceuticals, patents often work that way. Software is at the opposite extreme: a typical patent covers many dissimilar programs and even an innovative program is likely to infringe many patents.
That's because a substantial program must combine a large number of different techniques, and implement many features. Even if a few are new inventions, that still leaves plenty that are not. Each technique or feature less than two decades old is likely to be patented already by someone else. Whether it is actually patented is a matter of luck.
[...]
I've explained how patents impede progress. Do they also encourage it?
Patents may encourage a few people to look for new ideas to patent. This isn't a big help because we had plenty of innovation without patents. (Look at the journals and advertisements of 1980 and you'll see.) New ideas are not the limiting factor for progress in our field. The hard job in software is developing large systems.
People developing systems have new ideas from time to time. Naturally they use these ideas. Before patents, they published the ideas too, for kudos. As long as we have a lot of software development, we will have a steady flow of new published ideas.
The patent system impedes development. It makes us ask, for each design decision, "Will we get sued?" And the answer is a matter of luck. This leads to more expensive development and less of it.
With less development, programmers will have fewer ideas along the way. Patents can actually reduce the number of patentable ideas that are published.
[...]
A decade ago, the field of software functioned without patents. Without patents, it produced innovations such as windows, virtual reality, spreadsheets, and networks. And because of the absence of patents, programmers could develop software using these innovations.
We did not ask for the change that was imposed on us. There is no doubt that software patents tie us in knots. If there's no clear and vital public need to tie us up in bureaucracy, untie us and let us get back to work!
The american experience of software patents is a disaster. Before imitating them we should rather try to see if they won't agree to change their system.
In order to do that, it will be necessary to lobby the big american corporations.
The european software companies prefer to live with the pressure of having to improve constantly to the pressure of having to apply for patents, attack other companies and live with a constant risk of infringing on other companies' patents
Free software is an orthogonal problem. One could imagine applying for patents before publishing free software on the Net and thus creating inextricable legal situations.
The argument that the software startups are not able to access capital without patents is a lie. I have never encountered this kind of case.
[...]
The time and money we spend on patent filings, prosecution, and maintenance, litigation and licensing could be better spent on product development and research leading to more innovation. But we are filing hundreds of patents each year for reasons unrelated to promoting or protecting innovation.
[...]
Moreover, stockpiling patents does not really solve the problem of unintentional patent infringement through independent development. If we are accused of infringement by a patent holder who does not make and sell products, or who sells in much smaller volume than we do, our patents do not have sufficient value to the other party to deter a lawsuit or reduce the amount of money demanded by the other company. Thus, rather than rewarding innovation, the patent system penalizes innovative companies who successfully bring new products to the marketplace and it subsidizes or rewards those who fail to do so.
Our business and results of operations will be harmed if we are unable to acquire licenses for third party technologies on reasonable terms.
We remain dependent in part on third party license agreements which enable us to use third party technology to develop or produce our products. However, we cannot be certain that any such licenses will be available to us on commercially reasonably terms, if at all.
In sum, largely because the current patent system is poorly fashioned for the software design tool industry, the industry has evolved to minimize the impact that patents have on competition and has relied on other more market-oriented drivers of innovation. I believe this is a missed opportunity for accelerating technological and economic growth in the industry.
I recently took one of my lead developers, a gentleman who's widely considered a leader in his field -- he sits on both the MPEG and the ITU committees, is deeply involved with the entire intellectual property landscape around digital video -- and asked him to evaluate a particular patent that we've been hearing about in the marketplace.
We did a quick search on the USPTO website, which by the way is very useful, and uncovered no less than 120 patents that claim to be within the general scope of this particular patent, which was widely cited.
The poor guy spent the better part of five days examining all these different patents and came back to me saying, "I haven't the slightest idea whether or not we infringe on these patents, and frankly, they all seem to infringe on one another."
The end result being that I have no idea whether my product infringes on upwards of 120 different patents, all of which are held by large companies who could sue me without thinking about it.
The end result, much like Borland, I have now issued a directive that we reallocate roughly 20 to 35 percent of our developer's resources and sign on two separate law firms to increase our patent portfolio to be able to engage in the patent spew conflict. I think the concept here would be called saber rattling. I need to be able to say, "Yeah, I've got that patented too, so go away and leave me alone."
[...]
For example, when we at Adobe founded a company on the concept of software to revolutionize the world of printing, we believed that there was no possibility of patenting our work. That belief did not stop us from creating that software, nor did it deter the savvy venture capitalists who helped us with the early investment. We have done very well despite our having no patents on our original work.
On the other hand, the emergence in recent years of patents on software has hurt Adobe and the industry. A "patent litigation tax" is one impediment to our financial health that our industry can ill-afford. Resources that could have been used to further innovation have been diverted to the patent problem. Engineers and scientists such as myself who could have been creating new software instead are working on analyzing patents, applying for patents and preparing defenses. Revenues are being sunk into legal costs instead of into research and development. It is clear to me that the Constitutional mandate to promote progress in the useful arts is not served by the issuance of patents on software.
There are patents that come out today with hundreds of claims, unintelligible to almost anyone except the people who drew them. And yet, people who violate them jeopardize sometimes a lifetime of investment or their division or their product. That system doesn't work well to spur innovation or carry out the constitutional mandate.
Indeed, for those of you who were here this morning and listened to the people in the software industry talk about how threatening this is to their businesses, as I see it, patents today are often entrenching the established at the expense of allowing the newcomer to come in. I question today whether a Steve Jobs could start an Apple or a Bill Gates could start a Microsoft in view of the web and thicket of patents that is out there.
Patent law provides to inventors an exclusive right to new technology in return for publication of the technology. This is not appropriate for industries such as software development in which innovations occur rapidly, can be made without a substantial capital investment, and tend to be creative combinations of previously-known techniques.
[...]
Unfortunately, as a defensive strategy, Oracle has been forced to protect itself by selectively applying for patents which will present the best opportunities for cross-licensing between Oracle and other companies who may allege patent infringement.
The fundamental question is: Do we want to permit the monopoly possession of everything that works like logical intellectual processes. I hope not.
The mind has always been sacrosanct. The claim that intellectual processes and logical procedures (that do not primarily manipulate devices) can be possessed and monopolized extends greed and avarice much too far. Algorithmic intellectual processes must remain unpatentable -- even when represented by binary coding in a computer; even when executed by the successor to the calculator.
[...]
What frightens and infuriates so many of us about software patents is that they seek to monopolize our intellectual processes when their representation and performance is aided by a machine.
[...]
Everything that is represented or performed by software is first a completely-detailed algorithmic intellectual process. There are no exceptions, other than by error.
Thus, I respectfully object to the title for these hearings -- "Software-Related Inventions" -- since you are not primarily concerned with gadgets that are controlled by software. The title illustrates an inappropriate and seriously-misleading bias. In fact, in more than a quarter-century as a computer professional and observer and writer in this industry, I don't recall ever hearing or reading such a phrase -- except in the context of legalistic claims for monopoly, where the claimants were trying to twist the tradition of patenting devices in order to monopolize the execution of intellectual processes.
[...]
There is absolutely no evidence, whatsoever -- not a single iota -- that software patents have promoted or will promote progress.
[...]
The company for which I am speaking, Autodesk, holds some number of software patents and has applied for others -- which, of course, remain secret under current U.S. law. However, all are defensive -- an infuriating waste of our technical talent and financial resources, made necessary only by the lawyer's invention of software patents.
Autodesk has faced at least 17 baseless patent claims made against it and has spent over a million dollars defending itself, with millions more certain to pour down the bottomless patent pit unless we halt this debacle. Fortunately -- unlike smaller software producers -- we have the financial and technical resources to rebuff such claims. We rebutted all but one of the claims, even before the patent-holders could file frivolous law-suits, and will litigate the remaining claim to conclusion. Note that your Office has issued at least 16 patents that we have successfully rebutted, and we never paid a penny in these attempted extortions that your Office assisted.
But it was an enormous waste of resources that could have better been invested in useful innovation. These unending baseless claims benefit patent lawyers, but they certainly do not promote progress.
[...]
We offer two recommendations, the second having twelve parts -- so to speak, the 12 Apostles of Redress:
FIRST: Issue a finding that software, as I have defined it, implements intellectual processes that have no physical incarnation; processes that are exclusively analytical, intellectual, logical and algorithmic in nature. Use this finding plus the clearly-stated Constitutional intent, to declare that the Patent Office acted in error when it granted software patents. Declare that software patents monopolize intellectual and algorithmic processes, and also fail to fulfill the Constitutional mandate to promote progress -- that in fact, they clearly threaten it.
[...]
SECOND: Until -- and only until -- software patents are definitively prohibited, reject or at least freeze all such applications that have not yet been granted, pending conclusive action on all of the following twelve recommendations:
REDRESS SERIOUS ERRORS OF PREVIOUS ADMINISTRATIONS: Issue a finding that there have been extensive and serious errors of judgment in a large percentage of software patents granted in the past, and immediately recall all software patents for re-review and possible revocation.
[...]
Let us stand on each others' shoulders, rather than on each others' toes.
[...]
The period of patent protection, 17 years, no longer makes sense in an era when an entire generation of technology passes within a few years.
[...]
If some future litigant is successful in upholding rights to one of these "bad" patents, it will require expensive and time-consuming litigation, whose outcome is frankly uncertain, to defend the rights of creators which should never have been challenged in the first place.
The fact is, technical people are better off not looking at patents. If you don't know what they cover and where they are, you won't be knowingly infringing on them. If somebody sues you, you change the algorithm or you just hire a hit-man to whack the stupid git.
Do you believe a corporation should have the right to control what computer programs I can write and publish?
Without doubt not yet.
In reality, the national and conventional rules are clear: they stipulate without ambiguity a principle of non-patentability of software. The game which is being played today consists in twisting these rules one way or another, e.g. by imagining to consider, as we have seen, the totality of software and hardware as a virtual machine which is potentially patentable (tomorrow ...). From that point on one can speak about software in patent language. The patents which may be obtained this way, by this channel or by another, however still do not have any value beyond what we lend to them - but of course it is possible that they will finally acquire a value simply through an informal consensus to stop discussing the question. In fact, the efficiency of this twisting of rules of law is largely dependent on whether this consensus evolves to take for granted -- against the rules of written law -- that we will play this game or not. This question is no longer a legal question in the strict sense of the term.
In this domain, we must base our judgement on the evolution of the written rules, i.e. whether the exclusions of non-patentable subject matter are deleted or not.
...
It can furthermore be argued with good reasons that, given the unanimity with which the jurisdiction and the legal literature have always insisted on limiting the patent system to technical inventions, the above reasoning constitutes a theorem of customary patent law.
Whether we want to postulate such a theorem is however not essential for this discussion, because also from a purely objective point of view the concept of technical character seems to be the only usable criterion for delimiting inventions against other human mental achievements, for which patent protection is neither intended nor appropriate. If we gave up this delimitation, there would for example no longer be a secure possibility of distinguishing patentable achievements from achievements, for which the legislator has provided other means of protection, especially copyright protection. The system of German industrial property and copyright protection is however founded upon the basic assumption that for specific kinds of mental achievements different specially adapted protection regulations are in force, and that overlappings between these different protection rights need to be excluded as far as possible. The patent system is also not conceived as a reception basin, in which all otherwise not legally privileged mental achievements should find protection. It was on the contrary conceived as a special law for the protection of a delimited sphere of mental achievements, namely the technical ones, and it has always been understood and applied in this way.
Any attempt to attain the protection of mental achievements by means of extending the limits of the technical invention -- and thereby in fact giving up this concept -- leads onto a forbidden path. We must therefore insist that a pure rule of organisation and calculation, whose sole relation to the realm of technology consists in its usability for the normal operation of a known computer, does not deserve patent protection. Whether it can be awarded protection under some other regime, e.g. copyright or competition law, is outside the scope of our discussion.
[...]
In considering whether an invention is present, [the examiner] should disregard the form or kind of claim and concentrate on the content in order to identify the novel contribution which the alleged
So pflegen das Erarbeiten des Lösungsprinzips, das einem Computerprogramm zugrundeliegt, seine Umsetzung in Programmvorstufe wie Ablaufplan oder Datenflussplan und schließlich das maschinenlesbare Programm selbst beträchtlichen Aufwand zu erfordern. Die geistigen Leistungen, die dabei erbracht werden, sind gewiss nicht generell geringer als bei vielen patentwürdigen technischen Erfindungen. Wirtschaftlich ist Datenverarbeitungs-Software oft von bedeutendem Wert; ...
Der BGH lehnt es freilich ab, auf das Erfordernis des technischen Charakters zu verzichten.
...
Durch Ausdehnung des Technikbegriffs den Anwendungsbereich des Patentschutzes zu erweitern, hält der BGH ebenfalls nicht für richtig.
...
National Research Council of the USA 2000
Im Falle seiner Lockerung werde Schritt für Schritt allen Lehren für verstandesmäßige Tätigkeit der Patentschutz eröffnet; hiergegen bestünden Bedenken insbesondere wegen der Freihaltebedürfnisse in Bezug auf Arbeitsergebnisse und Methoden der Betriebswirtschaft (für Management, Organisation, Rechnungswesen, Finanzierung, Werbung, Marketing usw.), die von allen Wirtschaftsunternehmen benötigt würden, und auf Algorithmen, wie sie Computerprogrammen zugrundeliegen.
Auf der anderen Seite wird eine Überprüfung des Ausschlusses nichttechnischer Handlungsanweisungen verlangt, da er vorwiegend historisch bedingt und nicht mehr zeitgemäß sei.
2. Für das geltende Recht wird es bei der vom BGH bekräftigten Begrenzung des Patentschutzes auf technische Erfindungen sein Bewenden haben müssen. Neben der ausdrücklichen Regelung in §1 Abs 2 PatG und Art 52 Abs 2 EPÜ erlaubt es auch die bestehende institutionelle und organisatorische Ausgestaltung des Patentwesens, die durchweg auf das Gebiet der Technik zugeschnitten ist, nicht, hierüber durch richterliche Rechtsfortbildung hinauszugehen.
Eine gesetzgeberische Fortentwicklung hätte jedenfalls daran festzuhalten, dass Ausschlussrechte von nicht übersehbarer Tragweite vermieden werden müssen; mindestens Entdeckungen, wissenschaftlichen Theorien und mathematischen Methoden müsste deshalb der Patentschutz verschlossen bleiben.
3. Dagegen ist im Bereich der nichttechnischen Handlungsanweisungen und der Informationsvermittlung nicht notwendigerweise der mögliche Anwendungsbereich von Neuerungen so breit, dass die Reichweite eines Ausschlussrechts unkalkulierbar werden muss. Ob sich die Zulassung zum Patentschutz empfiehlt, hängt davon ab, wie die Schutz- und Belohnungsinteressen im Vergleich zu den Freihaltebedürfnissen zu werten sind.
Tendenziell dürfte hierbei das Freihaltebedürfnis schwerer wiegen als bei technischen Erfindungen, weil Ausschlussrechte an Neuerungen, die der Mensch ohne Einsatz von Naturkräften benutzen kann, weniger als solche an technischen Erfindungen durch außerhalb seiner selbst liegende Objekte definiert sind und deshalb regelmäßig unmittelbarer und stärker in seine Handlungsfreiheit eingreifen. Insbesondere wären von Ausschlussrechten an kommerziellen Neuerungen erhebliche wettbewerbsbeschränkende Effekte zu befürchten.
Kein hinreichendes Argument für die Gewährung von Patentschutz ist der Umstand, dass die geistige Leistung, der sie zugutekommen soll, anderweitig nicht oder nicht umfassend geschützt ist. Vielmehr können die Grenzen des nach geltendem Recht erreichbaren Schutzes auch Anzeichen dafür sein, dass den Freihaltungsinteressen der Vorrang gebührt.
[...]
Die Behauptung, die Beschränkung des Ausschlusses von Software von der Patentierbarkeit auf Software als solche in Absatz 3 habe den Zweck, im Lichte der Entwicklung der Informationstechnik durch Anerkennung der Patentierbarkeit den technischen Fortschritt zu fördern, überzeugt nicht. Falls der Gesetzgeber einen solchen Zweck verfolgt haben sollte, hätte er den Ausschluss in Absatz 2 von vornherein nicht vorgesehen. Die Unterstellung eines mit dem gewünschten Ergebnis übereinstimmenden Gesetzeszweckes ist zwar keine korrekte Anwendung der teleologischen Auslegungsmethode, zeigt aber deutlich die Bereitschaft der technischen Beschwerdekammer, die eigenen Wertungen an die Stelle der Wertung des Gesetzgebers zu setzen.
After jurisprudence has taken hold of any area treated by the law, it is up to science to develop it and all the other disciplines must resign; from now on it is the method of judicial thinking which must rule.
Recently we had to examin a patent conflict with a US patent and employed a highly specialised german patent law firm for this purpose.
The diagnosis of this firm (costing 4000,00 eur) was: for examining whether the US patent in question is being violated, the US patent attorney demanded pre-payment of 25,000.00 USD. Moreover, we were told that, as a result of this work, we would still not receive any definite information as to whether we are infringing or not. The answer would rather be something like "possibly ...", "it can not be excluded that ...". This was not to say that the US colleague was not competent. Rather, the german patent law took account of the common experience that in the field of bioinformatics reliable patent examinations are simply no longer feasible.
Developed and developing countries have historically provided that certain things do not constitute inventions for the purpose of patent protection. Included in these are those set out, for example, in Article 52 of the European Patent Convention (EPC):
[...]
Even though subsequent EPO practice and jurisprudence have to some extent diluted the scope of these Articles,13 it would seem entirely reasonable for most developing countries to adopt this list of exclusions as a minimum.
[...]
Summary of Recommendations Relating to the Patent System
[...]
Exclude from patentability computer programs and business methods
[...]
Aus ökonomischer Sicht ist die Sinnhaftigkeit eines Patentschutzes danach zu beurteilen, ob dieser effiziente Anreize für die Investition in Forschung und Entwicklung setzt. Immaterielle Güter zeichnen sich dadurch aus, dass sie beliebig und kostenlos reproduzierbar sind und der Konsum von Wissen durch eine Person eine andere Person nicht daran hindert, dieses Wissen ebenfalls zu konsumieren. Der Einzelne wird deshalb nur so viel in die Produktion von Wissen investieren, wie er durch seinen eigenen Konsum rechtfertigen kann. Dies führt insgesamt zu einer ineffizient niedrigen Produktion von Wissen. Deshalb müssen Anreize, z.B. durch Patente, geschaffen werden, die die kostenintensive Produktion von Wissen in einem darüber hinausgehenden Maß bewirken. Ökonomisch gesehen wird bei einem Patent ein (ineffizientes) Monopol vorübergehend gewährt, um Produktionsanreize zu setzen. Das soeben dargestellte Modell ist weitgehend statisch. Kompliziertere Szenarien haben demgegenüber gezeigt, dass eine Verstärkung des Patentschutzes keineswegs zwingend zu einem vermehrten Forschungsaufwand führt. Im Gegensatz zur allgemeinen Annahme, dass weitgehender immaterialgüterrechtlicher Schutz zu höherer Investitionstätigkeit führt, vermochten Untersuchungen, die unter ähnlichen Bedingungen wie die der Softwareindustrie operiert6, eine generelle Zunahme der Ausgaben für Forschung und Entwicklung nicht nachzuweisen7. Empirische Studien über das Verhalten von kleinen und mittleren Unternehmen im Softwarebereich haben gezeigt, dass Patente für diese zu den am wenigsten effizienten Methoden des Investitionsschutzes zählen.
Vor diesem Hintergrund ist eine Ausdehnung des Patentschutzes auf Computerprogramme kritisch zu bewerten. Die Entwicklung von Software ist generell nicht kapitalintensiv, außerdem bestehen auf diesen Märkten bereits Netzeffekte, die wiederum Konzentrationstendenzen begünstigen. Durch Softwarepatente werden insbesondere für kleine und mittlere Unternehmen erhebliche Marktbarrieren entstehen. Open-Source-Softwareprodukte stellen ex definitione den Programmcode allen Interessierten zur Verfügung und könnten Patentschutz deshalb generell nicht in Anspruch nehmen. Die mit dem Patentschutz verbundene vorübergehende Monopolstellung eines Unternehmens ist geeignet, die Konzentrationstendenzen auf dem Markt für Softwareprodukte weiter zu verstärken und den Wettbewerb zu behindern.
There are many reasons to be concerned. ...
An historical awareness of the political economy of patent reform suggests that this task is not easy at the domestic policy level. This is basically because those who perceive they would lose by such reform are concentrated, powerful and active defenders of their interests. In contrast, those who would gain by patent reform are diffuse and hardly aware of their interest in the matter.
One may well wonder what the real objective of the Directive is, in particular given the explanatory memorandum, which begins with considerations about the need to protect the software industry against piracy, and in the documents appended to the Directive discusses almost exclusively software and the "software industry", whose influence on the proposal seems excessive yet entirely irrelevant, if the scope of application was really as limited as the Commission maintains.
Is it wise in today's world to widen the scope of patents, tools of the industrial age, to intellectual works which are immaterial, such as software, and to the results of running software on a computer? The reply is quite explicit and partisan in the presentation of the proposal for a directive and the impact assessment form. The narrow field of vision that has been adopted, based on the legal regime for patents as the sole motivation, without sufficient consideration of the economic factors, the impact on research or on European companies, which therefore lacks a view of the whole, is not consistent with the importance of the implications for society, for development and indeed for democracy (e-administration, education, citizens' information), which in the longterm is what is at stake.
In the case of software, the debates that have taken place since the 1970s in the main countries concerned have all led to a copyright system, although such a legal framework is not entirely suited to the sector's specific requirements. The European Directive of 1 January 1993 has shown some wisdom in encouraging interoperability among programmes so as to counteract the anti-competitive strategies of seeking a dominant position. But for several years now, US case law has been led into allowing the issuing of patents for software "components", a practice to which it had previously been hostile. And the US is putting increasing pressure on Europe to allow software patenting.
The stakes here are extremely high. Such a practice would threaten the progress of innovation in this industry, since it would lead to a compartmentalisation of knowledge and procedures, thereby preventing any interaction. The multitude of patents registered and granted in the USA include a very large number of procedures, or even algorithms. Many of them seem a long way from satisfying the criteria of novelty and originality which, theoretically, are the basis for issuing a patent.
If the issuing of patents for software became institutionalised, it would strengthen the dominant position of the biggest US market leaders in the sector. It would be a direct threat to the huge number of innovating smaller firms in Europe, the USA and in other countries. Finally, it would be a very severe handicap for the European software industry, which has a hard time remaining commercially competitive despite its high level of competence.
The patent system doesn't seem to match the rhythm of innovation in the software sector: the time required for obtaining a patent is too long, as is the patent's validity term (20 years). The innovations in the software area are by their nature very close to mathematical discoveries: a new method of calculation, new algorithm or application of a known mathematical technique to a specific problem. How and where can we draw the line of separation between software processes and intellectual methods? We should also not forget that in our intellectual property system software already enjoys a significant legal protection.
Propositions
Therefore the negotiations at the European level require firm positions: thus, as long as no favorable effects on innovation can be seen, the socialists believe that:
The patent system doesn't seem to match the rhythm of innovation in the software sector: the time required for obtaining a patent is too long, as is the patent's validity term (20 years). The innovations in the software area are by their nature very close to mathematical discoveries: a new method of calculation, new algorithm or application of a known mathematical technique to a specific problem. How and where can we draw the line of separation between software processes and intellectual methods? We should also not forget that in our intellectual property system software already enjoys a significant legal protection.
Propositions
Therefore the negotiations at the European level require firm positions: thus, as long as no favorable effects on innovation can be seen, the socialists believe that:
Cette extension incontrôlée du système de brevet dans le domaine du logiciel contribue à mettre en péril de façon croissante les entreprises informatiques européennes, les auteurs de logiciels libres et les principes fondamentaux qui ont permis l'essor de la société de l'information. Plus de 10,000 brevets logiciels ont été déposés depuis 10 ans à l'Office Européen des Brevets par des astuces de procédure cautionnées par l'OEB alors même que les guides distribués depuis 10 ans par les offices nationaux de brevets rappellent clairement que les programmes d'ordinateur ne peuvent être brevetés. Plus de 75% de ces brevets ont été déposés par des entreprises non-européennes. Nombre de ces brevets logiciels portent sur des méthodes de commerce électronique, voire des méthodes d'organisation des entreprises ou des méthodes éducatives.
Mais, comme il est rappelé dans les manuels de référence juridique tels que le Lamy Droit Informatique, ces brevets n'ont de valeur que celle que l'on veut bien leur accorder en raison de la contradiction manifeste qui existe aujourd'hui entre le droit positif et le système jurisprudentiel de l'OEB. En cas de contentieux, il n'est pas certain qu'un juge national accepterait la validité de ces brevets en raison de leur objet, manifestement contraires à l'esprit de la loi. Les détenteurs de brevets logiciels, de brevets sur le commerce électronique et de brevet Internet n'attendent donc qu'une chose pour attaquer les acteurs français et européens de la nouvelle économie: une révision de la convention de Munich qui supprimerait l'exception sur les programmes d'ordinateurs.
Aussi, je vous serais reconnaissant de bien vouloir user dans les consultations nationales, européennes ou mondiales à venir, de tous les moyens qui sont en votre pouvoir pour exiger:
Aucune étude n'ayant été publiée par l'Office Européen des Brevets pour justifier l'intérêt économique de l'extension au logiciel de la brevetabilité, alors même que des économistes ont démontré que le système de brevet pouvait aboutir à une diminution de l'innovation dans l'économie du logiciel, il me semblerait également opportun de commanditer un audit de l'Office Européen des Brevets afin de déterminer les moyens de mieux contrôler les décisions de cet organisme et de s'assurer qu'elles sont bien conformes à l'intérêt général et au principe fondamental d'impartialité de la justice.
Computerprogramme "als solche" sind nach dem Europäischen Patent-Übereinkommen (EPÜ) nicht patentierbar. In den USA dagegen ist grundsätzlich alles menschengemachte patentierbar.
Bei Software-Entwicklern und in der Open-Source-Szene besteht erhebliche Verunsicherung, weil befürchtet wird, dass über die Novelle des EPÜ und eine angekündigte Richtlinie der Europäischen Kommission in Europa amerikanische Verhältnisse eingeführt werden sollen.
In den USA wird der Wettbewerb bereits erheblich auch durch die Patentierung von Geschäftsideen behindert. Viel zitiertes Beispiel ist das Patent von Amazon auf das one-click-Verfahren bei der Bestellung von Gütern im Internet.
Allerdings ist bereits in den letzten Jahren in Europa Software zunehmend als Bestandteil technischer Verfahren patentiert worden, denn: Technische Verfahren, die Computerprogramme beinhalten, sind patentierbar. Beispiel dafür ist eine computergesteuerte Werkzeugmaschine, die insgesamt patentierbar ist. Es mangelt derzeit an eingehenden ökonomischen Analysen, die die Wirkungen einer möglichen Patentierung von Software beschreiben. Wir sehen allerdings die Gefahr einer weiteren Verstärkung von Bürokratie mit dem Effekt, dass dringend notwendige Innovationen behindert werden.
Die Ermöglichung der Patentierung von Software würde darüber hinaus erhebliche technische und administrative Probleme schaffen: in der Zeit, die Anmeldung eines Patentes derzeit benötigt (derzeit 2 Jahre), ist das Patent längst veraltet. Die Dokumentation der Patente wäre extrem aufwendig. Kleine und mittlere Unternehmen würden durch die Patentierung benachteiligt: Große Firmen, die über die Ressourcen verfügen, die Patententwicklung zu verfolgen und Patente anzumelden könnten auf diese Weise zusätzliche Erträge erwirtschaften. Der Wettbewerb würde sich von der schnellen Umsetzung von Innovationen auf juristische Streitereien verlagern und der technische Fortschritt würde behindert werden. Das muss verhindert werden!
Selbst wenn es gelänge, Bereiche der Informationstechnik zu finden, in denen Patente nachweislich vorteilhaft wirken oder gewirkt haben, müsste man noch immer untersuchen, ob eventuelle schädliche Nebenwirkungen der Patentierung diese Vorteile nicht überwiegen.
Aber während bei der Legislative noch vollkommene Unklarheit herrscht, schreitet die Judikative bereits zur Tat, gewährt Tausende von Softwarepatenten und drängt auf Änderung der Gesetzesregeln. Es ist daher höchste Zeit für uns als Gesetzgeber, uns um diese Fragen zu kümmern.
Wir sollten sehr kritisch prüfen, ob wir auf dem schnellebigen Gebiet der Software einen exklusiven Patentschutz wollen. Denn die Patentierung von Software ist ein höchst zweischneidiges Unterfangen. Dem Schutzinteresse Einzelner steht die Innovationsfähigkeit der gesamten Branche gegenüber. Es sollte aufhorchen lassen, dass der zweitgrößte Softwarehersteller der Welt ORACLE sich aus diesem Grund massiv gegen Softwarepatente ausspricht. Insbesondere die in Europa starke und zukunftsträchtige Bewegung der freien Software (OpenSource wie LINUX) wäre durch Softwarepatente in ihren Grundfesten gefährdet.
Softwarepatente bergen die Gefahr in sich, daß die Großen der Branche dank Finanz und Personalkraft kleine und mittelständische Softwareschmieden mittels der Patentierung existenziell gefährden werden. Die Verfahren gegen Microsoft belegen aber deutlich, wie wichtig und schwierig Wettbewerb schon heute im Softwarebusiness ist. Die heftigen Debatten um Softwarepatente in den USA, aufgekommen durch die Patente für amazon.com, sollten Europa eine Mahnung sein. Wir sollten nicht um jeden Preis alles von Amerika übernehmen.
Europa wäre gut beraten, bei den Softwarepatenten an die meist klein- und mittelständische Struktur seiner Softwareindustrie zu denken. Es wirft kein gutes Licht auf das Gewicht die Bundesregierung, dass sie sich nicht im Verwaltungsrat gegen die Softwarepatentierung durchsetzen konnte. Die Märkte von morgen sind die Märkte von Ideen. Die Gedanken, auch die zu Software geronnenen, sollten aus liberaler Sicht weitestgehend frei bleiben.