2 ms·

The same sort of API copyright that Oracle is trying to establish in this case. How things actually shake out would depend a lot on the specifics of the Court'

The same sort of API copyright that Oracle is trying to establish in this case. How things actually shake out would depend a lot on the specifics of the Court's ruling, and I am not a lawyer either. But, if the court rules that Oracle owns a copyright to the Java APIs, and that this means they can prevent others from implementing their own versions of those APIs, and this right remains in effect even though they release a full implementation of them under GPLv2, then I can't see any particular reason to expect that things would work differently for Amazon's APIs and Apache2.

johncolanduoni 6y ago
The difference is that the way Google used the APIs is not compatible with code use under the GPLv2 (in particular, they didn’t GPLv2 license it). If the original code implementing the APIs is Apache licensed however, you have a very free hand in changing the original code so you probably wouldn’t care about your working being considered a derivative of it. I’m not sure that absolves you categorically but it definitely sounds like a better position to be in.