copyrightability – UA LAW IP

The following post comes from Liz Velander, a recent graduate of Scalia Law and a Research Assistant at CPIP.

By Liz Velander

The Supreme Court finally reached a determination in the decade-long dispute between two of the biggest technology companies in the world, Google and Oracle. Many have long-awaited the Court’s decision in this case, as it had the potential to provide market certainty in the software industry through its copyrightability analysis. The Court ultimately declines to give that certainty by bypassing the copyrightability issue and choosing to base its holding on a fact-intensive fair use analysis. The Court does this so as to “not answer more than is necessary to resolve the parties’ dispute,” “given the rapidly changing technological, economic, and business-related circumstances.” It emphasizes that its holding is narrow, only applies to declaring code, and does not modify its prior cases on fair use. However, by framing its opinion this way, the Court provides new arguments for infringers to use in a fair use defense in the software sphere and beyond. For this reason, the Court’s decision is not as narrow as it sets out to be. It may lead to lower court decisions that broaden the fair use doctrine and limit the copyright protection given to software.

The Court’s decision broadens fair use by using the doctrine to loosen copyright protection for certain types of code, allowing for a more expansive reading of a “transformative use,” and giving great weight to the public benefit of the use. Before it engages in its fair use analysis, the Court states that “fair use can play an important role in determining the lawful scope of a computer program copyright, such as the copyright at issue here.” Fair use “can distinguish between expressive and functional features of computer code where those features are mixed.” It can also “focus on the legitimate need to provide incentives to produce copyrighted material while examining the extent to which yet further protection creates unrelated or illegitimate harms in other markets or to the development of other products.” The Court describes fair use as a “context-based check that can help to keep a copyright monopoly within its lawful bounds.”

To highlight the ability of fair use to accomplish these goals, the Court begins its analysis with the second statutory factor, “the nature of the copyrighted work.” The Court uses this factor to discuss issues that would have come up if it analyzed the copyrightability of Oracle’s material, such as the applicability of the merger doctrine. It then moves to “the purpose and character of the use,” where it adopts an expansive reading of what constitutes a “transformative use.” The biggest impact of the Court’s fair use analysis, however, will likely come from the great weight it gives to the public benefit of the use under the market effect factor. By using fair use to determine “the lawful scope of a computer program copyright,” the Court’s holding may inadvertently broaden the fair use doctrine.

The Nature of the Copyrighted Work

The Court begins its analysis with describing “the nature of the copyrighted work.” The copyright at issue protects a portion of Oracle’s Java SE platform, called declaring code. Java SE has three essential parts: (1) implementing code, (2) method calls, and (3) declaring code. Implementing code tells the computer how to execute the particular task the programmer asks it to perform. Method calls are commands that help the computer carry out the task by choosing the correct programs written in implementing code. The declaring code is how the method call actually locates and invokes the particular implementing code that it needs to instruct the computer how to carry out a particular task.

For each task, the specific method call entered by the programmer matches up with a specific declaring code inside Java SE. That declaring code provides both the name for each task and organizes them within Java SE’s library. In this sense, the declaring code and the method call form a link, allowing the programmer to draw upon the thousands of prewritten tasks, written in implementing code. Without that declaring code, the method calls entered by the programmer would not call up the implementing code.

In this case, Google did not copy the implementing code from Oracle’s Java SE platform; it copied the declaring code. The Court draws a “critical line” between the uncopied implementing code and the copied declaring code under this factor. On one hand is the innovative implementing code and on the other, user-centered declaring code. The Court explains that the writing of implementing code requires balancing considerations as to how quickly a computer can execute a task or the likely size of a computer memory. The Court says that this balancing is “the very creativity that was needed to develop the Android software for use not in laptops or desktops but in the very different context of smartphones.”

Declaring code, the Court says, embodies a different kind of “creativity” because it is user facing. It must be designed and organized in a way that is intuitive and understandable to developers so they can invoke it. As part of a user interface, declaring code differs from most computer code because “its use is inherently bound together with uncopyrightable ideas (general task division and organization) and new creative expression (Android’s implementing code).” For these reasons, the Court concludes that “the declaring code is, if copyrightable at all, further than are most computer programs (such as the implementing code) from the core of copyright.” Therefore, the Court finds that the second factor, “nature of the copyrighted work,” points in the direction of fair use.

The Purpose and Character of the Use

The Court explains that the inquiry into “the purpose and character” of the use turns in a large measure on whether the copying at issue was “transformative,” that is, whether it “adds something new, with a further purpose or different character.” The Court finds that, even though Google copied Oracle’s declaring code verbatim, its use was “transformative” because it furthered the development of software programs.

The Court explains that what Google did is known as “‘reimplementation,’ defined as the ‘building of a system . . . that repurposes the same words and syntaxes’ of an existing system.” Google “reimplemented” Oracle’s declaring code to allow programmers expert in the Java programming language to use the “task calling” system that they had already learned. By using the same declaring code, programmers using the Android platform can rely on the method calls that they are already familiar with to call up particular tasks. Then Google’s own implementing code carries out those tasks.

The Court concludes that Google’s copying was a transformative use. “Google’s purpose was to create a different task-related system for a different computing environment (smartphones) and to create a platform—the Android platform—that would help achieve and popularize that objective.” Such use is “consistent with the creative ‘progress’ that is the basic constitutional objective of copyright itself.” Therefore, the purpose and character of Google’s copying was transformative to the point at which this factor also weighs in favor of fair use.

The Amount and Substantiality of the Portion Used

The Court says that the question here is whether the over 11,000 lines of code Google copied should be viewed in isolation or as one part of a considerably greater whole. On one hand, those lines of code amount to virtually all the declaring code needed to call up hundreds of different tasks. On the other hand, if one considers the entire set of software material in the Java SE platform, the quantitative amount copied was small (only 0.4 percent).

The Court decides to view Google’s copying as one part of a greater whole because the amount of copying was “tethered to a valid, and transformative, purpose.” It explains that Google did not copy the lines because of their creativity but because programmers had already learned to work with the Java SE platform, and it would have been difficult to attract programmers to build its Android smartphone system without them. It describes the portion of the declaring code used at “the key that [Google] needed to unlock the programmers’ creative energies. And it needed those energies to create and improve its own innovative Android systems.” For these reasons, the Court holds that this factor weighs in favor of fair use.

Market Effects

The fourth statutory factor focuses upon the “effect” of the copying in the “market for or value of the copyrighted work.” The Court explains that this requires a court to consider the copyright owner’s potential loss of revenue, the source of the loss, and the public benefits the copying will likely produce. As to the likely amount of loss, the Court states that Oracle was ill-positioned to enter the smartphone market, so the jury could have found that Android did not harm the actual or potential markets for Java SE. As to the source of the loss, the Court finds Android’s profitability has much to do with third parties’ (programmers’) investment in the Java programs and less to do with Oracle’s investment in creating the Java SE platform. It says that the Copyright Act does not protect third parties’ investment in learning how to operate a created work.

Finally, given programmers’ investments in learning the Java SE platform, to allow enforcement of Oracle’s copyright here would risk harm to the public by operating as a lock on innovation. “The result could well prove highly profitable to Oracle (or other firms holding a copyright in computer interfaces). But those profits could well flow from creative improvements, new applications, and new uses developed by users who have learned to work with that interface. To that extent, the lock would interfere with, not further, copyright’s basic creativity objectives.” The Court concludes that the uncertain nature of Oracle’s “ability to compete in Android’s market place, the sources of its lost revenue, and the risk of creativity-related harms to the public, when taken together, convince that this fourth factor—market effects—also weighs in favor of fair use.”

The Court ends its opinion by noting that “the fact that computer programs are primarily functional makes it difficult to apply traditional copyright concepts in that technical world.” While that is certainly true, the Court made its work more difficult by basing its opinion in fair use instead of analyzing the copyrightability of Oracle’s code in the first place.

The following post comes from Chris Wolfsen, a recent graduate of Scalia Law and a Research Assistant at CPIP.

U.S. Supreme Court building By Chris Wolfsen

Grocery store shelves, QWERTY keyboards, and restaurant menus. These are just three of the analogies that Supreme Court justices used to grapple with the complex issues in the long-awaited Google v. Oracle oral argument that was heard last Wednesday, October 7. The case between the two tech companies that has been brewing for over a decade comes down to 11,000 lines of Oracle’s Java code that Google copied, without permission, for use in its well-known Android smartphone platform—a competing product.

Oracle originally filed suit in 2010 against Google in the U.S. District Court for the Northern District of California for both patent and copyright infringement. In 2014, the Federal Circuit ruled that Oracle’s code was copyrightable, and Google appealed to the Supreme Court, only to be denied review. On remand, again in the district court, Google claimed that its use of the Oracle code was fair use—meaning that even if it were an infringing use it should still be allowed by law. In 2016, a jury sided with Google, and Oracle filed a motion to challenge the jury verdict, which was denied. So instead, Oracle appealed the case back up to the Federal Circuit where the court reversed the lower court’s judgment and held that Google’s copying of the code was not fair use and that the copyrightability issue that was resolved in its 2014 decision still applied. In 2019, Google filed its petition for Supreme Court review once again, and finally the time for oral argument arrived.

The main issues for the Court to decide are a review of the Federal Circuit decisions—whether Oracle’s code was copyrightable to begin with and whether Google made fair use of the code. But also, and perhaps most importantly, the Court must decide what standard of review should be used to make a fair use determination. This last question will have a lasting impact far beyond this particular dispute.

Copyrightability

Under the Section 102 of the Copyright Act, software is considered a “literary work” and is afforded legal protection. Oracle would therefore have the right to prevent others from using its code or, as was the case, license the use of its software for others to use. But Google makes an argument under the merger doctrine that the code was never subject to copyright protection. The merger doctrine states that when an idea and its expression are inextricably merged there cannot be any copyright protection for the idea. This doctrine gets right to the heart of copyright law: original expression is protectable; an idea—a method, a system, a way to explain something—is not. Google’s argument is that there is only one way to express Oracle’s code, and therefore the code itself cannot be copyrightable at all. Google repeatedly suggests that to rule otherwise would be imparting protection over a method, which is something reserved for patent law.

The Court, and perhaps the rest of us not well-versed in computer science, struggled with this concept in the context of a very technical set of facts. Google’s counsel, Thomas Goldstein, drew comparisons to the Baker v. Selden Supreme Court case where Selden created a new method of bookkeeping and attempted to assert copyright protection over his ledger forms. Goldstein likened Oracle’s code to those ledgers—innovative and hugely successful, but merely a methodology that does not warrant copyright protection. The justices took turns proposing different hypotheticals to challenge this argument. First was Chief Justice Roberts, “cracking the safe may be the only way to get the money that you want, but that doesn’t mean you can do it,” followed by Justice Thomas’s analogy to a football team’s playbook that Google swiped for its own win. Mr. Goldstein argued back that copyrighting the knowledge itself of how to crack a safe would not be allowed and that Google is not “trying to take someone’s fan base or their football players or anything else.” The justices did not seem convinced by Google’s assertion that Oracle’s method of writing code was the only way to create the function Google wanted for its Android platform.

It is easy to get lost in the technical language of the case, between declaring code and implementing code and shortcut programs. Oracle’s counsel, Joshua Rosenkranz, cut through all those distinctions saying, “code is code,” and he pointed out that no circuit court drew a distinction between the types of code. Congress could have carved out different types of code in its consideration of the Copyright Act, but it expressly chose otherwise. Mr. Rosenkranz also circled back to distinguish Oracle’s code from the accounting ledgers in the Baker v. Selden case, highlighting that Oracle is not trying to prevent others from creating their own programs. “Others are free to write and organize their own prewritten programs however they see fit, as long as they don’t copy ours.” Mr. Rosenkranz underscored, and multiple justices acknowledged, that other competitors like Apple and Microsoft did not resort to pure copying to create their products, and that companies like IBM and SAP paid Oracle to properly license the code. Just because Oracle’s method was the most elegant, and therefore popular, way of expressing the code does not make it the only method of doing so. Mr. Rosenkranz summarized this issue well, saying, “the Copyright Act does not give Google a pass just because it would be expensive to recreate our expression.”

Fair Use

Even if the code were copyrightable in the first place, Google argues, fair use still justifies its copying of the code. Fair use is an affirmative defense to an accusation of copyright infringement. A person or entity who has plainly copied another’s protected work can argue fair use to justify their taking and subsequent use of the copyrighted material. Congress has enumerated a four-factor test within the Copyright Act for courts to follow when evaluating a fair use claim—a test that the Supreme Court last used 26 years ago in Campbell v. Acuff-Rose Music—weighing the purpose and character of the use, the nature of the original work, the amount and substantiality of the portion used, and the effect of the use on the market value of the original work.

Modern courts, when evaluating the first factor of purpose and character of the infringing use, often focus on whether the use was transformative. Google has used this argument successfully in the past, in Authors Guild v. Google, defending its copying of millions of books for use in its Google Books search engine. The court in that case found that digitizing books for use in an online search database was highly transformative. In this case, Mr. Goldstein tried to make a similar argument that Google wrote an improved version of Oracle’s Java code to be more suitable for use in a smartphone. Mr. Goldstein said that this is “what Congress would want, that is to be able to take the functionality of a computer program, [and] someone else comes along and does it better.” He then stated that computer code only performs one function and therefore can still be considered transformative even if it does nothing different than the original work, only to later argue that the word “transformative” is not used in the Copyright Act and might not even be the correct standard of evaluation in this case.

Google also maintained a policy argument that “reusing software interfaces is critical to modern interoperable computer software,” and that to rule in Oracle’s favor would “upend that world” and make computer programming so inefficient as to have fewer creative computer programs. Justice Kavanaugh pointed out that despite Google and its amici claiming a dire result if the Court should rule for Oracle, in the years since the Supreme Court first denied certiorari, “I’m not aware that the sky has fallen.”

Oracle made a more direct argument based on legal precedent, noting that the Supreme Court had already held in Harper & Row and in Stewart v. Abend that no court had found or upheld a fair use verdict where an infringer copied so much of an original work for use in a competing commercial product, all while retaining the same meaning and purpose as the original work. Mr. Rosenkranz pointed out that Google conceded that every line of code copied serves the same purpose in Google’s Android platform as it did in the original software—there was no alteration or transformation of the original code—and Malcolm Stewart, arguing on behalf of the United States in support of Oracle, echoed that point. Mr. Rosenkranz then cited the Court’s own decision in Campbell, saying that what Google did is the “epitome of commercial superseding use: using a work ‘to get attention or to avoid the drudgery in working up something fresh.’”

Standard of Review

The discussion quickly turned to the standard of review that the Court should use to evaluate fair use—whether the determination must be left up to a jury, like the jury that ruled in Google’s favor previously, or whether it can be made by a court, such as the Federal Circuit that overturned the jury verdict to side with Oracle. Google argued that fair use is determined by “whether the jury could reasonably find fair use,” and that “no previous court ever held that only a court may decide fair use.” Mr. Goldstein argued that giving the decision to a jury is the better choice due to the numerous factors involved in a fair use verdict and that jury instructions exist to give appropriate legal certainty and guidance to the jurors.

Oracle disagreed and argued that de novo, meaning “anew,” is the correct standard to resolve this question. This would allow for a court to make a fair use determination without being bound by the decision of a previous court or verdict. Mr. Rosenkranz again cited Harper & Row: “an appellate court may conclude, as a matter of law, that the challenged use does not qualify as fair use once it has the factual record and resolves all subsidiary factual questions in favor of the fact-finder.” Judicial review provides certainty to a fair use determination that would be lost if left to a lay jury. Mr. Rosenkranz also noted that making fair use a fact-finding mission that only a jury may evaluate would all but preclude summary judgment determinations, which are exclusively judge-made decisions and currently comprise the vast majority of fair use cases.

Conclusion

The stakes in this case are extremely high—if it was not made clear by the number of times the justices and attorneys referenced the sky falling—not only for Oracle and Google and the computer science world at large, but also for any copyright creator or user who will eventually face a fair use determination. Joshua Simmons, co-counsel for Oracle and partner at Kirkland & Ellis, looks forward to the Court’s decision, writing:

Given that Google’s copyrightability argument would make it difficult for any code to be protectable, I am hopeful that the Court will follow the text of the Copyright Act and the intent of Congress that code, like Oracle’s, is protectable. Likewise, I hope that the Court will follow a century of precedent allowing courts to decide as a matter of law that, when the defendant creates a substitute that competes with the original, it simply is not fair use.

People of all industries, from professionals to hobbyists, should take note of last week’s oral argument and what will be an historic decision from the Court.

Recent Posts

Recent Comments

Archives

Categories