Slashdot Mirror


US Justice Department Urges Supreme Court Not To Take Up Google v. Oracle

New submitter Areyoukiddingme writes: The Solicitor General of the Justice Department has filed a response to the US Supreme Court's solicitation of advice regarding the Google vs. Oracle ruling and subsequent overturning by the Federal Circuit. The response recommends that the Federal Circuit ruling stand, allowing Oracle to retain copyright to the Java API.

45 of 223 comments (clear)

  1. Clean room implementation? by ardentsoap · · Score: 5, Insightful

    So, I can't make an API that mimics theirs because copyright?

    1. Re:Clean room implementation? by kennykb · · Score: 4, Informative

      Yes. Exactly.

      It's all about the term of copyright versus the term of patent. Patent lasts only twenty years at present, while copyright is effectively perpetual (whenever Pooh and Mickey might enter the public domain, the legislators fix it). If copyright governs interfaces, that part of the law will keep the government from stealing IP away from its rightful owners after twenty years.

    2. Re:Clean room implementation? by XanC · · Score: 5, Insightful

      Can they make Compaq's reverse engineering of IBM's BIOS illegal retroactively, and take back much of the PC revolution?

    3. Re:Clean room implementation? by Richard_at_work · · Score: 2

      Doesn't the Linux kernel group hold a very similar stance in that you cannot use the kernels internal APIs without breaching copyright and thus falling under the GPL as a derivative work?

    4. Re:Clean room implementation? by The+Rizz · · Score: 5, Insightful

      If copyright governs interfaces, that part of the law will keep the government from stealing IP away from its rightful owners after twenty years.

      You mean stop government from returning it to the rightful owners. The public (and public domain) are the rightful owners of all information and works - copyright/patents just give exclusive use for a time.

    5. Re:Clean room implementation? by paskie · · Score: 2

      Right now they are talking about if the API is actually copyrighted. If it is, there is still a (good?) chance that fair use will allow you to reimplement it anyway; but that's going to be another court case, likely.

      --
      It's not the fall that kills you. It's the sudden stop at the end. -Douglas Adams
    6. Re:Clean room implementation? by jandrese · · Score: 5, Interesting

      If the laws we have now were in place back then the computer revolution wouldn't have happened. We would still be paying $5000 for IBM Mainframe access terminals.

      Or in a slightly less Dystopian view, computers today would look like iPhones, with one vendor having a stranglehold on the platform and completely anemic third party hardware support outside of cosmetics.

      --

      I read the internet for the articles.
    7. Re:Clean room implementation? by sycodon · · Score: 4, Insightful

      Oracle must have contributed to the right Administration official.

      --
      When Fascism comes to America, it will call itself Anti-Fascism, and tell you to give up your guns.
    8. Re:Clean room implementation? by Immerman · · Score: 4, Interesting

      I believe it's not that you can't use the API, but that you can't interface non-GPL code with the kernel due to the restrictions of the GPL. That you would use the API to do so is incidental to that restriction.

      If instead you want to build your own kernel implementing the same API, I don't believe they have any objection.

      --
      --- Most topics have many sides worth arguing, allow me to take one opposite you.
    9. Re:Clean room implementation? by ShanghaiBill · · Score: 4, Insightful

      Why because the court asked for the government's opinion?

      No. Because the government's opinion sounds like it was written by Oracle's general counsel

    10. Re:Clean room implementation? by s.petry · · Score: 3, Informative

      The Laws we have in place are the same as we had back then. The main difference today is that people holding public offices tend to flaunt their pay-for-play status, where back in the 80s/90s they were still attempting to hide it. The biggest harm to IT took a while to get precedents set, but really started almost immediately with "ideas" being patented and copyrighted (you can thank the first Bush for that lovely patent reform).

      As an example, Athena (X) was developed mostly by DARPA funding and grant money. Yet we had to see 32 screens worth of copyrights just to start the Xserver (okay, 32 is an exaggeration but the point remains). Some of these were to Universities like MIT, Berkley, and Stanford. Many others though were to Novell, Sun Microsystems, Hewlett-Packard, IBM, etc.. etc... And no, these were not "credits", but copyrights. This is why Linux started with a pretty old version of X and basically had to reinvent the wheel. Linux had 1 crappy pay-for version of CDE because some schlep company ended up buying copyrights to extort money from people.

      --

      -The wise argue that there are few absolutes, the fool argues that there are no probabilities.

    11. Re:Clean room implementation? by ShanghaiBill · · Score: 2

      I am bothered by technical capabilities being copyrighted instead of patented

      Interfaces, including APIs, should be neither copyrightable nor patentable. There is precedent for this in prior supreme court decisions concerning the interface for printer cartridges. In principle, this is no different.

    12. Re:Clean room implementation? by Richard_at_work · · Score: 2

      The only sway the GPL has here is due to copyright law, so if the GPL is in force in my example then that means the API is considered to be copyrighted...

      No copyright issues means no GPL restrictions.

    13. Re:Clean room implementation? by GigaplexNZ · · Score: 2

      The Laws we have in place are the same as we had back then.

      The DMCA most definitely wasn't in place back then.

    14. Re:Clean room implementation? by Archangel+Michael · · Score: 2, Insightful

      To be fair, if it was (R) it would have happened too. And when people say that the (D) and (R) are really different, you can point them to this case to show that ... no not really.

      --
      Agent K: A *person* is smart. People are dumb, stupid, panicky animals, and you know it.
    15. Re:Clean room implementation? by GigaplexNZ · · Score: 2, Insightful

      Nitpick - technically, we're talking about Java, where there are no header files. The interface is defined in the same source files as the implementation.

      Even so, I don't think an API should be copyrightable, but if it is, it should be considered fair use to actually use it. Otherwise, the software industry just wouldn't work.

    16. Re:Clean room implementation? by NostalgiaForInfinity · · Score: 3, Interesting

      Google did a copy/paste of the Java source code into their own source code.

      Google probably does copy/paste of the Java source code all the time, like lots of other people, because it's open source, so that is a meaningless accusation.

      Google distributed interface definitions that look very similar to Oracle's. That's probably because in Java, there really aren't a lot of different ways of describing the same interface. Furthermore, interfaces should not usually be considered copyrightable.

      Google also distributed some copyrighted Java source files. That was stupid, but those files appear to have been test cases, not code that ships on handsets, and it appears to have been unintentional. It's hard to argue that Oracle suffered any harm from that and Google came into compliance.

    17. Re:Clean room implementation? by UdoKeir · · Score: 5, Insightful

      Or Google has been resisting the NSA a little too much.

    18. Re:Clean room implementation? by Immerman · · Score: 4, Informative

      No, it does not. Re-read my post after you've had your morning coffee. You're free to use the API however you want, it's presumed not copyrightable. The *one* exception is using it for interacting with the Linux kernel, because the kernel *is* protected from such access by the GPL, and only GPL-compatible code is allowed to interact with its internals. The API is irrelevant to that fact - it's simply the interface used by those who *are* allowed to interact.

      --
      --- Most topics have many sides worth arguing, allow me to take one opposite you.
    19. Re:Clean room implementation? by DrJimbo · · Score: 2

      If I'm reading this right, Google incorporated Oracle's Standard Library wholesale, instead of re-implementing the Standard Library from scratch.

      You are not reading it right. The standard library was re-implemented using the same API. That's why the government's stance would destroy the software industry as we know it because a complete re-implementation would still be covered by the copyright of the original implementation. This is exactly copyrighting an idea instead of a particular expression of an idea.

      My guess is that the reason for this idiotic position is to intentionally kill off Linux and all independent software development in order to stop terrorism.

      --
      We don't see the world as it is, we see it as we are.
      -- Anais Nin
    20. Re:Clean room implementation? by h4ck7h3p14n37 · · Score: 2

      Nitpick - technically, we're talking about Java, where there are no header files. The interface is defined in the same source files as the implementation.

      You're correct that Java doesn't have header files; Java uses Interfaces which fulfill the same function. Best practice is to write your API using Interfaces, and not code to a particular implementation (classes).

      You can define Interfaces and Classes in the same source file, but people typically create a separate file for each one.

    21. Re:Clean room implementation? by david_thornley · · Score: 2

      You can use Linux APIs all you want, no problem.

      You can't link certain code directly into the Linux kernel, because at that point you're creating a derivative work that has to be licensed under the GPLv2, and if the license of the code you added isn't compatible with GPLv2 you cannot satisfy both licenses simultaneously.

      --
      "When you have eliminated the unacceptable, whatever is left, however improbable, must be the truthiness" - Holmes
    22. Re:Clean room implementation? by gnupun · · Score: 2

      It may be a lot of work to create a phone directory (at least it used to be), but the listings aren't copyrightable.

      Sorry, but APIs are not fixed format like directories: "name: ph. number." As I stated above, there are plenty of subjective and creative design decisions that go into creating an API. This is very similar to the subjective and creative decisions that go into writing a novel. Hence both APIs and books should receive copyright protection.

      For example, both OpenGL and DirectX are 3D APIs that can be used to write 3D games. However, the design decisions and structure of API is quite different.

      Only extremely trivial problem spaces yield fixed APIs. Massive APIs like the Java API which contains thousands of methods are not trivial and should receive copyright protection. Why should Google benefit from Java API's good design with $0 license payment?

  2. Java is done by Anonymous Coward · · Score: 4, Funny

    If this stands, Java's vaunted claim to being on "billions of devices" will soon become the punchline to a bad joke.

    1. Re:Java is done by ardentsoap · · Score: 3, Funny

      It's almost like Oracle is trying to kill Java. Wouldn't it have been easier to let Sun implode and fade away?

    2. Re:Java is done by Anonymous Coward · · Score: 5, Funny

      Yes, but that would take a couple billion years.

    3. Re:Java is done by dAzED1 · · Score: 3, Interesting

      Sun was flush with cash at the time of the acquisition, and also had a great deal of solid IP and customer faith. Solaris prior to Oracle was *the* most solid OS available in my opinion, and sparcs were always great for their target audience. Sun's only problem is the market became too commodity - fabbers need to make billions of chips now to stay competitive, and that just wasn't possible. But Sun had paths forward to fix these things - they were actually on the right road already, imo - forming ties with AMD, coming up with a way to keep their core but become commodity, by giving AMD access to high tech they needed. A road that Oracle took them off - Sun would be just fine today if Oracle hadn't bought them.

    4. Re:Java is done by MouseR · · Score: 2

      That's retarded. Oracle had (and maintains) a sizeable investment in Java and the rack servers for which Oracle is optimized for.

      The acquisition was about securing the investment. Not any devious scheme.

      Disclaimer: I work for Oracle but am not in any way associated with the Java group nor am I part of the executive/decision-making chain.

    5. Re:Java is done by s.petry · · Score: 2

      That's retarded. Oracle had (and maintains) a sizeable investment in Java and the rack servers for which Oracle is optimized for.

      The acquisition was about securing the investment. Not any devious scheme.

      Disclaimer: I work for Oracle but am not in any way associated with the Java group nor am I part of the executive/decision-making chain.

      Your point of something being retarded is aimed in the wrong direction. "Securing" would mean that they originally owned it, but they didn't. They purchased Sun and immediately started legal actions which Sun was never going to pursue because they knew they had open sourced Java. In fact in the Google vs. Oracle case numerous messages from Sun came out expressing exactly that, which is why the first Judge ruled for Google. The Judge also understood the sheer idiocy of Oracle claiming patent and copyright on things like function names and how arguments get passed to them, and all the other crap that Oracle claimed was stolen by Google.

      I still have no idea how the first decision was overturned.. oh wait.. money and Larry's personal lobby group.. nevermind.

      --

      -The wise argue that there are few absolutes, the fool argues that there are no probabilities.

  3. Someone claim (C) on something oracle depend on by Anonymous Coward · · Score: 5, Insightful

    Like libc, or whatever, or change licenses to an "Oracle Exclusion License" so stupid things like "Copyrighting APIs" get dropped and common sense rules again.

    1. Re:Someone claim (C) on something oracle depend on by TheRaven64 · · Score: 2

      The Open Group claims the copyright on the POSIX specifications. If APIs can be copyrighted and this copyright includes all implementations, then it would be problematic for all open source *NIX systems. Of course, they might decide to provide a license that's valid for everyone except Oracle (though writing such a license in a way that's GPL compatible would be very hard, so glibc might be in trouble).

      --
      I am TheRaven on Soylent News
  4. Wasn't Java open sourced? by jfdavis668 · · Score: 2

    If Oracle open sourced Java, how can they be suing anyone?

    1. Re:Wasn't Java open sourced? by Anonymous Coward · · Score: 5, Informative

      Google didn't use the open source version (OpenJDK is GPL). They reimplemented it with a more permissive license (Apache2). Oracle is saying they are not allowed to do that.

    2. Re:Wasn't Java open sourced? by Lunix+Nutcase · · Score: 2

      Because open sourcing has nothing to do with giving up copyright. Sun didn't give up their copyright when GPLing it and Orcale now holds it.

    3. Re:Wasn't Java open sourced? by Hardhead_7 · · Score: 4, Insightful

      This is why when Microsoft open sourced the new .NET framework recently, they also included a "Covenant not the Sue" document saying you were free to re-implement the .NET API with your own code. Basically, promising not to pull an Oracle. The upshot is .NET is now more free-as-in-freedom than Java. It's enough to make your head explode.

    4. Re:Wasn't Java open sourced? by jfdavis668 · · Score: 2

      Google didn't modify the source code. They didn't even use the source code. Why would they have to follow the GPL?

    5. Re:Wasn't Java open sourced? by NostalgiaForInfinity · · Score: 4, Informative

      Here is what the copyright case was about:

      The copyright phase consisted of several distinct claims of infringement: a nine-line rangeCheck function, several test files, the structure, sequence and organization of the Java Application Programming Interface (API), and the API documentation

      http://en.wikipedia.org/wiki/O....

      No matter what Google may have copied, according to Oracle's own court case and allegations, they did not create a single API by copy-and-paste, as you allege.

      The only "actual Java source code" copied is these nine lines:

      private static void rangeCheck(int arrayLen, int fromIndex, int toIndex {
                if (fromIndex > toIndex)
                          throw new IllegalArgumentException("fromIndex(" + fromIndex +
                                    ") > toIndex(" + toIndex+")");
                if (fromIndex < 0)
                          throw new ArrayIndexOutOfBoundsException(fromIndex);
                if (toIndex > arrayLen)
                          throw new ArrayIndexOutOfBoundsException(toIndex);
      }

      But, actually, these lines pretty much follow from normal Java programming conventions; whether or not Google actually copied them, they should not be covered by copyright law since they are not creative.

      So, in different words, you're a liar.

  5. Mini Sample by koan · · Score: 5, Insightful

    Of what the TPP is going to do.

    --
    "If any question why we died, Tell them because our fathers lied."
  6. Justice Department? by BenJeremy · · Score: 5, Insightful

    WTF do they have to do with this case? This isn't a criminal proceeding, it's a civil matter.

    This isn't about "protecting" Oracle (though there may be some $$$ influence involved), but rather more about protecting the copyright racket, strengthening it beyond the accepted scope.

    APIs should not ever be copyrighted. Once you start doing that, it's only a matter of time before Disney copyrights all cartoon renderings of a mouse, or Nickelback gets to copyright all formulaic/generic rock.

    Unfortunately... the Justice Department, likely at the behest of the White House, is intervening to influence copyright law and give corporations even more power. Ugh. It's like our government is pushing to see how far it can go to enslave citizens (the real, human kind, not the corporate nonsense kind) before they decide they've had enough of this shit.

    I'd be inclined to chalk this up as a "First World Problem" but clamping down on technology denies everybody equal access. This is a serious infringement of our freedoms that will have a chilling effect on the progress of technology to help people in their daily lives everywhere in the world. It's not just about Java - it's about any programming language interface.

    1. Re:Justice Department? by Richard_at_work · · Score: 2

      WTF do they have to do with this case? This isn't a criminal proceeding, it's a civil matter.

      The Supreme Court asked the government to comment, and so they did.

  7. Java API: Copyrighted, but hope for fair use! by paskie · · Score: 4, Informative

    TL;DR: US executive shares the appeals court opinion that APIs are copyrightable, but that does not mean the copyright is enforceable - there will be another court case that will be about if it's fair use to re-implement the (copyrighted) API.

    Here is maybe the most important paragraph (italics mine):

    Despite the inherently functional character of all computer code, the Copyright Act makes clear that such code can be copyrightable. Nothing about the declaring code (API declarations) at issue here materially distinguishes it from other computer code ... . Although petitioner has raised important concerns about the effects that enforcing respondent's copyright could have on software development, those concerns are better addressed through petitioner's fair-use defense, which will be considered on remand.

    The brief is quite well readable (modulo the awful scribus ui), try it!

    --
    It's not the fall that kills you. It's the sudden stop at the end. -Douglas Adams
  8. Supreme court to DOJ, Challenge Accepted by Proudrooster · · Score: 4, Funny

    DOJ: We recommend you don't take this important copyright case.
    SCOTUS: Oh really, why is that?
    DOJ: Corporate interest mostly, we are looking to create a new form of monopoly power, and Larry Ellison has some really cool Sailboats.
    SCOTUS: Thanks for your recommendation, we are looking forward to hearing this case and just added it to the docket.

  9. Re:The SCO dementors by Al+Dunsmuir · · Score: 2
    Too bad Groklaw is no longer active. Ignorance is NOT bliss.

    If you go back and read the extensive coverage of the original trial, you would discover that you are arguing for the opposite of what the original court decided.

    The decision was that the API _interface_ itself is not copyrightable, but the implementation behind that interface was. That is what open source (and any sane closed source) software project requires. The judge took the time to learn how to program Java as part of his research, and crafted a well-reasoned and documented response.

  10. A periodic formality, like adopting House rules by tepples · · Score: 2

    A pattern of Congress continually extending term lengths retroactively is not the same as a law declaring that copyrights do not expire, because the action that occurs if Congress does not act is that copyrights expire. Whereas in the latter scenario Congress has to act in order to make copyrights expire.

    Each house of Congress also has to act every two years in order to set its rules. The requirement of a periodic formality to prevent copyrights from expiring does not change the practical outcome, just as the requirement of a periodic formality to readopt House and Senate rules every two years does not keep the House and Senate from having rules.

    Nobody actually wants perpetual copyright terms, except maybe Disney.

    And the Gershwin estate. And the leadership of the Motion Picture Assocation of America (to find sources, search the web for the phrase "forever less one day"). And Dr. Seuss Enterprises, whose argument in its Eldred amicus was that an author and his heirs deserve royalties from adaptations of the author's work to media invented decades after the work's first publication.

  11. MOD PARENT UP! by tlambert · · Score: 3, Interesting

    Or Google has been resisting the NSA a little too much.

    This.

    It's pretty obvious that this is a punishment for adding encryption to Android devices, and for going to SSL for all web transactions, making it much more difficult to spy, despite administrative objections.

    The recommendation is clearly punitive because Google has pissed the executive off, and consistently opted on the side of data protection, and has disclosed many of the recently discovered OpenSSL and SSSL protocol flaws which made eavesdropping easier.