|
Authored by: Anonymous on Monday, April 30 2012 @ 06:00 PM EDT |
We know Oracle have some problems with their registrations on this topic.
We also know (I think) that there is no such complete work as the 37 APIs. The
full work is the entire java API set. Of which Android only uses a portion.
And of the portion, all they actually use are the names and signatures (ruled
to be not protected), and the SSO (which is entirely defined by the names ie.
java.math.max and its signature and all the other non protected names and
signatures fully specify the SSO. There is nothing else to it. It makes no
sense
to claim the SSO is covered but not the names. None at all.)
IANAL, but it seems that Oracle only have a claim on the full SSO of the java
APIs (which means they have nothing, as the names and signatures aren't
covered), and even if they do manage to sort out that rather intractable
sounding problem, the 37 / 166 de minimis issue seems to arise more
strongly.
And even in the case that they get past that, they then risk the judge ruling
that it's not copyrightable anyway.
by my (meagre) understanding, they have a serious uphill fight on that issue.
[ Reply to This | Parent | # ]
|
|
|
|
|