decoration decoration
Stories

GROKLAW
When you want to know more...
decoration
For layout only
Home
Archives
Site Map
Search
About Groklaw
Awards
Legal Research
Timelines
ApplevSamsung
ApplevSamsung p.2
ArchiveExplorer
Autozone
Bilski
Cases
Cast: Lawyers
Comes v. MS
Contracts/Documents
Courts
DRM
Gordon v MS
GPL
Grokdoc
HTML How To
IPI v RH
IV v. Google
Legal Docs
Lodsys
MS Litigations
MSvB&N
News Picks
Novell v. MS
Novell-MS Deal
ODF/OOXML
OOXML Appeals
OraclevGoogle
Patents
ProjectMonterey
Psystar
Quote Database
Red Hat v SCO
Salus Book
SCEA v Hotz
SCO Appeals
SCO Bankruptcy
SCO Financials
SCO Overview
SCO v IBM
SCO v Novell
SCO:Soup2Nuts
SCOsource
Sean Daly
Software Patents
Switch to Linux
Transcripts
Unix Books

Gear

Groklaw Gear

Click here to send an email to the editor of this weblog.


You won't find me on Facebook


Donate

Donate Paypal


No Legal Advice

The information on Groklaw is not intended to constitute legal advice. While Mark is a lawyer and he has asked other lawyers and law students to contribute articles, all of these articles are offered to help educate, not to provide specific legal advice. They are not your lawyers.

Here's Groklaw's comments policy.


What's New

STORIES
No new stories

COMMENTS last 48 hrs
No new comments


Sponsors

Hosting:
hosted by ibiblio

On servers donated to ibiblio by AMD.

Webmaster
Judge is literally prejeducing Google by intending to tell the jury SSO is copyrightable | 394 comments | Create New Account
Comments belong to whoever posts them. Please notify us of inappropriate comments.
Judge is literally prejeducing Google by intending to tell the jury SSO is copyrightable
Authored by: Anonymous on Thursday, April 26 2012 @ 08:09 AM EDT
It not prejudice, SSO is a copyrightable component of a literary work,
particularly so in the case of compilations.


This is referred to as 'database' copyright.

The problem is that you have to copy the whole SSO, not just a little tiny bit
of it.

[ Reply to This | Parent | # ]

Judge is literally prejeducing Google by intending to tell the jury SSO is copyrightable
Authored by: Oliver on Thursday, April 26 2012 @ 08:56 AM EDT
Not at all. He is doing it to save time in the appeals process:
Judge: Reserving on the issue of whether SSO is a copyrightable issue. That way, it would be easy for the court of appeals to reverse without a new trial.
The point is that the jury shouldn't waste time trying to work out if it is copyrightable, nor should they be confused on that point, so they have to assume that it is. Then they can fairly judge the remaining defences that Google put forward. It also means that if the judge decides that it isn't copyrightable, and the appeals court disagrees then they don't need a new trial as this one has already progressed on the assumption that they are. I think that the judge intends to rule that they are not copyrightable (fortunately) and then it will go to appeal. What we might not end up with is a second trial, simply because of this instruction to assume that it is copyrightable.

[ Reply to This | Parent | # ]

And what about the damages phase?
Authored by: s65_sean on Thursday, April 26 2012 @ 09:56 AM EDT
If the jury does find that Google violated the SSO of the APIs based on the
judge telling them that the SSOs are protected by copyright, then the judge
rules later that the SSOs are not protected by copyright, will that be before or
after the damages phase of the trial?

Could the jury award higher damages for both copyright and patent infringement
on the basis of their understanding that "Big Bad Google" violated
poor little Oracle's copyrights and patents, when in fact ther was no copyright
to violate?

What I mean is, could the jury end up awarding damages for patent infringement
in an amount that be higher than it would have otherwise been because the jury
is biased against Google unfairly by the judge telling them that the SSOs are
protected when he later rules in fact that they are not?

[ Reply to This | Parent | # ]

Groklaw © Copyright 2003-2013 Pamela Jones.
All trademarks and copyrights on this page are owned by their respective owners.
Comments are owned by the individual posters.

PJ's articles are licensed under a Creative Commons License. ( Details )