Re:Google’s copying of the Java SE API was fair use [pdf]
by AnimalMuppet on Monday April 05, 2021 @04:52PM
(#26704560)
No. "Assume it's copyrightable. It's still fair use." That means you don't have to answer "Is it copyrightable?" The Supreme Court generally prefers to not answer questions that they don't have to answer.
[ Parent
| on HN ]
Re:Google’s copying of the Java SE API was fair use [pdf]
by shemnon42 on Monday April 05, 2021 @05:07PM
(#26704747)
So in programmer speak
if (!isFairUse(workUnderInvestigation) && copyrightable(originalWork)) {
bigCopyrightPayout();
}
Short circuit on the and operator. It's fair use, so copyrightable will not be evaluated. Evaluating copyrightable has an obervable side effect of creating a precedent.
Re:Google’s copying of the Java SE API was fair use [pdf]
by AnimalMuppet on Monday April 05, 2021 @05:18PM
(#26704855)
Yes, exactly that. Why do the && in that order? Because isFairUse(workUnderInvestigation) was a much less expensive operation than copyrightable(originalWork) for this particular value of originalWork.
Re:Google’s copying of the Java SE API was fair use [pdf]
by shemnon42 on Monday April 05, 2021 @06:49PM
(#26705648)
That is the order scotus considered it.
Re:Google’s copying of the Java SE API was fair use [pdf]
by AnimalMuppet on Monday April 05, 2021 @06:55PM
(#26705710)
Right, and that's why SCOTUS considered it in that order. Deciding API copyright was a much bigger decision than deciding fair use.