US Supreme Court rules for Google over Oracle
Google’s purpose was to create a different task-related system for a different computing environment (smartphones) and to create a platform—the Android platform—that would help achieve and popularize that objective. The record demonstrates numerous ways in which reimplementing an interface can further the development of computer programs. Google’s purpose was therefore consistent with that creative progress that is the basic constitutional objective of copyright itself."
Posted Apr 5, 2021 15:01 UTC (Mon)
by fsamson (subscriber, #80923)
[Link]
Posted Apr 5, 2021 15:05 UTC (Mon)
by ddevault (subscriber, #99589)
[Link] (1 responses)
Posted Apr 5, 2021 20:26 UTC (Mon)
by rodgerd (guest, #58896)
[Link]
Posted Apr 5, 2021 15:27 UTC (Mon)
by bjartur (guest, #67801)
[Link] (12 responses)
Posted Apr 5, 2021 16:14 UTC (Mon)
by excors (subscriber, #95769)
[Link] (3 responses)
Fair use seems like a tricky balance of multiple factors, and in this case (based on the summary) it considers that Google was using the API to create something substantially new, and that the copied lines were 0.4% of the Sun Java API, and that Google's use of the API probably didn't harm the copyright holder (because Sun would have failed in the mobile market regardless of Android's success), so on balance it's the kind of thing that fair use was meant to permit. If you're doing something different to what Google did (like reimplementing the entire API with the intention of competing with the copyright holder) then the same arguments won't apply. You'll need different arguments for fair use (which the judge might or might not agree with), or you'll need to get the Supreme Court to say that APIs aren't copyrightable.
Posted Apr 5, 2021 18:33 UTC (Mon)
by madscientist (subscriber, #16861)
[Link] (2 responses)
Posted Apr 5, 2021 20:58 UTC (Mon)
by rgmoore (✭ supporter ✭, #75)
[Link] (1 responses)
Ruling on the narrowest available reasoning is a part of judicial restraint. If they can, judges will usually try to rule narrowly so their decision affects only the one case rather than broadly in a way that affects other cases. They can't necessarily avoid broad rulings- ruling in favor of Oracle in this case would have required them to decide that APIs were copyrightable- but when given a choice of reasons for ruling a specific way, they will usually choose the narrow grounds over the broad. This is true even of the Supreme Court, which has the power to set binding precedents and theoretically could change the law as it sees fit.
Even when looking at the details of the case, there's a clear hierarchy of reasoning. First they'll look at whether the plaintiff has the right to bring a suit and if they've chosen the right court. Then they'll look to see if their legal theory of the case is correct. Only when they've gone through that part will they bother looking at the facts.
Posted Apr 5, 2021 21:42 UTC (Mon)
by Paf (subscriber, #91811)
[Link]
Posted Apr 5, 2021 16:18 UTC (Mon)
by fsamson (subscriber, #80923)
[Link]
IANAL, but this reads basically as a broad "reimplementation of APIs is generally allowed, primarily for interoperability, because that is a fundamental principle how software operates (today)", very similar to the EU's stance on that.
Posted Apr 6, 2021 1:30 UTC (Tue)
by timrichardson (subscriber, #72836)
[Link] (6 responses)
Posted Apr 6, 2021 11:44 UTC (Tue)
by farnz (subscriber, #17727)
[Link]
Not quite; the court made no decision about whether or not the code in question is copyrightable, merely that fair use would cover the alleged infringements, and thus there's no reason to think about whether or not the code is copyrightable, because either it is, but fair use means no infringement, or it isn't and thus copyright cannot be infringed by Google's actions. Either way round, the result is that Google has obeyed the law.
Posted Apr 6, 2021 15:03 UTC (Tue)
by rgmoore (✭ supporter ✭, #75)
[Link] (3 responses)
The fair use test is actually a complex one. It's not a simple question of whether the copying falls into a bucket of allowed conduct. Instead, the court is supposed to consider multiple factors and decide how they balance each other. Those factors include:
In this case, the amount of copying is small, both in absolute amount and relative to the total size of the project, it's used commercially, the court determined it's not likely to compete with the original, and the use was considered to be transformative. Based on that, the court decided it was fair use. But they easily could have decided otherwise if they felt it was likely to compete with Java. I'm not sure the decision was correct- I think it really is competing with Java- but deciding on fair use let the court sidestep the question of whether the code was copyrightable at all.
Posted Apr 7, 2021 5:51 UTC (Wed)
by gfernandes (subscriber, #119910)
[Link] (2 responses)
Sun tried from the very beginning, to get java into mobile phones. And failed. Miserably.
So the value add of Android is the transformative use of the java API, clubbed with a Linux kernel, and a custom user land layer.
Don't forget that.
Java, by itself, only ever managed to conquer the server.
Posted Apr 7, 2021 12:59 UTC (Wed)
by plugwash (subscriber, #29694)
[Link] (1 responses)
There was a time, before the iphone and andriod took over the world, when J2ME support on phones was not uncommon.
Would android still have taken over the smartphone world if it had not used the Java programming language and APIs? If not would J2ME still be a thing? I doubt anyone really knows.
Posted Apr 8, 2021 18:36 UTC (Thu)
by khim (subscriber, #9252)
[Link]
If Android would have actually supported J2ME then it would have been an open question.
As it is it's pretty obvious that Sun's mobile efforts were largely irrelevant.
Java was used in Android because it was taught in colleges, essentially, not because J2ME was ever viable.
Posted Apr 11, 2021 16:05 UTC (Sun)
by mina86 (guest, #68442)
[Link]
This is a bit of technicality, but if one operates within fair use doctrine, they do not infringe copyright. In other words, fair use is not a defence in copyright infringement cases, it’s a right everyone has and if it applies than there’s no infringement.
Posted Apr 5, 2021 15:55 UTC (Mon)
by jthill (subscriber, #56558)
[Link] (5 responses)
Posted Apr 6, 2021 8:05 UTC (Tue)
by Felix.Braun (guest, #3032)
[Link]
Reading the Syllabus of the ruling, the most convincing argument to me seems to be this:
Posted Apr 6, 2021 9:11 UTC (Tue)
by Karellen (subscriber, #67644)
[Link] (3 responses)
Are you sure that interpretation is correct? As I understand it, material used under "fair use" is still considered to be under copyright - it's just that that particular use of that copyrighted material is allowed by the law anyway. For example, I could quote 10 lines from a 1,000 line program in order to analyse it for educational purposes, and that would be "fair use". 100 different people could do that for distinct 10 line segments in a way that covered every line of the program, and they would all be covered by "fair use". But every single line of the program would still be under copyright, and making copies of the entire program for redistribution would still be a breach of copyright with the full force of the legal system behind it.
Posted Apr 6, 2021 20:11 UTC (Tue)
by jthill (subscriber, #56558)
[Link] (2 responses)
I'm not sure. I believe there's a sound argument in support, so I posted, that is about as sure as I get on this stuff, but I don't play in the same league as supreme court justices, so me thinking my argument's sound doesn't make me feel any too very sure, no.
"the fair use of a copyrighted work […] is not an infringement of copyright." means—it flat out says—that copyright does not cover fair use. Remember that §107 was codifying centuries of common-law precedent, cases judges saying ~no, copyright doesn't cover that (or does), go away~. The justices walked through every factor they could find that would weigh on whether Google's use was fair (as they point out, the statutory factors are noted but not exclusive), and in Google's use they all came out in Google's favor. So *this* case is basically the poster child for a fair-use slam dunk. Copyright authority cannot be extended to interfere with fair use. Pointing out that copyright covers, that holders are still granted the authority to prohibit and get the state to enforce penalties for, unfair use, doesn't have any bearing on whether it covers fair use: it doesn't. It can't. That's beyond the time-honored and now statutory limit of copyright ablility.
So the question that remains is whether reimplementing API's is going to *necessarily* be fair use. In any real use, I think so.
For starters, as the opinion spends some effort elaborating, it's incorrect in this context to regard the entries in an index as some sort of independently-copyrighted work. What Google copied was 0.004 of the only clearly copyrightable work in evidence. I dare say that shouldn't surprise anyone here, I wouldn't expect anyone here to credit any notion of a market for some "Java API header-files-equivalent" work, nor the equivalent argument that there's some plausible transaction where having just the headers would be any viable substitute for an entire original work. I think they pretty much put paid to the silliness of the "but they copied all of what they copied!"-vuvuzela-blowing cohort. Substantiality will necessarily favor reimplementers.
They got API's right:
"purpose and character" won't necessarily do that. Google's use clearly does, as does say WINE's. I think it's good that cases are decided on the facts before them, and that courts don't spend time adjudicating cases that don't actually arise. So I really don't care about the contrived ten-lines-at-a-time effort. The law isn't about imagining every conceivable bad behavior and launching preemptive strikes, because there'd be no end. It's enough to deal with behaviors people actually engage in, eagerly anticipating more is just borrowing trouble, wasted effort.
So of the four statutory factors, three (substantiality, nature, market effect) will always land squarely in fair use territory, and "purpose and character" would only be troubling when considering a direct competitor with some clearly detrimental tendencies. I'm having trouble imagining such a thing, implementation is A Lot Of Work; and remember that IBM got hit with anti-trust for trying to conceal their interfaces (this was before copyright was codified), copyright is a created artifice, instituted to promote progress, not to entitle permanent possession.
Posted Apr 7, 2021 1:23 UTC (Wed)
by rgmoore (✭ supporter ✭, #75)
[Link] (1 responses)
No, that's not what it says. What it says is that fair use is an exception to the general rule that you aren't allowed to copy a work that's protected by copyright. Very importantly, the determination of fair use depends on the details of the derivative work, not the original work. One derivative work may make fair use of a copyrighted work and thus not be a violation of copyright, while a different derivative work may use the exact same part of the original but not be fair use.
To give a concrete example, consider one short scene from a movie. If a professor of film studies makes a lecture that uses that scene, that lecture may very well qualify as fair use. It is for non-profit educational use, it is transformative, it doesn't compete with the original work, and the excerpt is small in relation to the whole lecture. By all the prongs of the fair use test, it should qualify, and the copyright holder would likely lose if they sued the professor.
But now imagine if someone took the exact same scene from the movie, put a frame around it with some ads, and posted it to YouTube. It was done for profit, wasn't transformative, does compete with the original movie, and the excerpt is large in relation to the whole. A court would undoubtedly rule the use was infringing. That would be true even if the same court had ruled in favor of the film professor. Finding that one use didn't infringe doesn't invalidate the copyright; it just says that specific use was allowed.
In this case, the court ruled that Google's use didn't infringe. That doesn't touch on the deeper issue of whether the files Google copied could have been copyrighted in the first place. It's possible that header files, by themselves, are not sufficiently expressive to be copyrightable. A lot of people have been pushing for the courts to rule exactly that. The ruling in this case hints in that direction, but it doesn't say it outright. As of today, those files are still under copyright, and Oracle could sue the next company that tries to copy them.
Posted Apr 8, 2021 4:16 UTC (Thu)
by k8to (guest, #15413)
[Link]
Posted Apr 5, 2021 16:19 UTC (Mon)
by Wol (subscriber, #4433)
[Link] (1 responses)
So while Google is fair use, that means that someone else could use the same argument to sue over an API. Okay, case law says they will probably lose.
But it's not settled that APIs are copyrightable or not. If the court had found for Google on that point it would be game over for copyright trolls :-(
Cheers,
Posted Apr 5, 2021 17:11 UTC (Mon)
by rgmoore (✭ supporter ✭, #75)
[Link]
I'm not surprised. Judges generally try to rule on the narrowest basis available. They really prefer not to invent new legal principles if they can find a justification within existing law that lets them avoid the issue. So ruling that Google was making fair use avoids the question of whether APIs are copyrightable, though it does hint at it.
Posted Apr 5, 2021 17:47 UTC (Mon)
by alan (guest, #4018)
[Link]
Posted Apr 5, 2021 17:55 UTC (Mon)
by jhhaller (guest, #56103)
[Link] (12 responses)
While the court did not decide on whether this code was actually something for which copyright could be applied, the dissent did consider the code to be subject to copyright. A much better result would have resulted from convincing Congress that it is worthwhile to not subject software API definitions to copyright.
Posted Apr 5, 2021 18:31 UTC (Mon)
by nix (subscriber, #2304)
[Link] (3 responses)
I don't understand. The Kindle does not use Android, and never has. The Kindle Fire does use Android, and always has. Amazon never switched anything.
Posted Apr 5, 2021 19:14 UTC (Mon)
by Wol (subscriber, #4433)
[Link] (1 responses)
Cheers,
Posted Apr 5, 2021 19:36 UTC (Mon)
by nix (subscriber, #2304)
[Link]
Posted Apr 5, 2021 19:30 UTC (Mon)
by jhhaller (guest, #56103)
[Link]
Posted Apr 6, 2021 0:57 UTC (Tue)
by pabs (subscriber, #43278)
[Link]
Posted Apr 6, 2021 18:55 UTC (Tue)
by zuki (subscriber, #41808)
[Link] (4 responses)
It is!
>>> Declaring code defines the scope of a set of implementing code and gives a programmer a way to use it by shortcut. Because declaring code incorporates implementing code, it has no function on its own.
I think Justice Thomas gets this crucial fact wrong. I think any programmer would say that the opposite is true: "declaring code" does not "incorporate implementing code", and very much has a function of its own. As an example, in test-driver-development we are encouraged to create "declaring code" without any implementation, and then use it, first without any implementation… And obviously there are many examples of implementations created independently to an API specification.
>>> The functionality of both declaring code and implementing code will thus typically rise and fall together.
This is also not true.
And the rest of his argument seems to be based on this (false, imo) understanding.
He also summarizes the majority opinion nicely:
>>> The result of this distorting analysis is an opinion that makes it difficult to imagine any circumstance in which declaring code will remain protected by copyright.
Yay!
Posted Apr 6, 2021 19:19 UTC (Tue)
by NYKevin (subscriber, #129325)
[Link] (2 responses)
> JUSTICE THOMAS’ thoughtful dissent offers a very different view of how (and perhaps whether) fair use has any role
Breyer is basically saying "See how wrong Justice Thomas is? I barely even have to respond to his arguments, he practically refutes himself." All cloaked in a respectful and collegial tone, but damn, this is some savage legal writing.
(Disclaimer: I work for Google and wanted Google to win, but those two facts are mostly unrelated.)
Posted Apr 6, 2021 22:53 UTC (Tue)
by rodgerd (guest, #58896)
[Link]
Posted Apr 11, 2021 14:58 UTC (Sun)
by Nemo_bis (guest, #88187)
[Link]
Posted Apr 8, 2021 4:20 UTC (Thu)
by k8to (guest, #15413)
[Link]
Posted Apr 7, 2021 8:08 UTC (Wed)
by nim-nim (subscriber, #34454)
[Link] (1 responses)
However, because only one judge bought Oracle’s argument that Java ME was a great product betrayed by Google, no one bothered to disprove it.
Posted Apr 7, 2021 8:17 UTC (Wed)
by nim-nim (subscriber, #34454)
[Link]
Posted Apr 5, 2021 21:12 UTC (Mon)
by flussence (guest, #85566)
[Link] (25 responses)
And really, taking it straight to the SC was a grave tactical error. You'd think a company whose primary product is litigation would have known to go to East Texas like the rest of the NPE scum.
Posted Apr 5, 2021 21:45 UTC (Mon)
by Paf (subscriber, #91811)
[Link]
Posted Apr 5, 2021 21:47 UTC (Mon)
by Paf (subscriber, #91811)
[Link] (23 responses)
Posted Apr 5, 2021 23:11 UTC (Mon)
by bauermann (subscriber, #37575)
[Link] (20 responses)
Copyright is a made-up concept that the government decided to create to incentivize creators with the ultimate goal of improving society as a whole.
Posted Apr 6, 2021 1:17 UTC (Tue)
by rgmoore (✭ supporter ✭, #75)
[Link] (4 responses)
Yes, copyright is a made-up concept that exists as the government's way of achieving a broader social goal. But in the service of that goal, the government has made it possible to assign copyright to someone else. This is a good and necessary thing. At the very least, it must be possible for a copyright holder to assign the right to their work temporarily. If they can't temporarily assign the right to copy, authors couldn't get a publisher to print their book, musicians couldn't license their songs to be played on streaming services, and software authors couldn't allow users to put copies of their software on their computers. And if you're going to allow people to transfer the copyright temporarily in exchange for a fee, it would be strange not to let them transfer it permanently.
Posted Apr 6, 2021 10:35 UTC (Tue)
by sabroad (guest, #92392)
[Link] (2 responses)
Licences are not "transfers" of copyright, not even temporarily: only the copyright holder has the right to licence the work.
The reason for copyright assignment is not because licences exist but that work-for-hire is the norm.
Posted Apr 6, 2021 17:46 UTC (Tue)
by rgmoore (✭ supporter ✭, #75)
[Link] (1 responses)
Yes and no. An exclusive license looks a lot like a temporary transfer of the property, especially if it comes with sublicensing rights. I think this gets at a bigger reason our legal system tends to look at things like copyright as forms of property: it's a useful abstraction. Just as Unix treats all kinds of things as files, even when they aren't, the legal system treats all kinds of things as property even when they aren't. Our legal and business systems are built around the concept of property, and they've spent centuries learning how to reason about it. Treating more and more abstract kinds of things- contracts, obligations, debts, government granted privileges, or what have you- as property lets lawyers and business people apply those centuries of case law and business processes to them. Even if the abstraction is imperfect so there need to be new principles added, like fair use for copyright, starting from well established principles means they aren't inventing everything from scratch.
Posted Apr 7, 2021 0:04 UTC (Wed)
by bauermann (subscriber, #37575)
[Link]
It's an argument Lawrence Lessig made in the Free Culture book far better than I ever could. 🙂
Posted Apr 8, 2021 17:02 UTC (Thu)
by smurf (subscriber, #17840)
[Link]
So what happens instead? I sell an exclusive and perpetual license to exercise those rights to somebody else. Same effect as a copyright transfer but an entirely different legal theory behind it, which matters a lot e.g. when the work is translated to a new medium that didn't exist when the sale took place. Lawyers tend to have a lot of fun trying to guess the intent behind those contracts.
Posted Apr 6, 2021 9:18 UTC (Tue)
by pebolle (guest, #35204)
[Link] (12 responses)
As are property rights, contracts, corporations, permits, licenses, marriage or, I'd say, any legal concept. Some go back only a century or two, while other concepts go back thousands of years. And I'm sure there are (historic) societies that do not have one or more of the legal concepts we now take for granted. Or people advocating for their end in some societies.
Legal concepts are made up. So what?
Posted Apr 6, 2021 15:20 UTC (Tue)
by Wol (subscriber, #4433)
[Link] (3 responses)
Time Immemorial?
Which is a real thing. The definition varies, but it is English Law that pre-dates the concept of a "Jury of one's Peers" - peers is capitalised because it means a Lord of the Realm.
So basically, "time immemorial" is stuff that predates either Magna Carta, or the accession of Henry III, whichever date you choose as they're both roughly the same.
Cheers,
Posted Apr 6, 2021 16:47 UTC (Tue)
by amacater (subscriber, #790)
[Link]
Posted Apr 28, 2021 15:50 UTC (Wed)
by nix (subscriber, #2304)
[Link] (1 responses)
Where does *this* come from? Peers is capitalized because nouns were frequently (and irregularly) capitalized in written text back then. It's got nothing to do with lordship, and juries were never composed entirely of peers of the realm (who are called that because they are distinct from *other sorts* of peers).
Posted Apr 28, 2021 22:25 UTC (Wed)
by Wol (subscriber, #4433)
[Link]
Basically, it was a reigning in of the absolute powers of the King, and making him formally answerable to the Baronage. This is the birth of Parliament and the House of Lords, I guess... the King could no longer sling a Lord he'd fallen out with into the brig without at least the permission of the other Lords.
All part of the everlastng political struggle between those in power, and those who want to be in power.
Cheers,
Posted Apr 7, 2021 0:16 UTC (Wed)
by bauermann (subscriber, #37575)
[Link] (6 responses)
Some people would put property in that category, though that is controversial. In any case, the fact that one concept is thousands of years old and another is a few centuries years old is IMHO relevant.
In any case, I just brought this up because conflating property with copyright is a strategy that has been used to argue for stronger copyright protections without bringing up the necessary discussion about the benefit such change should bring to society. Therefore it's important to be aware that it's an analogy with important flaws.
Posted Apr 7, 2021 14:49 UTC (Wed)
by nim-nim (subscriber, #34454)
[Link] (5 responses)
Some states have been more honest about this all by claiming everything belonged to them and was just temporarily granted to inhabitants (most recently, the Soviets, but that is still the case for some kinds of “property” in some parts of the world, with foreign investors treating such grants as “property” because they effectively behave exactly the same way).
“Natural rights property” is another fiction invented by people that want to convince states they do not owe any taxes. It only works on very corrupt administrations.
Posted Apr 7, 2021 15:35 UTC (Wed)
by Wol (subscriber, #4433)
[Link] (3 responses)
The Doomsday book, for example (1086).
(Spelt that way because, for the Saxon landowners it recorded, it WAS doomsday.)
Cheers,
Posted Apr 7, 2021 16:27 UTC (Wed)
by micka (subscriber, #38720)
[Link]
Posted Apr 28, 2021 16:13 UTC (Wed)
by nix (subscriber, #2304)
[Link] (1 responses)
Well, it was spelt "Domesday", but that meant the same thing. Wikipedia says (and my undergrad-level profs also told me) that this is from OE and Norse "doom" meaning "law, judgement". The implication is that this was a book of unalterable law: this suggests that the book was considered ancient uncontradictable canon of sorts, and unsurprisingly this term is first found centuries after the book itself was composed, in the 13th century. The books' compilers didn't call them that at all! The survey the books record was semi-informally known simply as the Great Survey (the first of a number of Great Surveys in English history), and the record as any of a number of things, most commonly simply as (in Latin) the "enrolling". i.e. it was named practically, for what it was, an enrolling of properties and households, not metaphorically.
The meaning "doom" as in "disaster" is many centuries newer. The OED says that while "doomsday" in the meaning of "the day of judgement" is ancient, the related expansion of the term "doom" is much newer: 16th--17th century, and so, probably, is the implication that doomsday is in any way disastrous. (I have seen older uses of "doom" to mean "disaster" than the OED cites, which I should probably pass on if I can track them down again, but there's only about 50 years in it, certainly not centuries.)
Posted Apr 28, 2021 22:29 UTC (Wed)
by Wol (subscriber, #4433)
[Link]
Cheers,
Posted Apr 28, 2021 15:57 UTC (Wed)
by nix (subscriber, #2304)
[Link]
The opposite ("allodial title") is *extremely* rare these days and generally grandfathered in where possible at all with no way to place anything new under that title, most likely because almost all modern states want the right not only to tax property but also to go and do things on what you consider your property in some rare circumstances (putting out fires, arresting criminals etc).
Posted Apr 28, 2021 15:49 UTC (Wed)
by nix (subscriber, #2304)
[Link]
The way societies are constructed is a social construct, obviously enough. The law is an aspect of the way societies are constructed, so it's a social construct. It sits on biological underpinnings shared with many other animals driving emotions governing things like perceived fairness, retribution, etc, but it is still a social construct.
Posted Apr 10, 2021 20:36 UTC (Sat)
by Max.Hyre (subscriber, #1054)
[Link] (1 responses)
Posted Apr 10, 2021 22:26 UTC (Sat)
by Wol (subscriber, #4433)
[Link]
I believe theft is defined as "permanently depriving the owner of their property". Which copying a song most definitely does not.
Amd when joyriders nicked a car over here, I believe their defence council argued "it's not theft, they got their car back". So they had to bring in a new law of "TWOCing" - Taking WithOut Consent.
Cheers,
Posted Apr 6, 2021 1:58 UTC (Tue)
by flussence (guest, #85566)
[Link] (1 responses)
The *copyright holders* were compensated in a way they deemed fair. The *creators'* reaction can be summed up in one word: "Unsubscribe".
Posted Apr 11, 2021 16:21 UTC (Sun)
by mina86 (guest, #68442)
[Link]
Posted Apr 6, 2021 1:04 UTC (Tue)
by xtifr (guest, #143)
[Link] (3 responses)
I'm not entirely sure here, but it seems to me that they have very cleverly rendered the question of whether APIs are copyrightable to be basically irrelevant! What it looks like they're saying is that because the API was copied for compatibility reasons, and because this is the norm in the industry, Google's actions were (at worst) fair use. The thing is, I can't imagine any other reason for copying an API! So, basically, as long as your goal is compatibility (and what other goal could you have?), you should be fine! This is basically saying that APIs can't be protected under normal circumstances, even if they're technically copyrighted! If that's really what it means, then I'd have to say that it's about as favorable a ruling as I could have hoped for, even if it does look, at first, to be overly narrow!
Posted Apr 6, 2021 2:49 UTC (Tue)
by Otus (subscriber, #67685)
[Link]
Posted Apr 6, 2021 12:33 UTC (Tue)
by dottedmag (subscriber, #18590)
[Link]
Posted Apr 6, 2021 13:00 UTC (Tue)
by danielthompson (subscriber, #97243)
[Link]
This recognizes that the value of an API arises, in part, from skilled people learning to use it rather than through the effort of the author and that this shared investment by all parties weighs in favour of fair-use.
Posted Apr 15, 2021 21:23 UTC (Thu)
by clicea (guest, #75492)
[Link] (2 responses)
Posted Apr 15, 2021 22:47 UTC (Thu)
by mathstuf (subscriber, #69389)
[Link]
Also note that this ruling was decided on fair use. It doesn't say APIs are protected by copyright. Also doesn't say that they aren't. It says that *regardless* of the status, *Google* is protected by fair use for its use in *Android*. Not for use in GCS, not Amazon for AWS.
Posted Apr 16, 2021 0:30 UTC (Fri)
by Cyberax (✭ supporter ✭, #52523)
[Link]
US Supreme Court rules for Google over Oracle
Finally.
US Supreme Court rules for Google over Oracle
US Supreme Court rules for Google over Oracle
US Supreme Court rules for Google over Oracle
US Supreme Court rules for Google over Oracle
US Supreme Court rules for Google over Oracle
US Supreme Court rules for Google over Oracle
US Supreme Court rules for Google over Oracle
US Supreme Court rules for Google over Oracle
Their wording is quite easy to comprehend (i.e., non-legalese) and concise.
US Supreme Court rules for Google over Oracle
US Supreme Court rules for Google over Oracle
US Supreme Court rules for Google over Oracle
US Supreme Court rules for Google over Oracle
US Supreme Court rules for Google over Oracle
US Supreme Court rules for Google over Oracle
US Supreme Court rules for Google over Oracle
They got fair use and API's right and decided the case on that, because that was enough, pointing out that there's no need to rule on whether APIs would be copyrightable in the absence of fair use, because as a matter of law fair use makes them not copyrightable:
US Supreme Court rules for Google over Oracle
we hold that the copying here at issue nonetheless constituted a fair use. Hence, Google’s copying did not violate the
copyright law
.
and they run down the criteria: fair purpose, minimal copying in both absolute and relative terms, transformative use, no effect (in fact, they point out, on the record a positive effect) on the market for the protected work: Google's use was fair by every criterion.
For my money the most consequential holding is this:
The record demonstrates numerous ways in
which reimplementing an interface can further the development of
computer programs. Google’s purpose was therefore consistent with
that creative progress that is the basic constitutional objective of copyright itself
Which combined with the inescapable facts about APIs (which boil down to, they're not in any sense a substitute for the copyrighted work of which they're a tiny part) makes reimplementation a protected act not just because it's fair in the statutory sense but as an actual constitutional right.
US Supreme Court rules for Google over Oracle
Google copied approximately 11,500 lines of declaring code
from the API, which amounts to virtually all the declaring code needed
to call up hundreds of different tasks. [...] As part of an interface, the copied lines of code are inextricably bound to other lines of
code that are accessed by programmers. Google copied these lines not
because of their creativity or beauty but because they would allow programmers to bring their skills to a new smartphone computing environment.
US Supreme Court rules for Google over Oracle
because as a matter of law fair use makes them not copyrightable
US Supreme Court rules for Google over Oracle
The nature of the work at issue favors fair use. The copied
lines of code are part of a “user interface” that provides a way for programmers to access prewritten computer code through the use of simple commands
[and not the prewritten code itself] so "nature of the work" will always point to fair use.
US Supreme Court rules for Google over Oracle
"the fair use of a copyrighted work […] is not an infringement of copyright." means—it flat out says—that copyright does not cover fair use.
US Supreme Court rules for Google over Oracle
Not a complete victory :-(
Wol
Not a complete victory :-(
But it's not settled that APIs are copyrightable or not.
US Supreme Court rules for Google over Oracle
US Supreme Court rules for Google over Oracle
US Supreme Court rules for Google over Oracle
US Supreme Court rules for Google over Oracle
Wol
US Supreme Court rules for Google over Oracle
US Supreme Court rules for Google over Oracle
US Supreme Court rules for Google over Oracle
US Supreme Court rules for Google over Oracle
US Supreme Court rules for Google over Oracle
> to play for computer programs. We are told that no attempt
> to distinguish among computer code is tenable when considering “the nature of the work,” see post, at 10, even
> though there are important distinctions in the ways that
> programs are used and designed, post, at 18 (“The declaring
> code is what attracted programmers”). We are told that no
> reuse of code in a new program will ever have a valid “purpose and character,” post, at 16, even though the reasons
> for copying computer code may vary greatly and differ from
> those applicable to other sorts of works, ibid. (accepting
> that copying as part of “reverse engineer[ing] a system to
> ensure compatibility” could be a valid purpose). And we are
> told that our fair use analysis must prioritize certain factors
> over others, post, at 9, n. 5, even though our case law instructs that fair use depends on the context, see Campbell,
> 510 U. S., at 577–578.
US Supreme Court rules for Google over Oracle
US Supreme Court rules for Google over Oracle
US Supreme Court rules for Google over Oracle
US Supreme Court rules for Google over Oracle
US Supreme Court rules for Google over Oracle
US Supreme Court rules for Google over Oracle
US Supreme Court rules for Google over Oracle
US Supreme Court rules for Google over Oracle
US Supreme Court rules for Google over Oracle
US Supreme Court rules for Google over Oracle
Copyright is a made-up concept that the government decided to create to incentivize creators with the ultimate goal of improving society as a whole.
US Supreme Court rules for Google over Oracle
US Supreme Court rules for Google over Oracle
Licences are not "transfers" of copyright, not even temporarily: only the copyright holder has the right to licence the work.
US Supreme Court rules for Google over Oracle
US Supreme Court rules for Google over Oracle
US Supreme Court rules for Google over Oracle
US Supreme Court rules for Google over Oracle
Wol
US Supreme Court rules for Google over Oracle
US Supreme Court rules for Google over Oracle
US Supreme Court rules for Google over Oracle
Wol
US Supreme Court rules for Google over Oracle
US Supreme Court rules for Google over Oracle
US Supreme Court rules for Google over Oracle
Wol
US Supreme Court rules for Google over Oracle
US Supreme Court rules for Google over Oracle
US Supreme Court rules for Google over Oracle
Wol
US Supreme Court rules for Google over Oracle
US Supreme Court rules for Google over Oracle
I was once in a movie theater which played the RIAA propaganda equating copying a song with smashing a car window to steal a CD. Afterwards someone actually shouted out ``It's not theft, it's copyright infringement.''
Copyright != property
Copyright != property
Wol
US Supreme Court rules for Google over Oracle
US Supreme Court rules for Google over Oracle
US Supreme Court rules for Google over Oracle
US Supreme Court rules for Google over Oracle
US Supreme Court rules for Google over Oracle
US Supreme Court rules for Google over Oracle
US Supreme Court rules for Google over Oracle
US Supreme Court rules for Google over Oracle
US Supreme Court rules for Google over Oracle