After mixed copyright win over Google, Oracle looks towards patents
Summary: The next phase of the trial will consider whether or not Google violated two patents associated with Java.
SAN FRANCISCO -- Oracle v. Google is moving full speed ahead into phase two of the trial, focusing on two charges of patent infringement associated with Java.
However, after a morning debating motions for evidence and witnesses for phase two as well as a debacle that temporarily placed jury deliberations on hold, only Oracle's lead attorney Michael Jacobs had time to deliver his 45-minute opening statement on Monday.
Earlier on Monday, the jury came to a partial verdict about charges of copyright infringement. Although the results were a mixed bag, the jury ultimately found for Oracle, finding Google guilty of copyright infringement.
However, the jury could not come to a unanimous decision about Google's fair use argument, prompting Google's lead attorney Robert Van Nest to move for an immediate mistrial for the first phase of the case. Arguments for a mistrial will be heard on Tuesday and Thursday this week as the matter needs to be resolved before damages can be determined.
Trying to ease the tension in the courtroom after the confusing verdict, Jacobs quipped, "I think you'll be pleased to know that fair use is not an issue in the patent case."
Essentially, the two patents at question here focus on the improvement of memory and performance in relation to mobile devices.
For example, one term we're bound to hear bounced around by the plaintiff and defense over the next couple of week is "symbolic reference," which Jacobs defined as a reference that identifies data by name other than the numeric memory location of the data, and that is resolved dynamically rather than statically.
The point of making symbolic references the heart of Oracle's case is because Oracle argues that Android relies on symbolic reference resolution to run faster.
In a college lecture-like fashion, Jacobs explained the Java platform components stack to the jury, extending from the Java application source code, down to the Java computer, Java byte code, Java virtual machine, and computing device. He then compared that to Android's platform components, highlighting the identical process for the Java application source code to the Java compiler.
But even more pointedly, Jacobs outlined four faults with Google's case in this half of the trial, positing that Google has no excuses this time around:
- Patented inventions are not free
- Google has no fair use defense
- The truth is in Google's own source code
- Google needs a license to use patents
Furthermore, it's important to note that Oracle is not only suing Google for patent infringement for use of these patents in-house, but also for induced infringement, which would hold Google liable for infringement by someone else.
In this case, that refers to the developers and mobile OEMs because Google made Android publicly available for these ecosystem partners to download.
Related:
- Oracle CFO: We never wanted this lawsuit with Google
- Oracle: Google wanted easy route to Android revenue with Java
- Google: Sun, Oracle couldn’t compete with Android
- Trial: Page, Rubin and Schmidt: How did they do?
- Decisions about Java use debated in Oracle-Google trial
Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.
Talkback
Oracle will lose the patent part!
The copyright will be won by google as soon as the judge rules the API are not copyrightable. Then the fair use question is moot and Oracle goes home tail between the legs!
*sigh* I am starting to wonder about you, LG.
One way to find out
Yes, nothing has been decided
Google's Sunny Day
Which, according to the reports I've seen, irritated the Judge because BSF had said they were going to take statutory damages and now that things aren't going so well, they are hoping no one remembers what they said. The Judge remembers.
So, I have looked at the patents in question.
Yeah.
Google took all the Java APIs and one by one, just essentially paraphrased them and gave them some different names, except for one or two they missed and forgot to paraphrase, which then slipped through as character-for-character copies. The result was a recognizable ripoff copy of the whole Java API structure and content, with the kickers of being incompatible with Java (forking the code - embrace and extinguish, anyone?), and promoted as their own "clean room" unique code.
That's what Oracle's case is, if I understand it. And, frankly, with the emails introduced at trial, I think it's pretty clear that that's just what happened. And the jury apparently buys that argument.
What the final outcome will be we'll all have to see, but I wouldn't assume that Android is free and clear now or even going to survive commercially, because depending on the final outcome, anyone who uses it in a product may either have to pay royalties to Oracle, or be liable for infringement as well.
well...
Really though we can only really guess at what their agreement even entailed. . .and I don't like guessing.
unlikely
Developer?
Google took a porition of the Java APIs and copied them EXACTLY line by line. That's the point of an API.
But, an API is only a specification. What's also critical is the implementation of the APIs. The implementation are the instructions that tell the computer how to perform the functionality. And Google did the implementation work, a so called "Clean room implementation."
A few of the implementation details were copied, but relatively speaking, it's probably less than 0.001% of the entire code base (millions of lines of code).
Both the API and implementation are important, it's a tough call IMO
.
What dave-1212 said... He's right!
APIs have been this way for years. Even Ellison's early efforts on Oracle DB were based on the work of a different person with algorithmic expertise on relational databases. If APIs (which encapsulate algorithms) were copyright-able back then, he might not even have a company today.
What Oracle was proposing is akin to copyrighting the title of every chapter in a book and then claiming someone ripped you off when they used the same chapter titles, but the content within is different from yours.
And as far as the 9 lines of "exact code". I'm a little skeptical of that as well. Sometimes there are very few solutions to a particular problem, and because of the way developers are trained, we all tend to break the problems apart in a similar way as we devise solutions. For example.. If you were to get a group of developers together, and asked them each to write an API to swap a couple numbers or sort a list of things, I'd wager a lot of them would come up with nearly identical solutions.
To say APIs are copyright-able at this point would have dire consequences. The depth of how much and how often this is already going on is VERY deep and reaches FAR beyond this little skirmish. Nearly every app out there would be subject to copyright violation. In fact, I'd be brave enough to say just about all of them would be. Including things in Oracle's flagship products. Makes me wonder if the lawyers examined the depth of such a ruling would reach. Luckily, the judge seems to be a very intelligent guy. I suspect he will rule in such a way that makes the US compatible with the EU ruling (i.e. they are NOT copyright-able)
Oracle won something?
Yeah.. that confused me too..
I think the confusion was set in by Google requesting a mistrial. I guess the notion that the obvious, less positive sounding move hiding the strategic, winning move downstream got a little lost somewhere.
another thing we need to get rid of.
Judge to Boies: "This Borders on the Riddiculous"! haha...
So the the only thing the Famed Oracle Attorney could think to ask for was about "Infringing Profits". To which the Judge said:
""Oracle: Separate damage calculation.
Judge: Do you want all their profits?
Oracle: No, Your Honor.
Judge: This borders on the ridiculous. Now you are changing your tune (adding to the agreed-upon statutory damages). Based on 9 lines of copying out of 15 million? That would be a big, big stretch.
Oracle: If we were, as a matter of law, able to seek disgorgement on question 1.
Google: mistrial briefing tomorrow...
Judge: Zero finding of liability so far. We will use the same briefing schedule. Brief tomorrow, responses by Thursday.""
Not sounding too good for Oracle and as for Patents it only gets worse.... not better. Google it seems.... has already coded around on patent and have the witnesses and evidence to prove they're non-infringing on the other!
Happy Days lie ahead for Google!!! :DDD ....and looks like Oracle will be facing another Shareholder Lawsuit (like that in reference to Defrauding US Department of GSA contracts) for now not being even remotely able to justify their Purchase of Sun!!! haha... this Oracle vs Google nonsense gets funnier every day!!!
Frankly, I don't want them to even have a ham sandwich.
Not Over Yet
Java is a security nightmare and the sooner Oracle manage to kill it through their own stupidity then it's one less attack vector we all have to worry about.
Wow, the headline is misleading, even by ZDNet standards
The real question is whether the judge is going to rule that the SSO of the APIs is copyrightable. Regardless of what he rules, it will be appealed all the way to the SCOTUS, with ping-pong rulings along the way, I'm sure.
If you really want to know who's winning the case, just ask the people who are in the courtroom. Whose lawyers are laughing and relaxed? (Hint: Google's) Whose lawyers have long faces and are feeling stress? (Hint: Oracle's).
Unless Oracle just gives up and goes back home, this issue won't be settled for YEARS. If you want to print bold headlines let's actually have something of substance to report.
-MC
ZDNet needs clicks
Welcome to the Ziff Davis Network, sunshine.
RE: Welcome to the Ziff Davis Network, sunshine.
The last line should read:
[i]Welcome to the Ziff Davis Network, sunshine. [u]Part of CBS Interactive, a CBS company.[/u][/i]
Now, the tabloid headline makes sense.