What exactly are the &quot;Java APIs&quot; that were under debate in Oracle America, Inc. v. Google, Inc.?
<p>In <em><a href="https://en.wikipedia.org/wiki/Oracle_America,_Inc._v._Google,_Inc." rel="nofollow">Oracle America, Inc. v. Google, Inc.</a></em>, the debate was over Google's use of 37 "Java APIs" in Android, and whether or not it was fair use. However, I've never found a clear description of the nature of those Java APIs. Are they method signatures? Compiled classes? Something else? And how was the number 37 arrived at?</p>

<p><a href="http://www.cafc.uscourts.gov/sites/default/files/opinions-orders/13-1021.Opinion.5-7-2014.1.PDF" rel="nofollow">Oracle v Google, CAFC (2014)</a>, at footnote 2:</p>

<blockquote>
  <p>The 37 API packages involved in this appeal are:
  java.awt.font, java.beans, java.io, java.lang, java.lang.annotation, java.lang.ref, java.lang.reflect, java.net,
  java.nio, java.nio.channels, java.nio.channels.spi,
  java.nio.charset, java.nio.charset.spi, java.security, java.security.acl,
  java.security.cert, java.security.interfaces,
  java.security.spec, java.sql, java.text, java.util, java.util.jar,
  java.util.logging, java.util.prefs, java.util.regex,
  java.util.zip, javax.crypto,
  javax.crypto.interfaces, javax.crypto.spec, javax.net,
  javax.net.ssl, javax.security.auth, javax.security.auth.callback,
  javax.security.auth.login,
  javax.security.auth.x500, javax.security.cert, and javax.sql.</p>
</blockquote>

<p>The "declaring code and the structure, sequence, and organization of the API packages" is what Google took and what the CAFC held was entitled to copyright protection. This was composed of "over six hundred classes, with over six thousand methods". Both sides acknowledged that "Google wrote its own implementing code".</p>

copyright software