As a legal strategy, that's not a problem, and in fact it's what lawyers are supposed to do: make the best possible arguments they can in any case they are a part of. It should not be interpreted as a case of corporate schizophrenia -- it's just the lawyers doing their jobs.
This can lead to contradictory positions if multiple cases are going on at the same time. That's fine. The legal system is designed around the assumption that this will happen.
If a company is filling a role and 2 similar applicants get matching offers and one accepts the first and the other negotiates I wouldn’t expect the company to go back to the first person and offer him more to bring them to parity.
However, I think that Oracle would argue that there is no contradiction.
In the case now before the US Supreme Court, Oracle argues that software copyrights do extend to the interface/API and that reimplementing the interface does not constitute fair use.
With regard to Amazon's API, Oracle argues that the license grants them permission to reimplement the interface.
This argument doesn't rely on disputing copyrightability of APIs or on fair use. It simply says that copyright holders get to decide whether or not reimplementation is permitted.
Fact in this matter is that the license for the Amazon API does allow the API to be copied. But Oracle did and does not follow the license, because the required attribution is missing. They are therefor not protected by the license. It is like using an illegal copy of Windows and claiming you had the right to use it under the license for the small omission of not having paid for it.
Even if the change the code to include attribution they are still liable for significant damages to Amazon for the period preceding the correction. Amazon can claim to them the attribution is a very significant part of the license agreement: It would deter competitors having to advertise Amazon and tell their customers that their product was actually invented by someone having a competing product.
Google can claim their fair use was actually already common practice, as most of us thought. Even Oracle itself assumed and acted on that assumption that copying APIs was fair use / not copyrightable and did not require following a license agreement, as they did not. Worst case for Google is that they should not have to pay significant damages for something they and others would see as a common mistake and Oracle's reversal complying with the Amazon license is proof that there was no established judicial practice to follow.
So Oracle is in a pickle: Either they claim copying the Amazon API was fair-use, or APIs are not copyrightable and they lose the case against Google. Or they claim that the license of Amazon allowed for copying of the API and they violated that license. The harder they push Google in the later case the bigger the risk Amazon will claim their share of Oracle's pie in return. Better get the spreadsheets out.
Also, the potential damages in these two cases are presumably very different. Google built an entire industry on top of Android whilst Oracle is limping along with a me-too cloud offering, some tiny part of which uses Amazon's API. So I think Oracle would gladly take the risk of losing that case if they can win the other one.
Oracle's case with Google will likely set precedent. If the side they're arguing for is going to hurt another side of their business by removing their legal argument, why are they fighting?
Wall garden, vendor lock, license, and litigate for every LOC. Make customers pay for technical debt by dumping more exotic spaghetti code.
Larry Ellison's way of doing business is about him and what he receives at the bottom line. The customer is an after fact in the sales funnel. A resource that needs to be milked as a proper cash cow.
Larry Ellison is as a evil as the offspring of Joffrey and Cersei Lannister could be.
What would be a better option (IMO) then just not enforcing your rights would be to get an nominal fee from the entities you like and in return grant them a favourable license.
(Not a lawyer, go ask your own lawyer if you want specific legal advice)
Implied license generally applies to situations where a reasonable person would believe they have a license even though one has not been explicitly granted. For example, if I pay you for the use of a photograph you took, even without a written contract granting me ownership or a license, a court would hold that I have an implied license.
Failing to defend IP can enable a laches defense, but that's quite different from an implied license.
Off the top of my head (Which may not be a great example but the first one that sprung to mind) Field v. Google.
> The Field court expanded the earlier doctrine to hold that implied license arises "where the copyright holder knows of the use and encourages it." Applying this two-pronged knowledge and encouragement test to the Field facts, the court found that the website owner was aware of the robots exclusion protocol mechanisms for communicating with the Googlebot, and that by not using them, he essentially encouraged the Googlebot to index his content.
> Field created a robots.txt file for his site and set the permissions within this file to allow all robots to visit and index all of the pages on the site. [...] Field created the robots.txt file because he wanted search engines to visit his site and include the site within their search results.
and (regarding meta-tags):
> Field concedes he was aware of these industry standard mechanisms, and knew that the presence of a “no archive” meta-tag on the pages of his Web site would have informed Google not to display “Cached” links to his pages. Despite this knowledge, Field chose not to include the no-archive meta-tag on the pages of his site. He did so, knowing that Google would interpret the absence of the meta-tag as permission to allow access to the pages via “Cached” links. Thus, with knowledge of how Google would use the copyrighted works he placed on those pages, and with knowledge that he could prevent such use, Field instead made a conscious decision to permit it. His conduct is reasonably interpreted as the grant of a license to Google for that use.
Field was trying to get his site indexed and cached (so that he could sue Google), and Google indexed and cached it. The court ruled that Field's actions were active encouragement and implied the grant of a license to do the thing he wanted Google to do.
Field didn't fail to defend his copyright. He put the files up in January, filed copyrights with the Copyright office, waited for them to be indexed and cached, and sued Google in April. He protected his copyright about as vigorously as you can with the available legal tools.
The question of implied license in this case is whether putting something on the internet without taking steps to stop search engines from indexing+caching it constitutes an implied license. The court ruled it did, but it relied in part on Field taking specific actions to allow it (such as the robots.txt file), so it's not entirely clear that in a different case they would rule the same way. If someone put up a site with just a plain text file without HTML tags and no robots.txt file maybe the court would rule that there was not an implied license there, I don't know. They also took into consideration that there are well-known industry standard ways of preventing Google and others from indexing and caching your site, so maybe they would consider that alone sufficient to rule that there's an implied license if you don't follow the industry standards.
In any case, Field v. Google has little-to-nothing to do with failing to defend a copyright.
For an example, lets just say for the sake of argument Amazon did decide to defend their API from Oracle's implementation and take action. Oracle could use as a defence (But prob not their only line of defense) that "That Internet Archive, LeoFS, Riak CS, Minio, cloudian and others all have S3-Like API's. Amazon must be aware that these products exist and by allowing such products to exist without defending their rights (what ever they are) to the API they allowed an implied license for the API to be created thus Oracle's implementation is just another implementation of that implied license.
A "Workaround" to such could be taking lets say Internet Archive to one side and saying "Hey, we like what you do, but we have a copyright on that API you are using. Pay us $1 and we will grant you a license to use that API.".
Personally I dislike the idea of enforcing copyrights on an API (Sure, enforce them code behind that API, unless you wish to give that away) and feel that the products using them should stand on their own.
They took an open source piece of software (the SDK) and made a derivative work (the backend the SDK uses). That indeed is copying and is essentially identical to what Google did. But there's no copyright violation here because Amazon explicitly granted everyone the right to do that by releasing the SDK under the Apache license.
Google acknowledge's this and isn't bothering to try and argue otherwise. They aren't presenting openjdk's license as a defense to infringement. Oracle for whatever reason is ignoring that issue in their statement to ars technica.
https://github.com/oracle/oci-ruby-sdk/blob/master/LICENSE.t...
I fail to see how it substantively differs.
While that is indeed the difference between using the API and implementing the API, I was under the impression that the Google-Oracle dispute was about the API itself, not the implementation. In the restaurant analogy, that would be the menu ("hash browns"), not the cook ("the customer wants hash browns, what are you going to do about it?").
When Oracle sued Google, the case originally had both copyright claims and patent claims.
Is Amazon's API patented? If not, then if Amazon were to sue Oracle it would be only a copyright case, not a patent and copyright case.
Normally, appeals from most cases, including copyright cases, go to the appeals court for the same Circuit that the district court that heard the case is in, which would be the 9th Circuit Court of Appeals (9th CA) in the case of Oracle vs. Google, and most likely also in an Amazon vs. Oracle.
However, if the case includes patent claims the appeal goes to the Court of Appeals for the Federal Circuit (CAFC) instead of going to the CA for the circuit containing the district court.
If the case includes both patent claims and non-patent claims, the whole thing goes to CAFC which decides both the patent issues and the non-patent issues.
On patent issues, CAFC decisions are precedent for all district courts.
On those issues that get dragged along when a mixed case ends up at CAFC because it includes patent issues, CAFC is supposed to follow the precedent of the appeals court for the Circuit the case came from.
A lot of people believe that CAFC totally botched following 9th CA precedent in the Google case.
If Amazon sues Oracle but doesn't have a patent claim included to force appeals to CAFC, the appeal will end up at the 9th CA, which presumably will do a better job of following 9th CA precedent than CAFC did, and so rule against the API copyright (and so in favor of Oracle).
Until the Supreme Court actually gets around to settling this matter, we are in an inconsistent state in the 9th Circuit.
1. As far as specifically Google and Oracle are concerned, Oracle's API is copyrighted and what Google did infringes. CAFC said so when it handled the appeal, and that is binding precedent to the lower courts in any further proceeding between those two litigants.
2. For API copyright claims that are not between Oracle and Google and are not accompanied by a patent claim, the law is still what it was before the Google case.
3. For API copyright claims that are not between Oracle and Google but are accompanied by a patent claim, and so will be appealed through CAFC instead of 9th CA, presumably they will end up with the same wrong outcome as Oracle vs. Google.
This is common any more in legal battles. Where a company will take a position in one case that is completely contrary to its position in a different legal case
> Did Oracle infringe Amazon's copyright here? Ars Technica contacted Oracle to ask them if they had a license to copy Amazon's S3 API. An Oracle spokeswoman said that the S3 API was licensed under an Apache 2.0 license. She pointed us to the Amazon SDK for Java, which does indeed come with an Apache 2.0 license.
> However, the Amazon SDK is code that uses the S3 API, not code that implements it—the difference between a customer who orders hash browns and the Waffle House cook who interprets the orders.
While I'm not a lawyer and didn't study the Google case in that much detail, I don't see how they can claim that their own Java APIs can be copyrighted, and then defending their copying of Amazon's API on the grounds that an SDK using it is open source. I would think they could just look at the documentation, and skip the SDK altogether. :)