Big Win For Fair Use: Jury Says Google's Use Of Java API's Was Fair Use... On To The Appeal

from the ain't-done-yet dept

This is somewhat surprising, but good: after a few days of deliberation, the jury in the redo of the Oracle v. Google case concerning Google's use of Java's APIs in Android has resulted in a jury verdict finding that Google's use was allowed as fair use. There's not much to unpack here beyond what we've already written about the case. The jury form was a simple question of whether or not the use was covered by fair use, with a "Yes" check box meaning "finding for Google" and a "No" check box finding for Oracle The jury checked yes.

So, a few quick thoughts:
  1. All things considered this is a good ruling in that it doesn't lead to a crazy situation that undermines the reimplementation of APIs and other structures in different software, so *phew*.
  2. This still sucks because fair use was the wrong vehicle. The APIs never should have been considered copyright-eligible in the first place, just as the judge in the original trial explained in his very detailed opinion. It's only because an excessively confused federal circuit appeals court mucked things up, that the case had to go back down and be redone over fair use.
  3. The trial itself was a weird one, because they weren't really allowed to talk about the first trial and how a very large number of people in the tech industry didn't think that APIs were covered by copyright at all. So that resulted in some weird conversations to explain why no one really thought this was infringing. They couldn't say no one thought APIs were covered by copyright, so they had to talk about "open" and "free" in ways that were slightly misleading.
  4. If anything, this may be the most important fair use case to turn on factor 2, "the nature of the copyrighted work." That's a factor that rarely is a very big deal, but without being able to (re)challenge the copyrightability, the focus was mostly on the nature of APIs and how the tech industry viewed them as free to be reused.
  5. Of course, no matter what the verdict was there would be an appeal, and that's absolutely true. Oracle will appeal. But it does make it more difficult to appeal. Oracle will have to challenge specific aspects of things, and will likely focus on the jury instructions, which it will argue unfairly biased the jury or something along those lines.
  6. The Court of Appeals of the Federal Circuit (CAFC) is still a disaster, and while I hope they don't, there's still a decent chance they'll end up siding with Oracle on appeal. Remember, CAFC is a court that normally focuses on patent laws and has a long and disgraceful history of loving to expand intellectual property and believing, incorrectly, that any kind of use is "theft."
  7. But, in the meantime, this at least lifts something of a cloud over the industry, and we can hope that (1) CAFC will get it right and if they don't (2) that the Supreme Court will fix it, rather than ignore it, next time around.
Overall, a good result of a bad process and a confused judicial system. For now.

Filed Under: android, api, cafc, copyright, fair use, java
Companies: google, oracle

Reader Comments

Subscribe: RSS

View by: Time | Thread

  1. identicon
    Anonymous Coward, 28 May 2016 @ 2:52pm


    Um... No.

    Allow me to enlighten you.
    U.S. Code § 102 - Subject matter of copyright

    § 102 (b)
    In no case does copyright protection for an original work of authorship extend to any idea, procedure, process, system, method of operation, concept, principle, or discovery, regardless of the form in which it is described, explained, illustrated, or embodied in such work.

    An API is essentially most of what this describes - an idea, procedure, process, method of operation, concept.

    An API is just a specification. It's basically a framework that describes how to communicate within a given app or another app. Hence the name "Application Programming Interface" The underlying "behind the scenes" stuff WITHIN the API can be copyrighted, but not the API itself. It has no functionality on its own. Google did not copy ANY of the underlying code at all - only the API concept - mostly in the name of interoperability - something that copyright also allows for.

    All was right as rain in the world until Oracle came along and started whining and had CAFC throw into chaos what had been decades long established industry practice (actually.. even before programming was even considered an industry for that matter)

Add Your Comment

Have a Techdirt Account? Sign in now. Want one? Register here

Subscribe to the Techdirt Daily newsletter

Comment Options:

  • Use markdown. Use plain text.
  • Remember name/email/url (set a cookie)

Follow Techdirt
Special Affiliate Offer

Report this ad  |  Hide Techdirt ads
Essential Reading
Techdirt Deals
Report this ad  |  Hide Techdirt ads
Techdirt Insider Chat
Report this ad  |  Hide Techdirt ads
Recent Stories
Report this ad  |  Hide Techdirt ads


Email This

This feature is only available to registered users. Register or sign in to use it.