|
Authored by: pem on Saturday, May 05 2012 @ 07:36 PM EDT |
As discussed in comments on a previous Groklaw article, all
google has to do is to provide the translator running on servers outside the
US.
The whole thing is silly indeed. [ Reply to This | Parent | # ]
|
|
Authored by: Anonymous on Saturday, May 05 2012 @ 08:44 PM EDT |
If coded something that read in the class name path and that
code didn't hold the full name in any constant in the
translator program, then even if the absurd notion that
class name paths were copyrightable was true, it wouldn't be
possible to assert copyright over that program.
On top of that, you could write the translator program in
Java (with a Java license). The data produced with the non-
standard SSO class name paths would be the creative work of
the author (not Oracle), would not have the Java SSO naming
convention in it at all, and could be distributed to
billions of Android devices without Oracle being able to
assert copyright on it.
Attempting to copyright the Java SSO is an exercise in
idiocy.
[ Reply to This | Parent | # ]
|
|
|
|
|