Slashdot Mirror


Oracle Claims Google 'Directly Copied' Our Java Code

itwbennett writes "On Wednesday, Oracle amended the lawsuit it filed against Google in August, saying that 'approximately one third of Android's Application Programmer Interface (API) packages' are 'derivative of Oracle's copyrighted Java API packages' and related documents. In particular, 'the infringed elements of Oracle America's copyrighted work include Java method and class names, definitions, organization, and parameters; the structure, organization and content of Java class libraries; and the content and organization of Java's documentation,' Oracle says. 'In at least several instances, Android computer program code also was directly copied from copyrighted Oracle America code,' Oracle alleges."

7 of 675 comments (clear)

  1. You don't know what the fuck you are talking about by pavon · · Score: 4, Informative

    The JDK that ships with Android is just a subset of Harmony, which is released under the Apache license. All improvements made by Google have been folded back into the project. The additional non-standard libraries they ship with android, are also opens source.

  2. Only if they are certified Java by JSBiff · · Score: 5, Informative

    I want to start by saying I'm not making any commentary here on the validity of Oracle's claims regarding direct copying (I suspect they are making that claim just because class names and methods are the same for some classes, for compatibility purposes).

    The thing is, Google doesn't claim Dalvik is "Java". They aren't using a Java license. Yes, you can create a free/open-source implementation of Java, as long as you are licensing from Sun/Oracle under the terms of the Java license.

    Google created something very similar to Java, but they are not calling it Java, and do not claim to have licensed Java from Sun/Oracle. I believe they claim copyright over the entire Dalvik VM and API. That makes a world of difference, legally, and so they can't use the defense the parent is suggesting.

  3. Re:Here we go again (SCO) by AmaDaden · · Score: 5, Informative

    James Gosling confirmed this some time ago "During the integration meetings between Sun and Oracle where we were being grilled about the patent situation between Sun and Google, we could see the Oracle lawyer's eyes sparkle. Filing patent suits was never in Sun's genetic code. Alas.... " http://nighthacks.com/roller/jag/entry/the_shit_finally_hits_the

  4. Re:Here we go again (SCO) by Nethemas+the+Great · · Score: 4, Informative

    I thought most of us saw the obvious reasons already. Sun was rather like a gift wrapped fruit basket.

    • They were constantly struggling with money problems making them weak to takeovers.
    • MySQL, Oracle's database division's biggest threat was purchased by Sun.
    • Sun owns Java, and more importantly J2EE--the technology powering the overwhelming majority of every corporate back-end that isn't .NET.
    • Sun railed hard against software patents, Oracle loves software patents, uses them as a profit center
    • Sun possesses a 10-year, patent non-aggression pact with Microsoft (started in 2004)
    • Sun has a somewhat sizable patent portfolio, including pertaining to Java, anyone not deriving from OpenJDK (which has permanent indemnification) is subject to litigation.
    • Most of Sun's software patents were as yet untapped (they never sued for licensing agreements) potential points of licensing revenue.
    • The Java specifications are copyrighted. There are a number of APIs that have similar designs
    --
    Two of my imaginary friends reproduced once ... with negative results.
  5. Small nit-pick by nedwidek · · Score: 5, Informative

    Not all of Sun's Java code went into Harmony et. al. So, maybe.

    The point of the project was that NONE of Sun's Java code would go into the project. They started with a clean slate and implemented all of the methods with their own code. They also had processes in place with the intention of keeping out the original Java code in contributions.

    Oracle is basically stating that by using the same package names, class names, and parameters that Android is an infringing derivative. This is the same argument as the SCO ABI argument. That was laughed out of court IIRC.

    --
    Post anonymously - For when your opinion embarrasses even you!
  6. Re:Here we go again (SCO) by butlerm · · Score: 4, Informative

    In Baystate v. Bentley Systems (1997), a district court held that technical interfaces including programmer APIs are not copyrightable under the scenes a faire and other copyright doctrines. If this logic is followed by the court in the Oracle case, Google will be held harmless from any claims of copyright infringement.

    This all despite the creativity that went into the API design in the first place. The practical benefit of not proscribing the copying of technical interfaces should be obvious. If such copying was proscribed, no one could make compatible software without permission of the original manufacturer anymore. File formats themselves might be protected to the degree that in the absence of any patent, it might be illegal to write code that reads and writes your own data.