05.11.14
Analysis of Text From the CAFC Reveals Lack of Technical Comprehension
Lawyers deciding on technical issues
Summary: The Court of Appeals for the Federal Circuit (CAFC) shows us yet again that it does not understand technology and its latest ruling is harmful to the technical community
YESTERDAY we wrote about the menacing CAFC ruling, which basically throws a lot of FOSS under the rug (by extension) for it alleges that APIs are copyrightable and that their reuse does not qualify as fair use. We have already criticised CAFC for being very pro-software patents and for being utterly clueless on technical matters on numerous occasions, so the latest decision from it oughtn’t be so shocking. As Ars Technica put it, “Google, which said it was exploring its legal options, decried Friday’s ruling. The Mountain View, CA-based media giant said the decision “sets a damaging precedent for computer science and software development.””
Google is correct and it will hopefully appeal this decision. What we have here is misuse of copyrights, SCO style, by Oracle.
TechDirt posted the best rebuttal to this decision, attracting hundreds of comments and revealing a lot of holes and mistakes in CAFC’s ruling (the text). Here’s a sample:
Appeals Court Doesn’t Understand The Difference Between Software And An API; Declares APIs Copyrightable
[...]
We sort of expected this to happen after the appeals court for the Federal Circuit (CAFC) held its oral arguments back in December, but CAFC has now spit at basic common sense and has declared that you can copyright an API. As we noted, back when Judge William Alsup (who learned to code Java to better understand the issues in the case) ruled that APIs were not subject to copyright protection, his ruling was somewhat unique in that it was clearly directed as much at an appeals court panel who would be hearing the appeal as it was at the parties. Alsup rightly suspected that the judges on the appeal wouldn’t actually understand the issues as well as he did, and tried to break it down clearly for them. Unfortunately, the three judge CAFC panel did not pay attention. The ruling is so bad that legal scholars are suggesting that it may be as bad as the horrific ruling in the Garcia case.
[...]
As for the ruling itself… well… it’s bad. The court seems to not understand what an API is, confusing it with software functionality. It also appears to misread Judge Alsup’s ruling, thinking that he’s mistakenly using a fair use analysis to determine whether or not something is copyrightable. But that was not the basis of Judge Alsup’s ruling. He very specifically noted that the “command structure is a system or method of operation under Section 102(b) of the Copyright Act and, therefore, cannot be copyrighted.” The CAFC panel doesn’t seem to understand this at all.
[...]
It seems fairly clear that the CAFC judges don’t understand the difference between an API and software. And thus they make a decision that makes no sense. There is no distinction recognized when it comes to the functionality of an API and how it’s entirely different than the purpose of the software itself. This is especially clear towards the end, in which the CAFC ruling misrepresents some discussions on whether certain functionality is best protected by patents or copyright. But the problem is that they misinterpret statements people are making about APIs, thinking that those statements were made about software as a whole. This is just a flat-out fundamental misunderstanding of what an API is, assuming that it’s just software.
[...]
Note that “[software]” thrown in before interfaces? Google is talking about whether APIs — “application programming interfaces” — are copyrightable. Not whether or not software is copyrightable. And yet the CAFC doesn’t even seem to realize this. Ridiculously, CAFC then uses its own misunderstanding and misquote, and points to some of the (many) arguments where people argue that patents are inappropriate for software to dismiss Google’s argument about APIs. It honestly doesn’t realize that it’s comparing two totally different things. What lots of people agree on: software shouldn’t be patentable and APIs shouldn’t be copyrightable, but software can be copyrightable and API functionality may be patentable. But by confusing APIs and software, CAFC totally misreads both arguments.
This will probably go to SCOTUS next (unless they decline to weigh in), but in the mean time it spreads uncertainty and doubt, harming not only Free software developers but developers in general. As TechDirt put it, “CAFC has mucked up another form of intellectual property law through a basic (and near total) misunderstanding of technology.” █
Content is available under CC-BY-SA