Hacker News new | past | comments | ask | show | jobs | submit login

I wouldn't say that Oracle won, as I don't believe Google has given up nor do I believe they have exhausted the legal tactics/maneuvers available to them. I fully believe this case will end up in front of the supreme court, as fundamentally this is a 1st amendment issue: do you have the right to say what other people are saying? (that's effectively what re-implementing APIs is).

I believe the 1st amendment provides for this.

My hope is that Google does not settle the case with Oracle, as I'm sure this case shows up at the top of their legal budget.




Didn't the Supreme Court already turn down the case? Or is there some other avenue of appeal that's yet to be decided?


The Supreme Court turned down the opportunity to hear Google's arguments that APIs are not protectable by copyright. Turns out, they are, according to the Supreme Court's implicit affirmation of the Federal Circuit's decision.

But "copyright protection can extend to APIs" is all that the courts' decisions amount to so far. As the article says, the case has been remanded back to the district court, which will be trying to answer the question, "Given that APIs are not inherently unprotected, are Google's actions in this case punishable, or did they amount to fair use?"

Here's how that's gonna go:

Allsup is almost definitely going to find it fair use, and (with a little less certainty) the Federal Circuit is going to reverse that decision when Oracle appeals it. At that point, we're back to waiting to see if the Supreme Court will hear Google's arguments, but this time their argument will be that, APIs being unprotected or not, their actions were essentially no different than the ones the Supreme Court determined were defensible in Lexmark v. Static Control in pursuit of interoperability. First Amendment probably won't actually factor in to this.

This is assuming that neither Oracle nor Google capitulates before it makes it that far. Oracle probably won't. Google might.


> The Supreme Court turned down the opportunity to hear Google's arguments that APIs are not protectable by copyright. Turns out, they are, according to the Supreme Court's affirmation the Federal Circuit's decision.

That's not an affirmation. An affirmation would be if the Supreme Court took the case, and agreed with the Federal Court. This is "we're not going to bother", which leaves the decision as good precedent in that Federal court (but not in any other).


Yes, it's always worth reiterating that the Federal Circuit's decision is precedent nowhere, not even in the Ninth Circuit where the district court is located.

This is one of the reasons why the FSF, for instance, sided with Google but still urged the Supreme Court not to take the case. They said the GPLed OpenJDK already gave Google the right to the APIs in question, but also noted that there wasn't precedent any court needed to defer to for the Supreme Court to address anyways.


I originally wrote "implicit affirmation", but edited it out. Hope you didn't downvote the entire comment because of that.


There's nothing to infer from a denial of a petition for certiorari, and there's certainly no precedential weight to it. And there's actually precedential weight to the fact that a denial has none :)

It is true that they implicitly affirmed the decision in this particular case, but as to the larger question of copyrightability of APIs, as I mention above, the reasoning for denial could just as easily be they didn't think this case would be a good test for that question for whatever reason.

Wikipedia cites a few cases in which the Supreme Court has explicitly stated this in [1] (see paragraph starting with "Conversely...")

[1] https://en.wikipedia.org/wiki/Certiorari#Federal_courts


Nope, I didn't downvote you. I think the rest of what you wrote is pretty accurate. I also don't think Google will capitulate. I think they're moving to OpenJDK to limit their downside, but I think they're doing it with the idea of fighting it out.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: