These are the statutory fair use factors the jury was required to consider (17 U.S.C. 107): (1) the purpose and character of the use, including whether such use is of a commercial nature or is for nonprofit educational purposes; (2) the nature of the copyrighted work; (3) the amount and substantiality of the portion used in relation to the copyrighted work as a whole; and (4) the effect of the use upon the potential…
Would that be like Oracle arguing jury nullification? It seems that the case law on nullification is that the jury's verdict is the definition unless vacated by procedural error. Thoughts?
Jury in Oracle v. Google finds in Google's favour
31–40 of 409 posts
Re: Jury in Oracle v. Google finds in Google's favour
#32But the fact that Oracle could get this close and spin deceit to a non-technical Jury to decide whether using API declarations from an OSS code-base would in some universe entitle them to a $9B payday, is frightening.
Re: Jury in Oracle v. Google finds in Google's favour
#33I wonder though how universal that ruling would be. Is any reimplementation of APIs going to be fair use, and if not, what are the criteria?
Re: Jury in Oracle v. Google finds in Google's favour
#34Earlier quoted context omitted.
Under the Copyright Act, the judge has discretion to award attorney fees to the prevailing party. [0] [0] https://www.law.cornell.edu/uscode/text/17/505
> Under the Copyright Act, the judge has discretion to award attorney fees to the prevailing party. [0] I think that'd be good for the ecosystem as it'd send a message that there will be consequence for pursuing frivolous lawsuits.
From a developer perspective, the ideal and just end result has always seemed rather obvious. However, the multi-year history of this case demonstrates the correct legal answer not so obvious, at least from a legal perspective.
For example, settling the issue on fair use was definitely not how most people thought/hoped this would shake out way back in the beginning of the law suit(s).
Re: Jury in Oracle v. Google finds in Google's favour
#35I'd also just like to give huge props to Sarah Jeong for keeping up such a high-quality live stream of tweets over the course of the entire trial. That's reporting done right.
Sarah's reporting: https://storify.com/sarahjeong
Parker's story: https://www.eff.org/deeplinks/2016/05/stakes-are-high-oracle...
Re: Jury in Oracle v. Google finds in Google's favour
#36My favourite part of the trial was when the judge told Oracle that a high schooler could write rangeCheck[1]. [1] https://developers.slashdot.org/story/12/05/16/1612228/judge...
Movement to a few minutes of terse explanations, including what the acronym GNU stands for: GNU is Not Unix.
“The G part stands for GNU?” Alsup asked in disbelief.
“Yes,” said Schwartz on the stand.
“That doesn’t make any sense,”
http://motherboard.vice.com/read/in-google-v-oracle-the-nerd...
Re: Jury in Oracle v. Google finds in Google's favour
#37This is possibly my best-case scenario. APIs are copywriteable (so says the Supreme Court), and this seems reasonable, since some APIs really are very good and treating them like an artistic work has benefits. But implementing them is fair use, preserving the utility of APIs for compatibility. Great news!
My understanding is that they refused to hear the case at the time. Is that, legally speaking, the same thing as agreeing with the circuit court, or could they have just refused to hear the case for some other reason (e.g. because they wanted to see the ruling on fair use first)?
Re: Jury in Oracle v. Google finds in Google's favour
#38Re: Jury in Oracle v. Google finds in Google's favour
#39This is possibly my best-case scenario. APIs are copywriteable (so says the Supreme Court), and this seems reasonable, since some APIs really are very good and treating them like an artistic work has benefits. But implementing them is fair use, preserving the utility of APIs for compatibility. Great news!
That decision was not made by the Supreme Court. The Supreme Court has not heard this case...yet.
Re: Jury in Oracle v. Google finds in Google's favour
#40These are the statutory fair use factors the jury was required to consider (17 U.S.C. 107): (1) the purpose and character of the use, including whether such use is of a commercial nature or is for nonprofit educational purposes; (2) the nature of the copyrighted work; (3) the amount and substantiality of the portion used in relation to the copyrighted work as a whole; and (4) the effect of the use upon the potential…
Agreed, it sounds like by the letter of the law Google's use was not "fair use", if you grant the assumption that APIs are copyrightable in the first place. What recourse does Oracle have now? Didn't the Supreme Court decline to take this issue up last time round? Does that mean this case is closed?