I’m actually not that upset. The decision may or may not stand, so nobody on either side should either overcelebrate or rend their garments in anguish. And even if APIs are copyrightable, maybe that’s not so terrible. But I think the OSS community just picked up a new to-do item.
[Disclosure: While working at Google, I worked with the attorneys on certain aspects of this case, and was deposed by Oracle. I am not the slightest bit neutral in this dispute.]
Might not stand? · I read most of the Federal Circuit Appeals Court judgment and boy, the law around this is clear as mud. While some of the judges’ language made think “are they crazy?” other arguments sounded sort of plausible.
On the other hand, this does fly in the face of the industry’s perception of the body of precedent, and I’ve read several sources asserting that this court has historically been controversial in its findings, something of an outlier. Anyhow, there are lots more miles of legal road ahead, and for now it’s safe to ignore predictions about how it plays out in the end.
The right thing to do is to pass legislation making it clear that API specifications aren’t copyrightable; but those wheels turn slow.
Might not be that bad? · Suppose it becomes settled precedent law that API specifications are copyrightable. That’s going to suck for the Java world, because Oracle will obviously look for ways to extract rent from this new-found territory. But Java is past its best-before date anyhow, for interesting new applications.
But beyond that? Well, let’s think, and make a mental list of all the big APIs that are existentially important to industry, and might prove to have copyright issues. I’m thinking... but coming up mostly empty.
The first thing that leaps to mind is AWS; Amazon has done some quiet saber-rattling about the APIs, and Eucalyptus took out a license. I think this is worth worrying about. Also, has Google been clear about the status of their Cloud APIs?
An OSS to-do · I think this means anyone who ships open-source software has a new line-item in their licensing work: Make sure it’s legally clear the API is freely re-implementable. Me, like everyone else I just copy the Apache or GPL boilerplate into my files. Is that good enough? I have no idea.
This is particularly interesting when a new OSS platform that wants widespread adoption has a big organization behind it: I’m looking at you, Go and Dart.
For the moment · To be safe, let’s just assume APIs are copyright-able, however crazy that seems, and have a close beady-eyed look at the ones we depend on.
The good news is, I just don’t see that many which really matter and are open to rentier exploitation.