paint-brush
Copyright Protection Can Extend to Both Literal and Non-literal Elements of a Computer Programby@legalpdf
302 reads
302 reads

Copyright Protection Can Extend to Both Literal and Non-literal Elements of a Computer Program

by Legal PDF: Tech Court CasesOctober 11th, 2023
Read on Terminal Reader
Read this story w/o Javascript
tldt arrow

Too Long; Didn't Read

It is well established that copyright protection can extend to both literal and non-literal elements of a computer program.

People Mentioned

Mention Thumbnail
featured image - Copyright Protection Can Extend to Both Literal and Non-literal Elements of a Computer Program
Legal PDF: Tech Court Cases HackerNoon profile picture

Oracle vs. Google (2014) Court Filing, retrieved on May 9, 2014, is part of HackerNoon’s Legal PDF Series. You can jump to any part in this filing here. This is part 6 of 16.

A. Copyrightability

The Copyright Act provides protection to “original works of authorship fixed in any tangible medium of expression,” including “literary works.” 17 U.S.C. § 102(a). It is undisputed that computer programs— defined in the Copyright Act as “a set of statements or instructions to be used directly or indirectly in a computer in order to bring about a certain result,” 17 U.S.C. § 101—can be subject to copyright protection as “literary works.” See Atari Games Corp. v. Nintendo of Am., Inc., 975 F.2d 832, 838 (Fed. Cir. 1992) (“As literary works, copyright protection extends to computer programs.”). Indeed, the legislative history explains that “literary works” includes “computer programs to the extent that they incorporate authorship in the programmer’s expression of original ideas, as distinguished from the ideas themselves.” H.R. Rep. No. 1476, 94th Cong., 2d Sess. 54, reprinted in 1976 U.S.C.C.A.N. 5659, 5667.


By statute, a work must be “original” to qualify for copyright protection. 17 U.S.C. § 102(a). This “originality requirement is not particularly stringent,” however. Feist Publ’ns, Inc. v. Rural Tel. Serv. Co., 499 U.S. 340, 358 (1991). “Original, as the term is used in copyright, means only that the work was independently created by the author (as opposed to copied from other works), and that it possesses at least some minimal degree of creativity.” Id. at 345.


Copyright protection extends only to the expression of an idea—not to the underlying idea itself. Mazer v. Stein, 347 U.S. 201, 217 (1954) (“Unlike a patent, a copyright gives no exclusive right to the art disclosed; protection is given only to the expression of the idea—not the idea itself.”). This distinction—commonly referred to as the “idea/expression dichotomy”—is codified in Section 102(b) of the Copyright Act, which provides:


In no case does copyright protection for an original work of authorship 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 in such work.


17 U.S.C. § 102(b); see Golan v. Holder, 132 S. Ct. 873, 890 (2012) (“The idea/expression dichotomy is codified at 17 U.S.C. § 102(b).”).


The idea/expression dichotomy traces back to the Supreme Court’s decision in Baker v. Selden, 101 U.S. 99, 101 (1879). In Baker, the plaintiff Selden wrote and obtained copyrights on a series of books setting out a new system of bookkeeping. Id. at 100. The books included an introductory essay explaining the system and blank forms with ruled lines and headings designed for use with that system. Id. Baker published account books employing a system with similar forms, and Selden filed suit alleging copyright infringement. According to Selden, the “ruled lines and headings, given to illustrate the system, are a part of the book” and “no one can make or use similar ruled lines and headings, or ruled lines and headings made and arranged on substantially the same system, without violating the copyright.” Id. at 101.


The Supreme Court framed the issue on appeal in Baker as “whether the exclusive property in a system of book-keeping can be claimed, under the law of copyright, by means of a book in which that system is explained.” Id. In reversing the circuit court’s decision, the Court concluded that the “copyright of a book on book-keeping cannot secure the exclusive right to make, sell, and use account-books prepared upon the plan set forth in such book.” Id. at 104. Likewise, the “copyright of a work on mathematical science cannot give to the author an exclusive right to the methods of operation which he propounds.” Id. at 103. The Court found that, although the copyright protects the way Selden “explained and described a peculiar system of book-keeping,” it does not prevent others from using the system described therein. Id. at 104. The Court further indicated that, if it is necessary to use the forms Selden included in his books to make use of the accounting system, that use would not amount to copyright infringement. See id. (noting that the public has the right to use the account-books and that, “in using the art, the ruled lines and headings of accounts must necessarily be used as incident to it”).


Courts routinely cite Baker as the source of several principles incorporated into Section 102(b) that relate to this appeal, including that: (1) copyright protection extends only to expression, not to ideas, systems, or processes; and (2) “those elements of a computer program that are necessarily incidental to its function are . . . unprotectable.” See Computer Assocs. Int’l v. Altai, 982 F.2d 693, 704-05 (2d Cir. 1992) (“Altai”) (discussing Baker, 101 U.S. at 103-04).


It is well established that copyright protection can extend to both literal and non-literal elements of a computer program. See Altai, 982 F.2d at 702. The literal elements of a computer program are the source code and object code. See Johnson Controls, Inc. v. Phoenix Control Sys., Inc., 886 F.2d 1173, 1175 (9th Cir. 1989). Courts have defined source code as “the spelled-out program commands that humans can read.” Lexmark Int’l, Inc. v. Static Control Components, Inc., 387 F.3d 522, 533 (6th Cir. 2004). Object code refers to “the binary language comprised of zeros and ones through which the computer directly receives its instructions.” Altai, 982 F.2d at 698. Both source and object code “are consistently held protected by a copyright on the program.” Johnson Controls, 886 F.2d at 1175; see also Altai, 982 F.2d at 702 (“It is now well settled that the literal elements of computer programs, i.e., their source and object codes, are the subject of copyright protection.”). Google nowhere disputes that premise. See, e.g., Oral Argument at 57:38.


The non-literal components of a computer program include, among other things, the program’s sequence, structure, and organization, as well as the program’s user interface. Johnson Controls, 886 F.2d at 1175. As discussed below, whether the non-literal elements of a program “are protected depends on whether, on the particular facts of each case, the component in question qualifies as an expression of an idea, or an idea itself.” Id.


In this case, Oracle claims copyright protection with respect to both: (1) literal elements of its API packages— the 7,000 lines of declaring source code; and (2) non-literal elements—the structure, sequence, and organization of each of the 37 Java API packages.


The distinction between literal and non-literal aspects of a computer program is separate from the distinction between literal and non-literal copying. See Altai, 982 F.2d at 701-02. “Literal” copying is verbatim copying of original expression. “Non-literal” copying is “paraphrased or loosely paraphrased rather than word for word.” Lotus Dev. Corp. v. Borland Int’l, 49 F.3d 807, 814 (1st Cir. 1995). Here, Google concedes that it copied the declaring code verbatim. Oracle explains that the lines of declaring code “embody the structure of each [API] package, just as the chapter titles and topic sentences represent the structure of a novel.” Appellant Br. 45. As Oracle explains, when Google copied the declaring code in these packages “it also copied the ‘sequence and organization’ of the packages (i.e., the three-dimensional structure with all the chutes and ladders)” employed by Sun/Oracle in the packages. Appellant Br. 27. Oracle also argues that the nonliteral elements of the API packages—the structure, sequence, and organization that led naturally to the implementing code Google created—are entitled to protection. Oracle does not assert “literal” copying of the entire SSO, but, rather, that Google literally copied the declaring code and then paraphrased the remainder of the SSO by writing its own implementing code. It therefore asserts non-literal copying with respect to the entirety of the SSO.


At this stage, it is undisputed that the declaring code and the structure and organization of the Java API packages are original. The testimony at trial revealed that designing the Java API packages was a creative process and that the Sun/Oracle developers had a vast range of options for the structure and organization. In its copyrightability decision, the district court specifically found that the API packages are both creative and original, and Google concedes on appeal that the originality requirements are met. See Copyrightability Decision, 872 F. Supp. 2d at 976 (“The overall name tree, of course, has creative elements . . . .”); Id. at 999 (“Yes, it is creative. Yes, it is original.”); Appellee Br. 5 (“Google does not dispute” the district court’s finding that “the Java API clears the low originality threshold.”). The court found, however, that neither the declaring code nor the SSO was entitled to copyright protection under the Copyright Act.


Although the parties agree that Oracle’s API packages meet the originality requirement under Section 102(a), they disagree as to the proper interpretation and application of Section 102(b). For its part, Google suggests that there is a two-step copyrightability analysis, wherein Section 102(a) grants copyright protection to original works, while Section 102(b) takes it away if the work has a functional component. To the contrary, however, Congress emphasized that Section 102(b) “in no way enlarges or contracts the scope of copyright protection” and that its “purpose is to restate . . . that the basic dichotomy between expression and idea remains unchanged.” Feist, 499 U.S. at 356 (quoting H.R. Rep. No. 1476, 94th Cong., 2d Sess. 54, reprinted in 1976 U.S.C.C.A.N. 5659, 5670). “Section 102(b) does not extinguish the protection accorded a particular expression of an idea merely because that expression is embodied in a method of operation.” Mitel, Inc. v. Iqtel, Inc., 124 F.3d 1366, 1372 (10th Cir. 1997). Section 102(a) and 102(b) are to be considered collectively so that certain expressions are subject to greater scrutiny. Id. In assessing copyrightability, the district court is required to ferret out apparent expressive aspects of a work and then separate protectable expression from “unprotectable ideas, facts, processes, and methods of operation.” See Atari, 975 F.2d at 839.


Of course, as with many things, in defining this task, the devil is in the details. Circuit courts have struggled with, and disagree over, the tests to be employed when attempting to draw the line between what is protectable expression and what is not. Compare Whelan Assocs., Inc. v. Jaslow Dental Lab., Inc., 797 F.2d 1222, 1236 (3d Cir. 1986) (everything not necessary to the purpose or function of a work is expression), with Lotus, 49 F.3d at 815 (methods of operation are means by which a user operates something and any words used to effectuate that operation are unprotected expression). When assessing whether the non-literal elements of a computer program constitute protectable expression, the Ninth Circuit has endorsed an “abstraction-filtration-comparison” test formulated by the Second Circuit and expressly adopted by several other circuits. Sega Enters. Ltd. v. Accolade, Inc., 977 F.2d 1510, 1525 (9th Cir. 1992) (“In our view, in light of the essentially utilitarian nature of computer programs, the Second Circuit’s approach is an appropriate one.”). This test rejects the notion that anything that performs a function is necessarily uncopyrightable. See Mitel, 124 F.3d at 1372 (rejecting the Lotus court’s formulation, and concluding that, “although an element of a work may be characterized as a method of operation, that element may nevertheless contain expression that is eligible for copyright protection.”). And it also rejects as flawed the Whelan assumption that, once any separable idea can be identified in a computer program everything else must be protectable expression, on grounds that more than one idea may be embodied in any particular program. Altai, 982 F.2d at 705-06.


Thus, this test eschews bright line approaches and requires a more nuanced assessment of the particular program at issue in order to determine what expression is protectable and infringed. As the Second Circuit explains, this test has three steps. In the abstraction step, the court “first break[s] down the allegedly infringed program into its constituent structural parts.” Id. at 706. In the filtration step, the court “sift[s] out all non-protectable material,” including ideas and “expression that is necessarily incidental to those ideas.” Id. In the final step, the court compares the remaining creative expression with the allegedly infringing program.[4]


In the second step, the court is first to assess whether the expression is original to the programmer or author. Atari, 975 F.2d at 839. The court must then determine whether the particular inclusion of any level of abstraction is dictated by considerations of efficiency, required by factors already external to the program itself, or taken from the public domain—all of which would render the expression unprotectable. Id. These conclusions are to be informed by traditional copyright principles of originality, merger, and scenes a faire. See Mitel, 124 F.3d at 1372 (“Although this core of expression is eligible for copyright protection, it is subject to the rigors of filtration analysis which excludes from protection expression that is in the public domain, otherwise unoriginal, or subject to the doctrines of merger and scenes a faire.”).


In all circuits, it is clear that the first step is part of the copyrightability analysis and that the third is an infringement question. It is at the second step of this analysis where the circuits are in less accord. Some treat all aspects of this second step as part of the copyrightability analysis, while others divide questions of originality from the other inquiries, treating the former as a question of copyrightability and the latter as part of the infringement inquiry. Compare Lexmark, 387 F.3d at 537-38 (finding that the district court erred in assessing principles of merger and scenes a faire in the infringement analysis, rather than as a component of copyrightability), with Kregos, 937 F.2d at 705 (noting that the Second Circuit has considered the merger doctrine “in determining whether actionable infringement has occurred, rather than whether a copyright is valid”); see also Lexmark, 387 F.3d at 557 (Feikens, J., dissenting-in-part) (noting the circuit split and concluding that, where a court is assessing merger of an expression with a method of operation, “I would find the merger doctrine can operate only as a defense to infringement in that context, and as such has no bearing on the question of copyrightability.”). We need not assess the wisdom of these respective views because there is no doubt on which side of this circuit split the Ninth Circuit falls.


lity are considered questions of copyrightability, concepts of merger and scenes a faire are affirmative defenses to claims of infringement. Ets-Hokin, 225 F.3d at 1082; Satava v. Lowry, 323 F.3d 805, 810 n.3 (9th Cir. 2003) (“The Ninth Circuit treats scenes a faire as a defense to infringement rather than as a barrier to copyrightability.”). The Ninth Circuit has acknowledged that “there is some disagreement among courts as to whether these two doctrines figure into the issue of copyrightability or are more properly defenses to infringement.” EtsHokin, 225 F.3d at 1082 (citations omitted). It, nonetheless, has made clear that, in that circuit, these concepts are to be treated as defenses to infringement. Id. (citing Kregos, 937 F.2d at 705 (holding that the merger doctrine relates to infringement, not copyrightability); Reed-Union Corp. v. Turtle Wax, Inc., 77 F.3d 909, 914 (7th Cir. 1996) (explaining why the doctrine of scenes a faire is separate from the validity of a copyright)).


With these principles in mind, we turn to the trial court’s analysis and judgment and to Oracle’s objections thereto. While the trial court mentioned the abstractionfiltration-comparison test when describing the development of relevant law, it did not purport to actually apply that test. Instead, it moved directly to application of familiar principles of copyright law when assessing the copyrightability of the declaring code and interpreted Section 102(b) to preclude copyrightability for any functional element “essential for interoperability” “regardless of its form.” Copyrightability Decision, 872 F. Supp. 2d at 997.


Oracle asserts that all of the trial court’s conclusions regarding copyrightability are erroneous. Oracle argues that its Java API packages are entitled to protection under the Copyright Act because they are expressive and could have been written and organized in any number of ways to achieve the same functions. Specifically, Oracle argues that the district court erred when it: (1) concluded that each line of declaring code is uncopyrightable because the idea and expression have merged; (2) found the declaring code uncopyrightable because it employs short phrases; (3) found all aspects of the SSO devoid of protection as a “method of operation” under 17 U.S.C. § 102(b); and (4) invoked Google’s “interoperability” concerns in the copyrightability analysis. For the reasons explained below, we agree with Oracle on each point.




[4] Importantly, this full analysis only applies where a copyright owner alleges infringement of the non-literal aspects of its work. Where “admitted literal copying of a discrete, easily-conceptualized portion of a work” is at issue—as with Oracle’s declaring code—a court “need not perform a complete abstraction-filtration-comparison analysis” and may focus the protectability analysis on the filtration stage, with attendant reference to standard copyright principles. Mitel, 124 F.3d at 1372-73.



Continue Reading Here.


About HackerNoon Legal PDF Series: We bring you the most important technical and insightful public domain court case filings.


This court case 10-CV-3561 retrieved on September 22, 2023, from law.justia.com is part of the public domain. The court-created documents are works of the federal government, and under copyright law, are automatically placed in the public domain and may be shared without legal restriction.