Oracle Files Its Opening Brief As It Tries (Again) To Overturn Google's Fair Use Win On Java APIs

Copyright

from the still-ain't-over dept

As was widely expected, back in October, Oracle announced its appeal of Google’s big fair use win, concerning its reuse of certain Java API components in Android. If you’ve been following this (long, long, long) case, you’ll recall that Google has won twice at the district court level. The first time, Judge William Alsup correctly noted that APIs were not subject to copyright, because copyright law clearly states that copyright protection does not apply to “any idea, procedure, process, system, method of operation, concept, principle, or discovery,” and an API is a process, system or method of operation. However, the Court of Appeals for the Federal Circuit (CAFC), who only had jurisdiction over the case because it initially involved a patent issue, seemed unable to understand that an API is different from software and overturned the lower court’s sensible ruling.

That resulted in the second case which was weird, because everyone had to tiptoe around the fact that basically everyone had assumed that APIs were not covered by copyright, in order to instead make a fair use argument, which ultimately succeeded. Oracle then tried to play some games to get that ruling overturned, but that failed miserably, when the judge pointed out that Oracle’s argument was almost entirely based on a failure to read what Google had actually given them (Oracle had claimed that Google failed to disclose something important, when the reality was that Oracle’s lawyers failed to read the material that Google had given them).

Anyway, now that things are back at CAFC, we have to hope and pray that the court doesn’t muck things up any worse than it already has (and, trust me, it’s mucked things up badly to the point that it’s impacting a bunch of other cases). On Friday, Oracle filed its 155-page opening brief. Feel free to dig in, if you must, but the arguments are (mostly) basically what we expected. Oracle argues that Google’s use is not fair use (basically saying the jury got it wrong). It further argues that the case should be sent back to the district court because it was prevented from presenting key evidence that would have undermined the fair use claim. And then, somewhat incredibly, at the end, Oracle continues to try to argue that Google concealed its plans to expand Android into PCs — the very issue that Judge Alsup smacked Oracle down for when it was revealed that Google had shared that info, and Oracle just hadn’t read it. In the filing, Oracle whines that Judge Alsup “blamed the victim” for not having read what Google actually gave them, saying that it was impossible to have read everything Google gave them because there was just too much stuff and this was a “needle in the haystack.” That… seems pretty weak. Amusingly, at the same time that Oracle is complaining that Google gave Oracle too much in discovery, it also complains that Google clearly withheld more info. Throw any argument at the wall and see what sticks, I guess.

Frankly, this opening brief seems to really lean in to CAFC’s notorious ignorance of how software works, and the fact that last time around it couldn’t tell the difference between an API and software. It just keeps focusing on the agreed upon point that Google copied some of Java’s APIs, but keeps calling it “copyrighted code.” It’s impossible to predict how CAFC will rule, because CAFC is frequently hilariously confused when it comes to how technology (and software in particular) actually work. But hopefully someone over there will take the time to figure it out. After all, there have been a few, somewhat shocking signs of enlightenment in the past few months at CAFC. Hopefully that continues.

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