Oracle America, Inc. v. Google Inc.
872 F. Supp. 2d 974
N.D. Cal.2012Background
- This action began after Google launched Android in 2007 and Oracle acquired Sun; Oracle sued Google alleging Java API copyright infringement.
- The dispute centers on 37 Java API packages and whether their structure, sequence, and organization are protectable by copyright.
- The trial proceeded in phases; phase one addressed copyrightability and equitable defenses, phase two covered patent issues, and damages were not pursued.
- Google admitted to not literally copying code but created its own implementations for the 37 API packages while allegedly replicating their structure, names, and organization.
- The jury found infringement for the compilable code but deadlocked on fair use; nine lines of “range-Check” code were involved in a separate conceded copy.
- This order resolves whether the replicated elements themselves are copyrightable and concludes the copied structure is not copyrightable under relevant law.
Issues
| Issue | Plaintiff's Argument | Defendant's Argument | Held |
|---|---|---|---|
| Whether the 37 Java API package structure is copyrightable | Oracle argues the structure/organization is protectable. | Google argues only expressions (declarations) are protected, not the system of operation. | Not copyrightable; the structure/organization constitutes a system of operation not protected by copyright. |
| Whether method and class declarations and names are protectable | Oracle contends declarations may be copyrighted as expressive elements. | Declarations and names are dictated by the language and not protectable; merger applies. | Declarations and names are not protectable; only implementing code may be; method implementations may be freely re-implemented. |
| Whether interoperability and 102(b) functional elements bar copyright | Oracle highlights structure as non-functional protection to shield Java APIs. | Functional aspects essential for interoperability are not copyrightable under 102(b). | Yes; functional elements required for interoperability are not copyrightable; 102(b) supports non-protection of such interfaces. |
| Role of merger and taxonomy arguments in copyrightability | Oracle uses taxonomy-like organization as protectable expression. | Merger doctrine bars protection when only one way to express a function exists; taxonomy is a system of operation. | Merger and taxonomy considerations preclude copyright protection for the command structure as a system of operation. |
Key Cases Cited
- Whelan Associates, Inc. v. Jaslow Dental Laboratory, Inc., 797 F.2d 1222 (3d Cir. 1986) (structure of a program may be copyrightable if multiple ways exist to perform the same function)
- Computer Associates International, Inc. v. Altai, Inc., 982 F.2d 693 (2d Cir. 1992) (abstract-filtration-comparison test for non-literal copying; filter out unprotectable elements)
- Sega Enterprises Ltd. v. Accolade, Inc., 977 F.2d 1510 (9th Cir. 1992) (interface procedures for compatibility not copyrightable under 102(b))
- Lotus Development Corp. v. Borland International, Inc., 49 F.3d 807 (1st Cir. 1995) (menu command hierarchy treated as a method of operation not protectable by copyright)
- Johnson Controls, Inc. v. Phoenix Control Sys., Inc., 886 F.2d 1173 (9th Cir. 1989) (structure/sequence may be protectable as expression depending on case facts)
- Atari Games Corp. v. Nintendo of America Inc., 975 F.2d 832 (Fed. Cir. 1992) (protectable expression in a program's data stream beyond the functional lock)