Skip to main content

Google v. Oracle

 


Regular readers of this blog may remember that I have on earlier occasion covered the very slow march through the court system of a monster of an intellectual property case, the dispute over the legality of Google's use of Java interfaces in its Android coding.

But to review: years ago Oracle bought Sun, the company whose engineers had created the Java programming language, on which various APIs (application programming interfaces) have in turn been built. 

The dispute is a matter of copyright, not of patents. And early on in this litigation, Google took the position that there is no copyrightable interest in APIs. The Federal Circuit held against that view, and remanded to the trial courts for consideration of whether Google use is "fair use" under copyright doctrine, or unfair and thus infringing use. The Supreme Court, in 2015, declined to hear an appeal from the Federal Circuit, so Google resigned itself to fighting that battle in the trenches of a trial. 

The jury held that it WAS a fair use. This time, then, it was Oracle's turn to pursue appeals, claiming that the jury's decision is not defensible even within the rather broad discretion that is supposed to be given to juries. It has won on that contention in the appellate courts. So far. But the matter is now before the Supreme Court which, in its first week back (as one of the first matters it heard after the death of the notorious RBG) heard oral arguments on this matter on October 9, 2020.

It would be an interesting exercise to research the following:

1) What were RBG's views on copyright in general and on this case as of 2015 in particular,

2) How do those views contrast with the views, as we might glean them from academic writings or opinions, of ACB? 

But since ACB wasn't on the court for the arguments, it is unlikely she'll cast a vote on this one.

There are two ways Google can win: it could convince the Justices to reverse the 2015 decision of the Federal Circuit that they refused to hear back then, and hold at last that APIs are not copyrightable. Or it can convince them to let the jury's verdict stand, that even though APIs are copyrightable, their use of these APIs is a fair use. 

Stephen Breyer made a fascinating observation. He compared the Java API to the QWERTY keyboard system. There are other ways to lay out a keyboard. But for generations typists and now computer users and the buyers of smartphones have been using QWERTY. So QWERTY has come to seem indispensable. From a micro point of view it IS indispensable. It would to give some person or entity a striking windfall to let then now copyright the QWERTY layout, even if there were some historic justification for doing so.

Breyer, then, seems inclined to give the win to Google, though such inferences from questions at oral argument cannot be counted on.  

We will wait on the outcome of this one.  



Comments

Popular posts from this blog

A Story About Coleridge

This is a quote from a memoir by Dorothy Wordsworth, reflecting on a trip she took with two famous poets, her brother, William Wordsworth, and their similarly gifted companion, Samuel Taylor Coleridge.   We sat upon a bench, placed for the sake of one of these views, whence we looked down upon the waterfall, and over the open country ... A lady and gentleman, more expeditious tourists than ourselves, came to the spot; they left us at the seat, and we found them again at another station above the Falls. Coleridge, who is always good-natured enough to enter into conversation with anybody whom he meets in his way, began to talk with the gentleman, who observed that it was a majestic waterfall. Coleridge was delighted with the accuracy of the epithet, particularly as he had been settling in his own mind the precise meaning of the words grand, majestic, sublime, etc., and had discussed the subject with William at some length the day before. “Yes, sir,” says Coleridge, “it is a majesti

Five Lessons from the Allegory of the Cave

  Please correct me if there are others. But it seems to be there are five lessons the reader is meant to draw from the story about the cave.   First, Plato  is working to devalue what we would call empiricism. He is saying that keeping track of the shadows on the cave wall, trying to make sense of what you see there, will NOT get you to wisdom. Second, Plato is contending that reality comes in levels. The shadows on the wall are illusions. The solid objects being passed around behind my back are more real than their shadows are. BUT … the world outside the the cave is more real than that — and the sun by which that world is illuminated is the top of the hierarchy. So there isn’t a binary choice of real/unreal. There are levels. Third, he equates realness with knowability.  I  only have opinions about the shadows. Could I turn around, I could have at least the glimmerings of knowledge. Could I get outside the cave, I would really Know. Fourth, the parable assigns a task to philosophers

Searle: The Chinese Room

John Searle has become the object of accusations of improper conduct. These accusations even have some people in the world of academic philosophy saying that instructors in that world should try to avoid teaching Searle's views. That is an odd contention, and has given rise to heated exchanges in certain corners of the blogosphere.  At Leiter Reports, I encountered a comment from someone describing himself as "grad student drop out." GSDO said: " This is a side question (and not at all an attempt to answer the question BL posed): How important is John Searle's work? Are people still working on speech act theory or is that just another dead end in the history of 20th century philosophy? My impression is that his reputation is somewhat inflated from all of his speaking engagements and NYRoB reviews. The Chinese room argument is a classic, but is there much more to his work than that?" I took it upon myself to answer that on LR. But here I'll tak