Patenting Software Is Wrong

Total Page:16

File Type:pdf, Size:1020Kb

Patenting Software Is Wrong Case Western Reserve Law Review Volume 58 Issue 2 Article 7 2007 Manuscript: You Can't Patent Software: Patenting Software is Wrong Peter D. Junger Follow this and additional works at: https://scholarlycommons.law.case.edu/caselrev Part of the Law Commons Recommended Citation Peter D. Junger, Manuscript: You Can't Patent Software: Patenting Software is Wrong, 58 Case W. Rsrv. L. Rev. 333 (2007) Available at: https://scholarlycommons.law.case.edu/caselrev/vol58/iss2/7 This Tribute is brought to you for free and open access by the Student Journals at Case Western Reserve University School of Law Scholarly Commons. It has been accepted for inclusion in Case Western Reserve Law Review by an authorized administrator of Case Western Reserve University School of Law Scholarly Commons. MANUSCRIPT* YOU CAN'T PATENT SOFTWARE: PATENTING SOFTWARE IS WRONG PeterD. Jungert INTRODUCTION Until the invention of programmable' digital computers around the time of World War II, no one had imagined-and probably no one could have imagined-that methods of solving mathematical . Editor'sNote: This article is the final known manuscript of Professor PeterJunger. We present this piece to you as a tribute to Professor Junger and for your own enjoyment. This piece was not, at the time of ProfessorJunger 's passing, submitted to any Law Review or legal journal.Accordingly, Case Western Reserve University Law Review is publishing this piece as it was last edited by Professor Junger, with the following exceptions: we have formatted the document for printing, and corrected obvious typographical errors. Footnotes have been updated to the best of our ability, but without Professor Junger's input, you may find some errors. Internalreferences are likely to be inconsistent and could not be corrected without the author's input; internet sources may be out of date or unavailable. The article was originally published as a work-in-progress at Professor Junger's website, http://samsara.law.cwru.edul patart/index.html(now unavailable). t I want to thank Judith Kaul for all the assistance that she has given me over the years in locating the materials that made writing this article possible. I also want to express my great debt of gratitude to Gino J. Scarselli for all the uncompensated work that he did in establishing that the First Amendment protects the publication of software in the case of Junger v. Daley. And finally I must apologize to Flanders and Swan for appropriating-more or less-a small portion of the lyrics of You Can't Eat People for the title of this article. Among the early programmable digital computers were Konrad Zuse's Z3 developed in Germany in 1941, the Colossus (which was not fully programmable, not being Turing complete) developed by Tommy Flowers in England in 1943, and Mauchly and Eckert's ENIAC I completed in 1946 in the United States. It is also worth noting that Charles Babbage designed, but was unable to actually construct, a programmable-using punch cards--mechanical computer, called the "analytical engine," back in the second-half of the nineteenth century. See infra Part VI.A.3(a)(i). Augusta Ada King, Countess of Lovelace wrote a program for Babagge's Analytical Engine and thus is usually credited with being the world's first computer programmer. Id Both Babbage and Lady Lovelace were skilled mathematicians. CASE WESTERN RESERVE LAW REVIEW [Vol. 58:2 problems could be patented. In 1972, however, the Supreme Court of the United States2 was confronted in Gottschalk v. Benson3 with the question of whether "an application for [a patent on] an invention... related 'to the processing of data by program and more particularly to the programmed conversion of numerical information' 4 in general- purpose digital computers," 5 covered patentable subject matter; the Court held that the claimed invention was not patentable,6 in effect holding that most, and probably all, claims that relate to programs for the processing of data-that is, most claims that relate to what is commonly, but perhaps unfortunately, 7 called "software"-do not cover patentable subject matter.8 Since then the holding in Benson has not been overruled-or even questioned-by the Court, yet it appears today that most patent lawyers, and most legal academics who think about such matters, are now convinced that software is patentable and that Benson is no longer good law having, in effect. been overruled by later decisions of 9 a lower court, the Federal Court of Appeals for the Federal Circuit. It is, however, my contention in this article that Benson is still good law-after all the Supreme Court is not likely to concede that its opinions can be overruled by any of the lower courts-and, more importantly from an academic point of view, that Benson was correctly decided, for most of the arguments for overturning the holding in Benson and permitting the granting of patents on software rest on a fundamental misunderstanding of the nature of the information that is processed by-and that is all that can be processed by-a computer. Thus it is my contention here that inventions, no matter how novel or useful they may be, in the field of computer programming-that is, 2 In this article I am only concerned with the law of the United States. If I know little about U.S. patent law, I know infinitely less about that of other jurisdictions. 3 409 U.S. 63 (1972). 4 All that computer programs do can fairly be described as the conversion-i.e., the processing--of information. See infra Part VI.C. 5 409 US at 64. 6 In this article I argue at length-and, frankly, I think quite persuasively-that the holding in Benson that the application in that case did not cover a patentable invention applies to all applications for patents on inventions that consist of computer programs for the processing of data-and that all computer programs do nothing more, or less, than control the way in which a computer processes data, i.e. numerical information." For a discussion of Benson in some detail, see infra Part II.A. 7 See infra note 13 and accompanying text. 8 In Benson the Court was careful to say: "It is said that the decision precludes a patent for any program servicing a computer. We do not so hold", 409 U.S. at 71, but that cautious statement does not, of course, amount to a holding, or even a dictum, that there are programs that are patentable. 9 See infra Part 11. 2008] YOU CAN'T PATENT SOFTWARE in the field of processing data or information-are not and should not be patentable. I. COMPUTERS AND SOFTWARE We all know what computers are, or at least we think we do: they are machines 10 that process information." Few of us, on the other hand, have any idea of what information is, 12 even though we are supposedly living in an "information age." Moreover, few of us have any clear idea about what software is other than the generic name for computer programs.' 3 And most of us, I fear, do not really understand not.14 what computer programs are--or what, for that matter, they are A quick, but perhaps not too informative, definition of software is: Data that controls how a computer processes data.15 Computers, on the other hand, are tangible, kickable gadgets that will in a pinch serve as doorstops16 and that are designed to be used in the processing of information. 17 If someone were to invent a new type of computer or a new way to manufacture 8computers, there is no doubt that that invention would be patentable.' Computer programs are, according to the foregoing definition, software and they also have been defined as "a set of statements or instructions to be used directly or indirectly in a computer in order to bring about a certain result," 19 that is, in order to process information 10 And sometimes human beings. I I.e., data. For further discussion of the nature of computers, see infra Part VI.A. 12 For a discussion of the nature of information and data-which is information that is interesting enough for someone to process it in a computer-See infra Part VI.C. 13 The term "software" is misleading to the extent that it suggests that software is-that computer programs are-the same sort of "ware" as the hardware, i.e., the computer, upon which it runs. See infra Part VI.B. 14 In particular, they are not-and thus they are not patentable as-machines, manufactures, or compositions of matter. See infra note 20. 15 For a quick definition of data, see infra note 17. 16 At least in those cases where they are not human beings. See infra text accompanying notes 23 and 24. 17 Or, slightly more precisely, data. "Data" is simply information that someone finds interesting and perhaps worth processing. As to what information is, see infra Part VI.C. 18 As a machine. See infra note 20. 19This definition comes from the Copyright Act, 17 U.S.C. § 101. One caution about this definition: the term "instructions" does not imply that computers understand and obey instructions the way human beings--or even dogs--do. Digital computers mechanically carry out their instructions in the same manner that an automobile obeys the instructions transmitted to it by the steering wheel or the brake, quite without any understanding. Human computers, on the other hand, may, but are not required to, understand what it is that they are doing. The Copyright Act also provides that: "In no case does copyright protection.., extend to any idea, procedure, process, system, method of operation, concept, principle, or discovery, regardless of the form in which it is described, explained, illustrated, or embodied .
Recommended publications
  • Is Software Still Patentable?
    Is Software Still Patentable? The last four years have posed significant hurdles to software patents; nevertheless they continue to be filed and allowed. By James J. DeCarlo and George Zalepa | August 20, 2018 | The Recorder Over the past four years, decisions by the Supreme Court and Federal Circuit, as interpreted by the U.S. Patent and Trademark Office, have had a dramatic effect on software-related inventions. These decisions have focused primarily on what comprises patentable subject matter under 35 U.S.C. § 101 and whether a patent’s specification adequately supports the claims. While uncertainty still exists, recent court decisions, coupled with sound prosecution strategies, can be used to bolster a practitioner’s arguments before the USPTO and courts. In Alice v. CLS Bank (2014), the Supreme Court applied the now familiar “two-part test” first laid out in Mayo v. Prometheus (2012). Under this test, a claim is first analyzed to determine if it is “directed to” an abstract idea. If so, the claim is then analyzed to determine whether it recites “significantly more” than the identified abstract idea or just “routine and conventional” elements. This test was (and is) routinely applied to software claims, and the pendulum of patentability for software inventions post-Alice swung firmly towards ineligibility. Nearly all decisions by the Federal Circuit in the immediate aftermath of Alice found claims ineligible. Similarly, the USPTO’s allowance rate in software-related art units plummeted, and many allowed but not yet issued applications were withdrawn by the USPTO. While many cases are representative of this period, the decision in Electric Power Group v.
    [Show full text]
  • The Fuzzy Software Patent Debate Rages On
    OPINION The Fuzzy Software Patent Debate Rages On By Heather J. Meeker LinuxInsider 02/23/05 5:00 AM PT Once upon a time, we intellectual property lawyers got to live peacefully in our ivory towers. Now it seems that intellectual property policy issues have become fraught with partisan rhetoric. Most open-source promoters are against software patents. Most corporate spokesmen side with patents, period, whether they cover software or not. But it is worth looking beyond the rhetoric. The European Commission recently tolled the death knell for the EU Software Patent Directive, or more precisely, the "Directive on the Patentability of Computer- Implemented Inventions." Like most Americans, I am fairly clueless about the EU political process, and I wouldn't presume to write about exactly how it was killed. But the decision may have been swayed by an eleventh-hour public relations pitch against the directive by open-source spokesmen from the United States. On that aspect, I will add my two cents. A delegation of open-source leaders, led by Linus Torvalds, published an "Appeal" at softwarepatents.com, calling software patents "dangerous to the economy at large, and particularly to the European economy." Look Beyond the Rhetoric Leaders of the open-source software movement have long been harsh critics of software patents. The GPL [license] itself says, "any free program is threatened constantly by software patents." The appeal contends that copyright provides adequate protection for the creations of software authors. The Appeal advocated reliance on copyright law, rather than patent law, for the protection of software. Not long afterward, in late January, the European Parliament's Legal Affairs Committee recommended scrapping the pending directive, extending the debate until at least the end From www.linuxinsider.com/story/40676.html 1 April 2011 of the year.
    [Show full text]
  • Does Strict Territoriality Toll the End of Software Patents?
    NOTES DOES STRICT TERRITORIALITY TOLL THE END OF SOFTWARE PATENTS? James Ernstmeyer* INTRODUCTION ............................................................................................. 1267 I. UNITED STATES PROTECTION FOR INTELLECTUAL PROPERTY RIGHTS IN SOFTWARE ........................................................................ 1269 A. Defining Software ...................................................................... 1269 B. Copyright Protection for Software ............................................ 1270 C. Patent Protection for Software .................................................. 1272 D. The Backlash Against Intellectual Property Rights in Software ..................................................................................... 1274 E. In re Bilski Turns Back the Clock .............................................. 1278 II. UNITED STATES SOFTWARE PATENTS IN CROSS-BORDER TRADE .... 1280 A. Global Economic Stakes in United States Software Patents ..... 1280 B. Congressional Protection of Patents in Cross-Border Trade ......................................................................................... 1281 C. Extraterritoriality Concerns in Applying § 271(f) to Software Patents ........................................................................ 1283 III. DO PATENTS PROTECT SOFTWARE? – WOULD COPYRIGHTS DO BETTER? ............................................................................................ 1287 A. Effects of the Microsoft v. AT&T Loophole .............................. 1287 B. Combining
    [Show full text]
  • There Is No Such Thing As a Software Patent
    There is no such thing as a software patent 1 Kim Rubin BSEE/CS 45 years technology experience 4 startups 100+ inventions Patent Agent Author Taught computer security Book shelf for patents 2 {picture of file cabinets here} 3 There is no such thing as a software patent 4 7.5 5 7.4 6 7.3 7 There is no such thing as a software patent. There is no such thing as a rubber patent. There is no such thing as a steel patent. There is no such thing as an electricity patent. 8 There is only ... a patent. 9 pro se en banc said embodiment 10 Czapinski v. St. Francis Hosp., Inc., 2000 WI 80, ¶ 19, 236 Wis. 2d 316, 613 N.W.2d 120. v. The Federal Food, Drug, and Cosmetic Act (FDCA), ch. 675, 52 Stat. 1040, as amended, 21 U.S.C. § 301 et seq., iSee 21 U.S.C. § 355(a); Eli Lilly & Co. v. Medtronic, Inc., 496 U.S. 661, 665—666, 674 (1990). 11 Article I, Section 8 8. “To promote the Progress of Science and useful Arts, by securing for limited Times to Inventors the exclusive Right to their Discoveries.” 12 Article I, Section 8 8. “To promote the Progress of Science and useful Arts, by securing for limited Times to Inventors the exclusive Right to their Discoveries … except for software.” 13 Jefferson, Congress, SCOTUS and MPEP 3. “The Act embodied Jefferson’s philosophy that ‘ingenuity should receive a liberal encouragement.’ 5 Writings of Thomas Jefferson, 75-76 Washington ed. 1871).
    [Show full text]
  • Prior Art Searches in Software Patents – Issues Faced
    Journal of Intellectual Property Rights Vol 23, November 2018, pp 243-249 Prior Art searches in Software Patents – Issues Faced Shabib Ahmed Shaikh, Alok Khode and Nishad Deshpande,† CSIR Unit for Research and Development of Information Products, Tapovan, S.No. 113 & 114, NCL Estate, Pashan Road, Pune - 411 008, Maharashtra, India Received: 15 November 2017; accepted: 24 November 2018 Prior-art-search is a critical activity carried out by intellectual property professionals. It is usually performed based on known source of literature to ascertain novelty in a said invention. Prior-art-searches are also carried out for invalidating a patent, knowing state of the art, freedom to operate studies etc. In many technological domains such as chemistry, mechanical etc., prior art search is easy as compared to domain such as software. In software domain, prior-art can prove to be a complex and tedious process relying heavily on non-patent literature which acts as a pointer to the current technological trends rather than patent documents. This paper tries to highlight the issues faced by patent professionals while performing prior-art search in the field of software patents. Keywords: Patents, Software patents, World Intellectual Property Organisation, Prior art, Search Issues A patent is a form of intellectual property. It provides The identification of the relevant prior art, comprising exclusionary rights granted by national IP office to an of existing patents and scientific or non-patent inventor or their assignee for a limited period of time literature is important as it has bearing on the quality in exchange for public disclosure of an invention.
    [Show full text]
  • Google Inc. in Response to the PTO's Request for Comments on the Partnership for Enhancement of Quality of Software-Related Patents, Docket No
    From: Suzanne Michel Sent: Monday, April 15, 2013 8:40 PM To: SoftwareRoundtable2013 Subject: Submission of Google Inc Please find attached the submission of Google Inc. in response to the PTO's request for comments on the partnership for enhancement of quality of software-related patents, Docket No. PTO-P-2012-0052. If possible, please send an acknowledgment of receipt of the submission. Thank you very much, Suzanne Michel -- Suzanne Michel Senior Patent Counsel, Google [email protected] 202 677- | | | 5398 Before the United States Patent and Trademark Office Alexandria, VA 22313 In re: ) ) Docket No. PTO-P-2012-0052 Request for Comments and Notice ) of Roundtable Events for ) Partnership for Enhancement of ) Quality of Software-Related ) Patents ) ) COMMENTS OF GOOGLE INC. Daryl L. Joseffer Suzanne Michel KING & SPALDING LLP GOOGLE INC. 1700 Pennsylvania Avenue, NW 1101 New York Avenue, N.W. Washington, DC 20006 Washington, DC 20005 (202) 737-0500 (650) 253-0000 Adam M. Conrad KING & SPALDING LLP 100 N Tryon Street, Suite 3900 Charlotte, NC 28202 (704) 503-2600 April 15, 2013 TABLE OF CONTENTS PART I: INTRODUCTION ...................................................................................................1 PART II: THE PTO SHOULD APPLY SECTION 112(F) TO MORE PATENTS THAT CLAIM SOFTWARE-IMPLEMENTED INVENTIONS ...........................3 A. Section 112(f) Permits The Use Of Functional Claim Elements Only When The Specification Discloses Sufficient Structure To Limit The Claim To The Applicant’s Actual Invention. ...............................3 1. As A Matter Of Policy And Precedent, Patent Law Has Never Permitted Pure Functional Claiming. .......................................3 2. Congress Enacted Section 112(f) To Permit Functional Claiming Accompanied By Sufficient Disclosures.
    [Show full text]
  • Committee on Development and Intellectual Property
    E CDIP/13/10 ORIGINAL: ENGLISH DATE: MARCH 27, 2014 Committee on Development and Intellectual Property Thirteenth Session Geneva, May 19 to 23, 2014 PATENT-RELATED FLEXIBILITIES IN THE MULTILATERAL LEGAL FRAMEWORK AND THEIR LEGISLATIVE IMPLEMENTATION AT THE NATIONAL AND REGIONAL LEVELS - PART III prepared by the Secretariat 1. In the context of the discussions on Development Agenda Recommendation 14, Member States, at the eleventh session of the Committee on Development and Intellectual Property (CDIP) held from May 13 to 17, 2013, in Geneva, requested the International Bureau of the World Intellectual Property Organization (WIPO) to prepare a document that covers two new patent-related flexibilities. 2. The present document addresses the requested two additional patent-related flexibilities. 3. The CDIP is invited to take note of the contents of this document and its Annexes. CDIP/13/10 page 2 Table of Contents I. EXECUTIVE SUMMARY……………………………………………………………...…….….. 3 II. THE SCOPE OF THE EXCLUSION FROM PATENTABILITY OF PLANTS..…….…….…4 A. Introduction……..……………………………………………………………………….….4 B. The international legal framework………………………………………………………. 6 C. National and Regional implementation………………………………………………… 7 a) Excluding plants from patent protection……………………………………........ 8 b) Excluding plant varieties from patent protection………………………………... 8 c) Excluding both plant and plant varieties from patent protection……...……….. 9 d) Allowing the patentability of plants and/or plant varieties……………………… 9 e) Excluding essentially biological processes for the production of plants…….. 10 III. FLEXIBILITIES IN RESPECT OF THE PATENTABILITY, OR EXCLUSION FROM PATENTABILITY, OF SOFTWARE-RELATED INVENTIONS………………………….…….…. 12 A. Introduction………………………………………………………………………….….…12 B. The International legal framework………………………………………………………13 C. National implementations……………………………………………………………….. 14 a) Explicit exclusion …………………………………………………………………. 14 b) Explicit inclusion…………………………………………………………………... 16 c) No specific provision……………………………………………………………… 16 D.
    [Show full text]
  • How Electric Power Group Case Is Affecting Software Patents by Michael Kiklis (August 19, 2019)
    This article was originally published by Law360 on August 19, 2019. How Electric Power Group Case Is Affecting Software Patents By Michael Kiklis (August 19, 2019) Many commentators predicted the end of software patents after the U.S. Supreme Court’s Alice Corp. v. CLS Bank International decision. Software patent practitioners therefore applauded when the U.S. Court of Appeals for the Federal Circuit stated in 2016’s Enfish LLC v. Microsoft Corp. decision that “claims directed to software, as opposed to hardware, are [not] inherently abstract.”[1] But soon thereafter, our optimism waned when the Federal Circuit in Electric Power Group LLC v. Alstom SA found that data gathering, analysis and display is an abstract idea, thus rendering many software inventions abstract.[2] In fact, the Federal Circuit is recently applying Electric Power Group more Michael Kiklis frequently and has even expanded its use to find that “entering, transmitting, locating, compressing, storing, and displaying data”[3] and “capturing and transmitting data from one device to another” are abstract ideas.[4] Many software inventions — such as artificial intelligence systems — gather data, analyze that data and perform some operation that usually includes displaying or transmitting the result. Electric Power Group and its progeny therefore pose a serious risk to software inventions, including even the most innovative ones. Knowing how to avoid Section 101 invalidity risk from these cases is therefore critical. This article provides strategies for doing so. The Problem With Being Abstract Alice holds that if a claim is directed to an abstract idea and it does not recite an inventive concept, the claim is ineligible under 35 U.S.C.
    [Show full text]
  • A Symposium for John Perry Barlow
    DUKE LAW & TECHNOLOGY REVIEW Volume 18, Special Symposium Issue August 2019 Special Editor: James Boyle THE PAST AND FUTURE OF THE INTERNET: A Symposium for John Perry Barlow Duke University School of Law Duke Law and Technology Review Fall 2019–Spring 2020 Editor-in-Chief YOOJEONG JAYE HAN Managing Editor ROBERT HARTSMITH Chief Executive Editors MICHELLE JACKSON ELENA ‘ELLIE’ SCIALABBA Senior Research Editors JENNA MAZZELLA DALTON POWELL Special Projects Editor JOSEPH CAPUTO Technical Editor JEROME HUGHES Content Editors JOHN BALLETTA ROSHAN PATEL JACOB TAKA WALL ANN DU JASON WASSERMAN Staff Editors ARKADIY ‘DAVID’ ALOYTS ANDREW LINDSAY MOHAMED SATTI JONATHAN B. BASS LINDSAY MARTIN ANTHONY SEVERIN KEVIN CERGOL CHARLES MATULA LUCA TOMASI MICHAEL CHEN DANIEL MUNOZ EMILY TRIBULSKI YUNA CHOI TREVOR NICHOLS CHARLIE TRUSLOW TIM DILL ANDRES PACIUC JOHN W. TURANCHIK PERRY FELDMAN GERARDO PARRAGA MADELEINE WAMSLEY DENISE GO NEHAL PATEL SIQI WANG ZACHARY GRIFFIN MARQUIS J. PULLEN TITUS R. WILLIS CHARLES ‘CHASE’ HAMILTON ANDREA RODRIGUEZ BOUTROS ZIXUAN XIAO DAVID KIM ZAYNAB SALEM CARRIE YANG MAX KING SHAREEF M. SALFITY TOM YU SAMUEL LEWIS TIANYE ZHANG Journals Advisor Faculty Advisor Journals Coordinator JENNIFER BEHRENS JAMES BOYLE KRISTI KUMPOST TABLE OF CONTENTS Authors’ Biographies ................................................................................ i. John Perry Barlow Photograph ............................................................... vi. The Past and Future of the Internet: A Symposium for John Perry Barlow James Boyle
    [Show full text]
  • Master Thesis Innovation Dynamics in Open Source Software
    Master thesis Innovation dynamics in open source software Author: Name: Remco Bloemen Student number: 0109150 Email: [email protected] Telephone: +316 11 88 66 71 Supervisors and advisors: Name: prof. dr. Stefan Kuhlmann Email: [email protected] Telephone: +31 53 489 3353 Office: Ravelijn RA 4410 (STEPS) Name: dr. Chintan Amrit Email: [email protected] Telephone: +31 53 489 4064 Office: Ravelijn RA 3410 (IEBIS) Name: dr. Gonzalo Ord´o~nez{Matamoros Email: [email protected] Telephone: +31 53 489 3348 Office: Ravelijn RA 4333 (STEPS) 1 Abstract Open source software development is a major driver of software innovation, yet it has thus far received little attention from innovation research. One of the reasons is that conventional methods such as survey based studies or patent co-citation analysis do not work in the open source communities. In this thesis it will be shown that open source development is very accessible to study, due to its open nature, but it requires special tools. In particular, this thesis introduces the method of dependency graph analysis to study open source software devel- opment on the grandest scale. A proof of concept application of this method is done and has delivered many significant and interesting results. Contents 1 Open source software 6 1.1 The open source licenses . 8 1.2 Commercial involvement in open source . 9 1.3 Opens source development . 10 1.4 The intellectual property debates . 12 1.4.1 The software patent debate . 13 1.4.2 The open source blind spot . 15 1.5 Litterature search on network analysis in software development .
    [Show full text]
  • Intellectual Property Protection for Computer Programs
    Ekonomi och samhälle Economics and Society Skrifter utgivna vid Svenska handelshögskolan Publications of the Hanken School of Economics Nr 246 Rosa Maria Ballardini Intellectual Property Protection for Computer Programs Developments, Challenges, and Pressures for Change Helsinki 2012 < Intellectual Property Protection for Computer Programs: Developments, Challenges, and Pressures for Change Key words: computer programs, software, intellectual property law, patents, copyright, open source software © Hanken School of Economics & Rosa Maria Ballardini, 2012 Rosa Maria Ballardini Hanken School of Economics Department of Accounting and Commercial Law P.O.Box 479, 00101 Helsinki, Finland ONM VIR EN Hanken School of Economics N TA E L IC L A D B R E O ISBN 978-952-232-173-2 (printed ) L N ISBN 978-952-232-174-9 (PDF) ISSN-L 0424-7256 ISSN 0424-7256 (printed) 441 002 ISSN 2242-699X (PDF) Printed matter Edita Prima Ltd, Helsinki 2012 i PREFACE While growing up in a small, remote village in the Italian Alps, I could not help but dream about exotic destinations and faraway lands. Back then I never imagined myself embarking on a journey that would eventually materialize into a PhD project at a Finnish University. However, the greatest travels are often those without clear destinations or meticulous planning, and as it turns out this has been one of my best voyages. On this journey, I’ve drifted and sailed. Thankfully, I’ve benefited from the guidance and support of many. First and foremost, the vast academic experience and accommodating personalities of my supervisors have been crucial for developing both the research and the independent thinking skills necessary for any doctoral project.
    [Show full text]
  • Everlasting Software
    NOTES EVERLASTING SOFTWARE Software patents are some of the most commonly litigated, and pre- liminary evidence shows that they are particularly prone to ambush litigation.1 The typical ambush litigation plaintiff obtains a broadly worded patent and alleges that it covers a wide range of technologies, some of which may not even have existed at the time of the patent.2 The odd results of ambush litigation have led some commentators to call for the elimination of software patents.3 Their concerns are best illustrated with a famous example, the case of Freeny’s patent. In 1985, Charles Freeny, Jr., a computer scientist, obtained U.S. Pat- ent No. 4,528,643 on a method of remote manufacturing of goods using intermodem communication over phone lines.4 Freeny realized that it was inefficient for stores to stock electronic merchandise that might never sell.5 Therefore, he disclosed and claimed the following solution: customers would use an “information manufacturing machine[]” (IMM) at a point of sale to order goods.6 The IMM would communicate via modem with a central machine located at a remote location and receive authorization to produce the good via an authorization code.7 The IMM would then record an electronic good, such as a song, on a mate- rial object, such as a cassette, that the customer could take home.8 ––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– 1 John R. Allison et al., Patent Quality and Settlement Among Repeat Patent Litigants, 99 GEO. L.J. 677, 695–96 (2011). 2 See JAMES BESSEN & MICHAEL J. MEURER, PATENT FAILURE 66–67 (2008). 3 See, e.g., Pamela Samuelson, Benson Revisited: The Case Against Patent Protection for Al- gorithms and Other Computer Program-Related Inventions, 39 EMORY L.J.
    [Show full text]