|
| Authored by: naka on Saturday, April 21 2012 @ 03:19 PM EDT |
According to Oracle's trial brief there was also:
6.
Eight Android source code files (and corresponding object code),
AclEntryImpl.java, AclImpl.java, GroupImpl.java, OwnerImpl.java,
PermissionImpl.java, PrincipalImpl.java, PolicyNodeImpl.java,
AclEnumerator.java, which are not part of Android’s implementation of the 37 API
packages.
7. Comments contained in two Android source code files,
CodeSourceTest.java and CollectionCertStoreParametersTest.java, which are not
part of Android’s implementation of the 37 API
packages.
Your comment does make me wonder though... Will
the jury be left hanging while the lawyers hash this API stuff out with the
judge? [ Reply to This | Parent | # ]
|
|
|
| Authored by: Anonymous on Saturday, April 21 2012 @ 03:31 PM EDT |
I believe the jury would still decide if google willfully
infringed, assuming of course the judge decides that there is
even copyright to willfully infringe.[ Reply to This | Parent | # ]
|
|
|
| Authored by: Anonymous on Saturday, April 21 2012 @ 07:42 PM EDT |
Looks like it.
And interestingly, if he wasn't employed by Oracle to write the code, he not
Oracle still owns the copyright on what he created.
And given that Oracle have the history of the code in whatever version control
software system they have, this all starts to look very dubious for Oracle.
Effectively all Oracle have achieved so far is prove to the Jury that they are
thieves and liars - the jury may not get to rule on the (c), but that history is
one hell of a hurdle for Oracle to get over for a favourable ruling from the
same group of people on the patents.
[ Reply to This | Parent | # ]
|
|
|
| Authored by: Anonymous on Saturday, April 21 2012 @ 07:48 PM EDT |
The 9 lines of rangeCheck() code (within the 900 lines of TimSort) may have been
donated back to Oracle Java but those 9 lines were copied from an existing
private method within Arrays. That is the issue here. The copying.
Of course the author has stated that his use of the copied rangeCheck() was
temporary and he anticipated that TimSort would be merged back into Arrays with
only the original rangeCheck() being used. I believe it. It's a mountain being
made out of a molehill.[ Reply to This | Parent | # ]
|
|
