News for hackers. Stuff that matters.
Re:Google’s copying of the Java SE API was fair use [pdf] by franklampard on Monday April 05, 2021 @11:38AM (#26700428)
No but it’s okay to copy all the entry names in the encyclopedia and fill in the content yourself
Re:Google’s copying of the Java SE API was fair use [pdf] by chris_wot on Monday April 05, 2021 @12:58PM (#26701532)
Wikipedia already does this. For instance, there is currently a list of Australian Dictionary of Biography articles missing.[1]

I maintain a reflist of women in the ADB who have no Wikipedia article.[2]

1. https://en.wikipedia.org/wiki/Wikipedia:WikiProject_Australi...

2. https://en.wikipedia.org/wiki/User:Chris.sherlock/Australian...

Re:Google’s copying of the Java SE API was fair use [pdf] by Ekaros on Monday April 05, 2021 @02:46PM (#26702926)
I think all entry names in encyclopaedia would fall under collection of facts that is not copyrightable... Same goes for recipes. I don't see how list of words existing and being used would qualify as work under USA copy-right. The entries themselves though are likely in many cases protected, but likely not all.
Re:Google’s copying of the Java SE API was fair use [pdf] by benley on Monday April 05, 2021 @11:47AM (#26700522)
This is an excellent metaphor but now I am curious, is it literally true?
Re:Google’s copying of the Java SE API was fair use [pdf] by lostcolony on Monday April 05, 2021 @01:32PM (#26701942)
Would have to be tested in court.

Certainly, the fact that competing encyclopedias exist, and have for hundreds of years, with > 99% identical entry names (but of course, substantively different content), and that predicated not on any given invention or IP but rather the common use English language, would, I think, make the judges rather reluctant to rule differently even should there be 100% match in entries.

Re:Google’s copying of the Java SE API was fair use [pdf] by shmageggy on Monday April 05, 2021 @12:33PM (#26701160)
Two distinctions come to mind: the encyclopedia text doesn't have a "functional purpose" in the same way as the implementation of an API does, and thus there isn't a market of users who have pre-existing skills with encyclopedia entries that they could put to use if the entries were copied to another platform. In my non-lawyerly reading of the first bit of the decision it seemed they leaned on those aspects quite a bit.
Re:Google’s copying of the Java SE API was fair use [pdf] by nickspag on Monday April 05, 2021 @12:28PM (#26701084)
Probably not? The crux of the opinion seems to grant fair use because it enabled a "new and transformative use," which is a box that a different line of encyclopedias doesn't seem to check.
Re:Google’s copying of the Java SE API was fair use [pdf] by franklampard on Monday April 05, 2021 @03:51PM (#26703745)
Yeah I was giving an analogy similar to what Google is doing, but I am not sure of the legality of the exact case
Re:Google’s copying of the Java SE API was fair use [pdf] by ant1oz on Monday April 05, 2021 @12:30PM (#26701117)
Yes.