6 ms·
I would imagine if the ruling went the other way, IBM might want to talk to all the BIOS companies. Luckily, that didn't happen.
by protomyth 6y ago
I would imagine if the ruling went the other way, IBM might want to talk to all the BIOS companies. Luckily, that didn't happen.
- oblio 6y agoIBM would probably want to talk to 99% of computing companies out there, not just BIOS companies :-)
- bryanlarsen 6y agoIncluding Oracle, since their copying of IBM's SQL API is what the whole company is based on.
- jcranmer 6y agoAnd Oracle is now copying AWS's API to try to enter the cloud market. (This was explicitly brought up in one of the amici briefs).
- jpdb 6y agoAre you referring to the S3 API? I believe the S3 API is explicitly licensed under Apache. Disclaimer: I was previously employed by Amazon and currently Google. Opinions are my own, I'm not a lawyer, etc.
- jcranmer 6y agoAnd OpenJDK is GPLv2 with a classpath exception. So why is Google unable to use Java's API here while Oracle able to use Amazon's API?
- tephra 6y agoIIRC (this case has been going on for way to long) they didn't cope the GPLed version of the code (oracle/sun had another proprietary version).
- jcranmer 6y agoSo the original case had claims against copying more of the original Sun JVM code than just the API--the entire furor over "rangeCheck" was a key part of the original case. By the first appeal, this was reduced to a de minimis claim of copyright and Oracle no longer pursued claims of copyright on anything but the API. My understanding is that all of the APIs in question are shared between the (now-Oracle) JVM and the OpenJDK implementation. (Indeed, I think the actual implementation of the Java code in question is the same between the closed and open source versions, it's only the JVM itself that differs.)
- fX0rObfoMN4 6y agoI thought this case is from back when Android was using Apache Harmony?
- kaba0 6y agoBecause it wasn’t GPLv2 at the time, and Sun explicitly disallowed mobile use?
- iam-TJ 6y agoGoogle used the Apache Harmony version as the basis for Android (Until Nougat). Some of the argument was over whether the Apache licence inherited by Google from Harmony was valid, or whether Harmony itself was in breach of copyright (and therefore had no valid licence Google could use). Once the courts decided APIs are copyrightable the argument switched to whether Google's was Fair-Use, with a jury saying it was, federal appeals court saying no, and thus it ended up at the Supreme court. Here's a Groklaw [0] copy of an early (April 2012) Oracle argument asking for Jury instructions around the licence topic that explains it well: "As made clear by Apache itself, Apache never had a license from Sun or Oracle for Harmony. Apache had no rights to Java technology that it could give to Google" [0] http://groklaw.net/pdf3/OraGoogle-959.pdf http://groklaw.net/pdf3/OraGoogle-959.pdf
- gpm 6y agoIIRC the API is probably licensed under the Apache license (by virtue of client libraries being licensed, not intentionally) but Oracle isn't complying with the requirements of the license, so that would have been more or less irrelevant.
- mtgx 6y agoIncluding Oracle... Good thing the SC saved Oracle from its own stupidity.
- philjohn 6y agoand Amazon could talk to Oracle who "borrwed" the S3 API for their cloud storage.
- derekdb 6y agoS3 explicitly changed their license to allow copying the S3 API. I forget the year, ~2010? I was working an S3 at the time and it was a strongly debated decision. Google’s initial launch of their cloud storage copied not just the S3 API, but also the error codes.
- winwhiz 6y agoI think the point is that if this case had gone the other way this kind of open licensing would happen a lot less. Companies would be obliged to enforce API copyright to protect themselves from loss of copyright (share holder value)