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
Oracle: Wrong, Possibly, but not Surely | 97 comments | Create New Account
Comments belong to whoever posts them. Please notify us of inappropriate comments.
Oracle: Wrong, Possibly, but not Surely
Authored by: Anonymous on Friday, April 27 2012 @ 10:42 AM EDT

It could be my post of yesterday that you are mocking. Let me be clear, I am not a lawyer either and I hope that I don't assert that the issues are obvious. I presume that if it were as cut and dried as you suggest, the Court would not have wasted its time building a record in the dispute.

I read the judge's instructions on the matter and I find them succinct and clear as to the issues and as to what is and isn't being alleged.

The jury may find that there was no copying, no copying of protected items, or that the copying was fair use or de minimis and we're done. We may even have this phase terminated because of Oracle's fuzzy understanding of what Sun registered or that the materials provided to the Copyright office were incomplete. Without a valid registration, as I understand it, proof of authorship and date of publication is required and there are lower limits for claims. The latter bit is a recollection from 25 years back when I was paying attention to the copyright rules as a songwriter. The law may have changed or be different when applied to software.

I saw the instruction on vicarious infringement and I don't understand how a programmer's use of Google's documentation infringes on Oracle's rights, when Oracle's documentation is not protected for use as reference.

[ Reply to This | Parent | # ]

And statement wrong....
Authored by: Anonymous on Friday, April 27 2012 @ 10:54 AM EDT
"In this connection, the source code that implements the function of the
API is called the “implementation.” The “compilable code” does not include the
English-language comments you have heard about."

An implementation not "the" for source code

And source code *does* contained the English language comments

Object code does not, and is compiled rather than compileable..


Doesn't matter what a jit is or what a jVM does.

Java source, is compiled to java byte code (class files)


It's not good when you don't have accurate Jury instruction at this stage.

[ Reply to This | Parent | # ]

Another error
Authored by: Anonymous on Friday, April 27 2012 @ 11:19 AM EDT
"Google had no right to copy any elements of the Java platform protected by
copyright unless it had a written license to do so from Sun or Oracle or had a
written sub-license to do so from a third party who had a license from Sun
or"


Yet the document provides no instruction for what may not be protected by
copyright and therefore what google *may* be permitted to copy from the java
platform.

[ Reply to This | Parent | # ]

And another error
Authored by: Anonymous on Friday, April 27 2012 @ 11:23 AM EDT
nowhere is "structure, sequence and organization" defined.

some distinction is drawn between that on the code and that on the
documentation

It is not made clear that they are two separate things or in fact what exactly
it is that is being referred to as the SSO.

[ Reply to This | Parent | # ]

Question 2 conflates two seperate issues
Authored by: Anonymous on Friday, April 27 2012 @ 11:26 AM EDT
which will be very confusing....

1) is SSO in the code

2) is documentation copied (not SSO of documentation)

[ Reply to This | Parent | # ]

Oracle: Surely wrong as a matter of law
Authored by: Oliver on Friday, April 27 2012 @ 11:42 AM EDT
As various witnesses have stated, the names are the SSO. Well
the Structure & Organisation. The Sequence is irrelevant and
so could arguably be compared.

[ Reply to This | Parent | # ]

The law here is wrong.
Authored by: reiisi on Friday, April 27 2012 @ 07:38 PM EDT
Names can be munged with macro preprocessors. Structure can be munged with macro
preprocessors. So can order.

Which I wish some lawyer would discover. SSO is a completely arbitrary argument,
founded in random assumptions and producing random conclusions.

[ 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 )