Oracle America, Inc. v. Google Inc.

Filing 898

Statement re #877 Order Google's Proposed Findings of Fact Regarding the Copyrightability of the Structure, Selection and Organization of the 37 APIs by Google Inc.. (Van Nest, Robert) (Filed on 4/12/2012)

1
2
3
4
5
6
7
8
9
10
11
12

KEKER & VAN NEST LLP
ROBERT A. VAN NEST - # 84065
[e-mail]
CHRISTA M. ANDERSON - # 184325
[e-mail]
MICHAEL S. KWUN - # 198945
[e-mail]
633 Battery Street
San Francisco, CA 94111-1809
Tel: [phone]
Fax: [phone]

KING & SPALDING LLP
DONALD F. ZIMMER, JR. - #112279
[e-mail]
CHERYL A. SABNIS - #224323
[e-mail]
101 Second Street, Suite 2300
San Francisco, CA 94105
Tel: [phone]
Fax: [phone]

KING & SPALDING LLP
SCOTT T. WEINGAERTNER
(Pro Hac Vice)
[e-mail]
ROBERT F. PERRY
[e-mail]
BRUCE W. BABER (Pro Hac Vice)
1185 Avenue of the Americas
New York, NY 10036
Tel: [phone]
Fax: [phone]

IAN C. BALLON - #141819
[e-mail]
HEATHER MEEKER - #172148
[e-mail]
GREENBERG TRAURIG, LLP
1900 University Avenue
East Palo Alto, CA 94303
Tel: [phone]
Fax: [phone]

13
14

Attorneys for Defendant
GOOGLE INC.

15

UNITED STATES DISTRICT COURT

16

NORTHERN DISTRICT OF CALIFORNIA

17

SAN FRANCISCO DIVISION

18

ORACLE AMERICA, INC.,

19

Plaintiff,

20

v.

21

GOOGLE INC.,

22

Defendant.

Case No. 3:10-cv-03561 WHA
GOOGLE’S PROPOSED FINDINGS OF
FACT REGARDING THE
COPYRIGHTABILITY OF THE
STRUCTURE, SELECTION AND
ORGANIZATION OF THE 37 APIS
Dept.:
Judge:

Courtroom 8, 19th Floor
Hon. William Alsup

23
24
25
26
27
28
GOOGLE’S PROPOSED FINDINGS OF FACT REGARDING COPYRIGHTABILITY
Case No. 3:10-CV-03561 WHA
648583.01

1
2

1.

An API consists of a set of names that can be used to access features of a library,

together with specified conventions about their use.

3

2.

API specifications, by design, describe the structure, selection and organization

4

(“SSO”) of API elements needed for compatibility between implementations of the APIs, and

5

with programs using the APIs.

6

3.

The 37 APIs are fundamental to the Java language.

7

4.

Developers learn the 37 APIs when they learn the Java language.

8

5.

Developers treat the 37 APIs as part of the Java language.

9

6.

The Java language cannot be implemented without many of the 37 APIs.

10

7.

Without the 37 APIs, the Java language cannot perform basic tasks, e.g., receiving

11

input from and providing output to the user, or processing text strings.

12
13

8.

The 37 APIs and their SSO are how developers access the implementing code in

the 37 API packages, and thus the functionality provided by that code.

14

9.

Developers cannot use the 37 APIs without relying on their SSO.

15

10.

The SSO of the 37 APIs are functional requirements for compatibility with the 37

17

11.

The 37 APIs cannot be implemented without their SSO.

18

12.

Code using different APIs with different SSO than the 37 APIs will not be

16

19
20
21
22
23
24
25
26
27

APIs.

compatible with the 37 APIs.
13.

The design of the 37 APIs and their SSO is constrained by external factors

including functionality, efficiency and ease of use.
14.

The 37 APIs and their SSO build on previous programming languages and long-

accepted conventions.
15.

The 37 APIs and their SSO are a system of expression developers use when

programming in the Java language.
16.

For years before this litigation, Sun was aware of, and did not object to, use of the

37 APIs and their SSO in GNU Classpath, Apache Harmony and Android.

28
1
GOOGLE’S PROPOSED FINDINGS OF FACT REGARDING COPYRIGHTABILITY
Case No. 3:10-CV-03561 WHA
648583.01

1
Dated: April 12, 2012

KEKER & VAN NEST LLP

2
3
By:

/s/ Robert A. Van Nest
ROBERT A. VAN NEST

4
Attorneys for Defendant
GOOGLE INC.

5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
2

GOOGLE’S PROPOSED FINDINGS OF FACT REGARDING COPYRIGHTABILITY
Case No. 3:10-CV-03561 WHA
648583.01