Earlier quoted context omitted.
> say, a new battery It would be more about copying the batteries terminal structure, such that you could build products compatible with the battery or a battery compatible with the products. It snot about copying the battery, its about supporting interoperability. That's what is at risk here. Sixty seven different kinds of outlets, or arbitrarily expensive ones where the "design" itself is licesned, instead of the c…
> its about supporting interoperability I think this is a very important point. I haven't read all of the briefs in this case, or looked at the arguments presented at the hearing, so I don't know if Google's lawyers stressed this point, but they sure ought to.
Google’s Supreme Court faceoff with Oracle was a disaster for Google
461–470 of 771 posts
Re: Google’s Supreme Court faceoff with Oracle was a disaster for Google
#462Earlier quoted context omitted.
If I'd publish a cookbook with the same chapters and recipe names as a different cookbook, but every recipe my own creation from scratch; I wouldn't consider that copyright infringement.
Perhaps it shouldn't, but under current law it probably would be. Justice Roberts asked a very similar question during the hearing: Roberts: Let's say someone copies the headings in your brief and they copy the organization in your brief, which sections you put first and how you organize them. Would your argument say that's perfectly fine so long as they write their own text? Google's lawyer didn't really have a grea…
Re: Google’s Supreme Court faceoff with Oracle was a disaster for Google
#463Re: Google’s Supreme Court faceoff with Oracle was a disaster for Google
#464Earlier quoted context omitted.
When I learned that Java is open source, I had assumed that it was free . I guess I was wrong.
There's open source and really open source, it seems. Just wondering if the ruling will put a bomb under the Java edifice? Maybe it will even pave the way for Kotlin to become the dominant JVM language. One can only dream.
This is why the FOSS licenses enshrine Compilation, modification and redistribution also.
Re: Google’s Supreme Court faceoff with Oracle was a disaster for Google
#465I'm not sure why so many people here seem to be surprised by this, I got the exact same impression from the hearing. The problem for Google on the copyrightability front is that "compilations" of non-copyrightable items can be copyrightable even if the underlying items themselves are not, if the "selection, coordination, or arrangement" of those items involves sufficient creativity to be considered an "original work…
I wouldn’t be surprised if Oracle wins on copyright (I think it is almost impossible for Google to count to 5 on their merger doctrine argument) but I disagree that fair use is a long shot. The justices that brought up the case’s procedural history were all unanimously skeptical that the Federal Circuit correctly set aside the fair use verdict in favor of Google. I think the most likely outcome of this case (especial…
I wonder if they win on that front if the Court will be able to dodge the question of API copyrightability in general.
Re: Google’s Supreme Court faceoff with Oracle was a disaster for Google
#466Earlier quoted context omitted.
You’re misunderstanding your cookie analogy. You can’t copyright a single recipe that contains components of other recipes, but if you had written a book titled “My grandmas chocolate chip cookies from scratch”, where the first recipe is for homemade chocolate chips, the second is for how to grind your own flour for dough, and the third is for combining the previous two into a cookie, then yeah you can copyright that…
> You can’t copyright a single recipe that contains components of other recipes, but if you had written a book titled “My grandmas chocolate chip cookies from scratch”, where the first recipe is for homemade chocolate chips, the second is for how to grind your own flour for dough, and the third is for combining the previous two into a cookie, then yeah you can copyright that particular set of recipes. Suppose I want…
Re: Google’s Supreme Court faceoff with Oracle was a disaster for Google
#467Earlier quoted context omitted.
Sure- but then you have to be careful defining labels. Trying to peg a generic one dimensional (left-right) or even two dimensional (social/fiscal) political position on justices is difficult, even with loosely defined labels/ categories. It's much easier to look at justices relative position/ rank on a per-topic basis. Alternatively, and less useful to the general public, but very useful to SCOTUS junkies, is lookin…
scotusblog is biased because they have/had a working relationship with Google.
But they are still an excellent source, and are about as good as it gets compared to most (supposed) non-partisan media these days.
Fwiw, I also believe their bias to be almost entirely unintentional, which is way more than can be said for most sites. For topical seminars, where authors might actually argue for a side, they do a decent job of getting various opinions from multiple sources, even if it's not always exactly balanced 50/50.
And they disclose all cases in which someone might be involved.
Like anything else, you still need to consider the source when reading it.
Re: Google’s Supreme Court faceoff with Oracle was a disaster for Google
#468Earlier quoted context omitted.
I agree. Personally, I espouse the "copyright should not exist at all" viewpoint. However, I think in the current legal framework, APIs are clearly copyrightable. However, re-implementing the APIs should obviously be allowed under fair use. Remember that copyright exists solely for the purposes of increasing the production of otherwise-easily-copyable works that take time to create but then are "worthless" (i.e. the…
> copyright should not exist at all Copyright is not just about software. Imagine a world in which you write a novel, let's call it Harry Potter, and publish it. And then I see people liking it, so I publish it too, but I can sell it cheaper because I don't have to recoup the costs of having written it. Or imagine you write and record a song, let's call it Revolution. A shoe company can use that exact recording in an…
Re: Google’s Supreme Court faceoff with Oracle was a disaster for Google
#469Earlier quoted context omitted.
Having read multiple perspectives, some pro-Google and some pro-Oracle, I cannot reconcile this sort of argument with the Baker v. Selden precedent. [1] Perhaps my understanding of APIs is different because I'm an engineer and not a lawyer, but how is this not an open and shut case? The cookbook analogy is not applicable for the same reason one could not apply it in Baker , accounting methods are not of themselves co…
The Google v. Oracle argument hinges on Structure, Sequence, and Organization[1]. Things like the actual package structure arguably involve creative decisionmaking, and are not strictly analogous to something like accounting methods. For example, even if the idea of a max() function that takes two integers and returns the larger of the two is not copyrightable, the specific name "java.lang.Math.max()" might still be.…
See my other reply down thread, but my own reading of Baker seems to indicate this specifically is not a factor. 37 packages vs 1 method should make no difference. Copying one ledger template or copying hundreds is not a violation of copyright in the same way, because copyrights don't extend to methods of practice.
I'll have to read up on the SSO stuff as it appears there are more relevant & recent precedent cases there.
Re: Google’s Supreme Court faceoff with Oracle was a disaster for Google
#470Earlier quoted context omitted.
Having read multiple perspectives, some pro-Google and some pro-Oracle, I cannot reconcile this sort of argument with the Baker v. Selden precedent. [1] Perhaps my understanding of APIs is different because I'm an engineer and not a lawyer, but how is this not an open and shut case? The cookbook analogy is not applicable for the same reason one could not apply it in Baker , accounting methods are not of themselves co…
I'm not going to argue whether I think APIs should be copyrightable, but I believe creating a good API is a work of creative design, and is artistic I design an API for graphical coding and spend significant creative energy choosing the right words, calling conventions, result types to not only make something intuitive, but emotionally pleasurable to code with Sometimes I'll spend days writing out possible forms of t…
But that's not what it's about. Lots of things are a work of creative design but not copyrightable. Like a recipe for chocolate chip cookies.