In a significant ruling on March 27, 2018, the Court Appeals for the Federal Circuit ruled that Google's copying of 11,500 lines of code from the Java programming language was not fair use.[ref]Oracle America, Inc. v. Google, LLC 2108 WL 1473875 Court of Appeals for the Federal Circuit 2018[/ref]
Plaintiff Oracle America, the owner of Java, originally was seeking $8.8 billion dollars in damages, though they are now expected to ask for more than that.[ref]Google Could Owe Oracle $8.8 Billion in Android Fight-Patent, Trademark & Copyright Journal - Daily Edition (BNA) Bloomberg Law[/ref] The Court has remanded the case back to the District Court in California for a trial on damages.[ref]Oracle America, Inc. v. Google, LLC at 6 (pagination references are to the original opinion)[/ref]
The dispute arises out of one of Google's most frequent tactics: take what you want without permission, and duke it out in Court later.[ref]Id. at 10[/ref]
Google initially approached Oracle about a license to use the Java programming language in software it was developing for its smartphone. It had acquired Android, Inc. as a first step to doing so.[ref]Id.[/ref] It wanted to use the widely available Java as a means for third parties to write apps for the new operating system.[ref]Id.[/ref] Google had been unsuccessful in writing the "application programming interface" and thus needed to use Java's APIs.[ref]Id.[/ref] When negotiations stalled, Google simply copied the code anyway,[ref]Id.[/ref] and released the Android operating system in 2007.
Google insured the wide adoption of its (slightly purloined) operating system by giving it away for free to mobile device manufacturers.[ref]Id.[/ref] The effect on Oracle was immediate and severe. There was a massive switch away from using the Java platform, and those that did stay with Java demanded steep discounts.[ref]Id.[/ref]
Oracle filed suit in 2010. Since that time, the case has literally bounced around the Court system for the next 8 years, with sudden reversals of fortune for each side.
The first trial ended in a finding of infringement against Google. The trial Judge reversed that ruling, holding that the APIs were not copyrightable. In the appeal, the Federal Circuit then reversed that ruling, saying that the APIs were copyrightable. Google filed a petition for certiorari with the Supreme Court, who in response asked for an advisory opinion from the Solicitor General. The Solicitor General agreed that the APIs were copyrightable, leading to the Supreme Court denying the petition. The case then headed back to California to determine whether Google's copying was (all together now) fair use. The jury did return a finding of fair use. In the inevitable appeal that followed, the case wound up back before the Court of Appeals for the Federal Circuit, who now ruled the copying not to be fair use as a matter of law, and sent the case back to California for a trial on damages.[ref]Id. at 6-7[/ref]
If you are wondering (as did I) how a copyright case wound up at the Court of Appeals for the Federal Circuit, it is because Oracle's case originally contained a patent claim in addition to the copyright claim. Even though the patent claim has since been removed from the case, its original presence means the appeal goes to the Federal Circuit, which has exclusive jurisdiction over patent appeals.[ref]Id. at 15[/ref] Even though the Federal Circuit is obliged to follow 9th Circuit precedent, Google probably feels that they would have gotten a different result in their "home court." Google apologist, the Electronic Frontier Foundation, makes no bones about this point, whining that the Federal Circuit was a playing field slanted in favor of the Plaintiff.[ref]Federal Circuit Continues to Screw Up Copyright Law and Thwart Innovation[/ref]
Since this is a fair use case, and we've got Google as a defendant, it's not hard to guess how Google is going to defend its verbatim copying: (all together now) it's "transformative."
The Court spends 9 pages addressing Google's argument, so there can be no complaint that every point was not seriously considered. Yet, in the final analysis, Google loses every single point.
"Google's use of the API packages is not transformative as a matter of law because: (1) it does not fit within the uses listed in the preamble to § 107; (2) the purpose of the API packages in Android is the same as the purpose of the packages in the Java platform; (3) Google made no alteration to the expressive content or message of the copyrighted material; and (4) smartphones were not a new context."[ref]Oracle America, Inc. v. Google, LLC at 33[/ref]
"Google's primary argument on appeal is that Android is transformative because Google incorporated the declarations and SSO of the 37 API packages into a new context—smartphones. But the record showed that Java SE APIs were in smartphones before Android entered the market. Specifically, Oracle presented evidence that Java SE was in SavaJe mobile phones and that Oracle licensed Java SE to other smartphone manufacturers, including Danger and Nokia. Because the Java SE was already being used in smartphones, Google did not ‘transform' the copyrighted material into a new context and no reasonable jury could conclude otherwise."[ref]Id. at 36-37[/ref]
It is reassuring that a Court finally looks to the wording of Section 107 guidance. The primary reason for fair use is to promote criticism, commentary, news reporting and the like. Too often, fair use is stretched to absurd lengths to justify the result the Court wishes.[ref]Has This Court Decision Rendered the Creative Commons License Unenforceable?[/ref] The whole argument that an exact copy merely placed into a different setting, somehow "transforms" does not hold true to the purposes of fair use of promoting criticism, commentary and news reporting.
But the most absurd argument put forth by Google was the assertion that because it gave away the Android operating system for free, and its revenue was from advertising, that this made it a non-commercial use.[ref]Oracle America, Inc. v. Google, LLC at 29[/ref] Under this loopy theory, every pirate website in the world could not be held liable for copyright infringement for allowing users to download pirated works for free. Of course Google, and its apologist the EFF, would love for this to be true, but the Court rules decisively this is not the case.
"First, the fact that Android is free of charge does not make Google's use of the Java API packages noncommercial. Giving customers ‘for free something they would ordinarily have to buy' can constitute commercial use (citation omitted)… [T]he question ‘is not whether the sole motive of the use is monetary gain but whether the user stands to profit from exploitation of the copyrighted material without paying the customary price.'(citation omitted)… [T]o the extent we must assume the jury found Google's use of the API packages to be anything other than overwhelmingly commercial, that conclusion finds no substantial evidentiary support in the record. Accordingly, Google's commercial use of the API packages weighs against a finding of fair use."[ref]Id. at 29-30[/ref]
If the use is commercial, and non-transformative, this is a big strike against Google, because, as we have seen time and time again, Courts tend to let the "transformative" label turn into a trump card.
The Court then turns to the second factor: the nature of the work used. There was conflicting testimony as to whether the APIs were more functional or artistic. The Court held that a reasonable jury had sufficient evidence to determine that the nature was primarily functional, and that this would tend to favor a finding of fair use.[ref]Id. at 44[/ref]
The third factor, the amount and substantiality of the taking, winds up being ruled neutral to perhaps weighing against fair use.[ref]Id. at 48[/ref]
The amount copied by Google was 11,500 lines of code. The Java SE platform has 2.86 million lines of code. So, it would seem that the portion used is very small. The problem is that only 170 lines of code were necessary to write in the Java language. Google copied 11,500 lines, or 11,300 lines more than were necessary.[ref]Id. at 46[/ref]
"Google sought ‘to capitalize on the fact that software developers were already trained and experienced in using the Java API packages at issue.' (citation omitted) But there is no inherent right to copy in order to capitalize on the popularity of the copyrighted work or to meet the expectations of intended customers. Taking those aspects of the copyrighted material that were familiar to software developers to create a similar work designed to be popular with those same developers is not fair use." (emphasis added)[ref]Id. at 47[/ref]
As to the fourth factor, market harm, the Court found plenty of evidence of harm to Oracle.
"Specifically, the jury heard testimony that Java SE was already in smartphones, including Blackberry, SavaJe, Danger, and Nokia. That Android competed directly with Java SE in the market for mobile devices is sufficient to undercut Google's market harm arguments. With respect to tablets, the evidence showed that Oracle licensed Java SE for the Amazon Kindle. After Android's release, however, Amazon was faced with two competing options—Java SE and Android—and selected Android. The jury also heard evidence that Amazon later used the fact that Android was free to negotiate a steep discount to use Java SE in its newer e-reader. In other words, the record contained substantial evidence that Android was used as a substitute for Java SE and had a direct market impact. Given this evidence of actual market harm, no reasonable jury could have concluded that there was no market harm to Oracle from Google's copying."[ref]Id.[/ref]
"Android's release effectively replaced Java SE as the supplier of Oracle's copyrighted works and prevented Oracle from participating in developing markets. This superseding use is inherently unfair."[ref]Id. at 54[/ref]
But what was probably the killer nail in the coffin for Google, was its admission that it could have written its own APIs for Android, but was having problems, so it resorted to copying Oracle APIs.[ref]Id. at 9 and at 27[/ref]
"Google could have furthered copyright's goals of promoting creative expression and innovation by developing its own APIs, or by licensing Oracle's APIs for use in developing a new platform, it chose to copy Oracle's creative efforts instead. There is nothing fair about taking a copyrighted work verbatim and using it for the same purpose and function as the original in a competing platform."[ref]Id. at 54[/ref] (emphasis added)
Again, we need to kill once and for all the idea that people cannot create unless they are able to copy what someone else has done.
As the EFF whines "the Ninth Circuit generally protects innovation by recognizing that copying of a functional work, like an API, is often necessary and appropriate in order to make something new."[ref]Federal Circuit Continues to Screw Up Copyright Law and Thwart Innovation[/ref]
How in the world is something "new" when you copied it from someone else? Copying is not creativity![ref]Copying Is Not Creativity! Why Creative Artists Don't Need the Public Domain[/ref]
What now? A second petition to the Supreme Court is a foregone conclusion. Whether the Court would choose to hear it is anybody's guess. It might be a good opportunity to reign back in the mess that is transformative use. But barring that, the case will return to California for a trial on damages. I'm sure Oracle will have plenty of evidence as to their lost licensing revenue for Java, and on the other side there's the fact that Google realized $42 billion dollars in revenue from advertising on Android.[ref]Oracle America, Inc. v. Google, LLC at 10[/ref]
Oracle has found the droids they were looking for. And it's going to get very expensive for Google.
If you are are involved in the real estate business, (or even if you're not, because it's such a well-known cliché) the three most important things that govern the value of a particular piece of property are "location, location and location."
In dealing with copyright in the modern internet era, this has also become true. Websites (who more often than not are doing something they shouldn't) claim to be exempt from liability for copyright infringement because of the "location" of the infringing files. They promote a theory that since the infringing files are located "there" and not "here," that they have no liability for copyright infringement. Indeed, this is the entire argument of notorious sites like The Pirate Bay, backed by the usual suspects of infringement apologists like Public Knowledge and the Electronic Frontier Foundation,[ref]Federal Judge Says Embedding a Tweet Can Be Copyright Infringement[/ref] who maintain the idea comes from "years of settled precedent."[ref]Id.[/ref]
Guess what? It's not settled precedent at all.
This is what is known as the "Server Test," and originates with the 9th Circuit Court of Appeals. In the case of Perfect 10 v. Google,[ref]508 F.3d 1146 (9th Cir. 2007)[/ref] they ruled that liability for direct copyright infringement depended upon whether the infringing images were stored on the defendant's server (in this case, Google) or was simply imbedded or linked from a 3rd party server. If it was the latter, there was no direct infringement by Google.
However, this ruling has failed to be followed by other District Courts around the country. In a thoroughly researched opinion, the District Court for the Southern District of New York in the closely watched case of Goldman v. Breitbart News Network,[ref]2018 WL 911340 District Court for the Southern District of New York 2018[/ref] recently found that "[f]our courts in this district have discussed the Server Test and Perfect 10's holding; none have adopted the Server Test for the display right."[ref]2018 WL 911340 at 5[/ref]
After an intensive survey of those cases that have squarely addressed the display right issue, the Court concludes: "this Court is aware of only three decisions outside of the Ninth Circuit considering the display right in light of Perfect 10; one from the Seventh Circuit which adopted the Server Test for contributory liability, one from the Southern District which stated as a factual matter only that Perfect 10 existed, and one from the Northern District of Texas rejecting Perfect 10."[ref]Id. at 6[/ref]
"Years of settled precedent?" Hardly.
In the span of about six weeks, we have received four opinions, three in the United States and one in Germany, where three out of the four cases hold "it's not where the copy is stored, it is where the damage occurs that matters."
First up is the case from Germany of S. Fischer Verlag Gmbh v. Project Gutenburg Literary Archive.[ref]S. Fischer Verlag GmbH vs. Project Gutenberg Literary Archive Foundation[/ref] (N.B. endnote contains a link to an English Translation).
The facts are simple and undisputed. Project Gutenberg is a not-for-profit internet archive that makes digital copies of public domain works available for download. Its website states:
"This eBook is for the use of anyone anywhere at no cost with almost no restrictions whatsoever. You may copy it, give it away or re-use it under the terms of the Project Gutenberg License included with this eBook or online at www.gutenberg.org."[ref]S. Fischer Verlag Gmbh v. Project Gutenburg at 4 (emphasis added)[/ref]
Problem is, PG only checks to see if the book is in the public domain in the United States. It conveniently leaves it up to the downloader to determine if the work is protected by copyright in the country of the downloader.[ref]Id. at 5[/ref]
It turns out that PG was delivering into Germany, books in German, by German authors where the books were in the public domain in the United States, but not in Germany. A German publisher of some of these works made contact with PG to get these items removed. The response by PG can be best characterized as lackadaisical and indifferent, ultimately resulting in a refusal to remove the works at all.[ref]Id. at 5-6[/ref]
The German publishers sued PG in Germany, alleging infringements of 18 works to which they held the copyright. PG defended the suit claiming:
- We don't know who is downloading our works or how often, since we don't keep track.
- Providing this information is just too darn difficult so we shouldn't have to do it.
- We are wholly located within the U.S. so German law does not apply to us.
- We tell users not to download works which are under copyright protection in their country.
- That people download copyright protected works anyway is not our problem.
- Even though part of the website is in German, we are only targeting German speakers in the U.S.
- The requested "geo-blocking" is too easily circumvented, so we shouldn't have to do it at all.[ref]Id. at 8-9[/ref]
- Our lawyers told us it was OK.[ref]Id.[/ref] (seriously)
- Under German law, an offense is committed not only in the place where committed but also in the place where the offense had its effect.[ref]Id. at 9-10[/ref]
- Material which a website makes publically accessible in Germany, and which material is protected under German law, is an unlawful act committed in Germany.[ref]Id. at 10[/ref]
- PG targets German users by having parts of the website in German, offering works by German authors, and explicitly states that the eBook may be used by "anyone, anywhere."[ref]Id.[/ref]
- Alleged lack of proof of actual downloads is not dispositive. Since PG openly targets German users to download infringing works, "infringements are to be expected."[ref]Id. at 19[/ref]
- "[M]aintaining a fully automated video-on-demand service cannot constitute a copyright violation because the end user, who ultimately selects which content to view, is alone liable for any infringement."[ref]Id. at 8[/ref]
- "[B]ecause its conduct occurred exclusively in Poland, imposing Copyright Act liability on the basis of that conduct would amount to an impermissible extraterritorial application of the Act."[ref]Id.[/ref]
- It's not my fault that by making it easy for infringements to occur, that actual infringements do occur; and
- It's not my fault that your window is damaged, because I threw the rock from my own yard.
No Subjects
February 26, 2018 saw the commencement of "Fair Use Week."[ref]Columbia University's Copyright Advisory Services Fair Use Contest to win an iPad![/ref] Intentionally or unintentionally, but certainly ironically, the Second Circuit Court of Appeals used this week to release its long awaited opinion in Fox News Network, LLC v. TVEyes, Inc.[ref]Fox News Network, LLC v.TVEyes, Inc 2018 WL 1057178 Second Circuit 2018[/ref] This decision completely rejects the fair use defense of TV video indexer TVEyes.
Faithful readers of this blog will recognize the business known as TVEyes. I have written about this service twice before, and in a lengthy post here,[ref]The "Eyes" Don't Quite Have It: Judge Rules Against TV Indexer's Fair Use Defenses[/ref] described the basis of the dispute with Fox News Network and the legal analysis of the fair use claim. Back then I wrote:
"TVEyes is a video indexer. It offers, for a fee, searchable segments of television shows. It uses the closed-captioning function to create a searchable database where one can search for how many times, and in what context, certain words and phrases occur in television shows. To this end, it records all of the content on more than 1,400 television and radio stations. One of these stations is the Fox News Network.
A subscriber can not only obtain a transcript of the segment of the show selected, he/she can also see a copy of the original video in which the usage occurred. TVEyes is definitely a "for profit" enterprise and has 22,000 subscribers. It is not available to the general public."[ref]Id.[/ref]
The District Court ruled on four specific points as to whether they were fair use:
- Allowing subscribers to "archive" segments on TVEyes' servers indefinitely
- Allowing subscribers to provide links to video content to non-subscribers of TVEyes
- Allowing searches by date and time, rather than keywords
- Allowing subscribers to download to their own computers' video segments free of restrictions
- Internet Archive
- American Library Association
- Association of College and Research Libraries
- Association of Research Libraries
- Society of American Archivists
- Electronic Frontier Foundation
- Public Knowledge
- Computer & Communications Industry Association
- Media Critics
- Professors of Intellectual Property Law
- National Association of Broadcasters
- Copyright Alliance
- American Photographic Artists
- American Society of Media Photographers
- Digital Media Licensing Association
- National Press Photographers Association
- Professional Photographers of America
- American Society of Journalists and Authors, Inc.
- National Cable & Telecommunications Association
- Cable News Network, Inc.
- Gray Television Group, Inc.
- Hearst Television, Inc.
- ITV America
- Intellectual Property Scholars
No Subjects