04.11.2014 Views

cyckV4

cyckV4

cyckV4

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Methods of Operation: Introduction to Computer Software 361<br />

Oracle America, Inc. v. Google, Inc.<br />

750 F.3d 1339 (Fed. Cir. 2014)<br />

O’MALLEY, Circuit Judge.<br />

This copyright dispute involves 37 packages of computer source code. The parties<br />

have often referred to these groups of computer programs, individually or collectively,<br />

as “application programming interfaces,” or API packages, but it is their content, not<br />

their name, that matters. The predecessor of Oracle America, Inc. (“Oracle”) wrote these<br />

and other API packages in the Java programming language, and Oracle licenses them on<br />

various terms for others to use. Many software developers use the Java language, as well<br />

as Oracle’s API packages, to write applications (commonly referred to as “apps”) for<br />

desktop and laptop computers, tablets, smartphones, and other devices.<br />

Oracle filed suit against Google Inc. (“Google”) in the United States District Court<br />

for the Northern District of California, alleging that Google’s Android mobile operating<br />

system infringed Oracle’s patents and copyrights. . . . [T]he district court issued its<br />

decision on copyrightability, finding that the replicated elements of the 37 API<br />

packages—including the declaring code and the structure, sequence, and organization—<br />

were not subject to copyright protection. . . . Oracle asserts that all of the trial court’s<br />

conclusions regarding copyrightability are erroneous. Oracle argues that its Java API<br />

packages are entitled to protection under the Copyright Act because they are expressive<br />

and could have been written and organized in any number of ways to achieve the same<br />

functions. Specifically, Oracle argues that the district court erred when it: (1) concluded<br />

that each line of declaring code is uncopyrightable because the idea and expression have<br />

merged; (2) found the declaring code uncopyrightable because it employs short phrases;<br />

(3) found all aspects of the SSO devoid of protection as a “method of operation” under<br />

17 U.S.C. § 102(b); and (4) invoked Google’s “interoperability” concerns in the<br />

copyrightability analysis. For the reasons explained below, we agree with Oracle on each<br />

point. Because we conclude that the declaring code and the structure, sequence, and<br />

organization of the API packages are entitled to copyright protection, we reverse the<br />

district court’s copyrightability determination. . . .<br />

The district court found that the structure, sequence, and organization [“SSO”] of<br />

the Java API packages is creative and original, but nevertheless held that it is a “system<br />

or method of operation . . . and, therefore, cannot be copyrighted” under 17 U.S.C.<br />

§ 102(b). In reaching this conclusion, the district court seems to have relied upon<br />

language contained in a First Circuit decision: Lotus Development Corp. v. Borland<br />

International, Inc. . . .<br />

[T]he Ninth Circuit has not adopted the court’s “method of operation” reasoning<br />

in Lotus, and we conclude that it is inconsistent with binding precedent. Specifically, we<br />

find that Lotus is inconsistent with Ninth Circuit case law recognizing that the structure,<br />

sequence, and organization of a computer program is eligible for copyright protection<br />

where it qualifies as an expression of an idea, rather than the idea itself. And, while the<br />

court in Lotus held “that expression that is part of a `method of operation’ cannot be<br />

copyrighted,” this court—applying Ninth Circuit law—reached the exact opposite<br />

conclusion, finding that copyright protects “the expression of [a] process or method.”<br />

Atari Games Corp. v. Nintendo of Am., Inc., 975 F.2d 832, 839 (Fed. Cir. 1992).<br />

We find, moreover, that the hard and fast rule set down in Lotus and employed by<br />

the district court here— i.e., that elements which perform a function can never be<br />

copyrightable—is at odds with the Ninth Circuit’s endorsement of the abstraction-

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!