Year: 2002
Type: article
Abstract: I. INTRODUCTION Since Federal Circuit's 1995 decision in In re and United States Patent and Trademark Office's (PTO) subsequent issuance of its Guidelines for Computer Related Inventions (PTO Guidelines) in 1996, programs embodied in a computer-readable medium are now considered patentable subject matter under 35 U.S.C. [section] 101 by PTO. (1) Specifically, patent now commonly referred to as Beauregard claims, that recite an invention embodied in a computer-readable medium are readily allowed by PTO as long as they satisfy novelty, non-obviousness, and utility requirements of 35 U.S.C. [subsection] 102 and 103. (2) However, Federal Circuit has never definitely concluded whether such embodied programs are indeed patentable. Therefore, question is raised, what does PTO mean by a computer program? (3) To appreciate ambiguity of term computer program, imagine a scenario in which a programmer at a security company is searching Web for an elegant solution to a cryptographic problem. He comes across a cryptography open source project Web site that appears to offer such a solution. The programmer downloads source code from Web site onto his computer's hard drive. However, after inspecting source code, he concludes that solution provided by source code is not sufficiently robust to be used at his company and decides not to use code. Now, further assume that unknown to either programmer or open source project, functionality described in downloaded source code is covered by a third party's patent (i.e., in form). By simply downloading source code onto his hard drive (i.e., a computer-readable medium), has programmer infringed third party's patent? In a world where source code on a hard drive is a embodied in a computer-readable medium programmer has infringed third party's patent, because by merely downloading source code, programmer has made under Patent Act. (4) Thus, under such an interpretation of computer program, any person or company wishing to assess quality of source code by downloading a copy simply to examine it, without even compiling or executing it, could potentially be infringing another's patent. Such potential for patent liability could discourage widespread distribution of source code that produces exchange of new ideas, innovative theories and techniques, and secure coding practices that are so valued by open source ideal. As such, those in open source community typically view software as the monster hiding under every developer's bed. (5) Nevertheless, rather than addressing ambiguities of patentability in current legal framework, much of open source discussion regarding patents focuses on lack of novelty or obviousness in patent claims. (6) It is far from clear whether we live in a world where source code on a hard drive (or any other computer-readable medium) is considered statutory subject matter as a computer program by PTO or Federal Circuit. This Article explores current legal framework regarding and patents. It explores distinctions between source code and object code and discusses legal ramifications of these distinctions in patent law. Part II provides a brief discussion of technical distinctions between source code and object code. Part III explores issue of whether source code infringes patents, presents an argument that infringement of by source code may overextend patent jurisprudence, and points out ambiguities of PTO with regard to claims when applied to source code. Finally, Part IV examines implications of foregoing for open source community and concludes that if source code does not infringe patents, then many important open source activities may be free from patent concerns. …
Authors: Daniel S. Lin, Matthew Sag, Ronald S. Laurie
Language: English
Topic: Intellectual Property Law
Subfield: Law
Field: Social Sciences
Domain: Social Sciences
Open Access status: green
OpenAlex ID: W1585130830
