Groklaw - Digging for Truth

	When you want to know more...

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

You won't find me on Facebook

Donate

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:

On servers donated to ibiblio by AMD.

Webmaster

Sorry, but you can see the SSO for yourself | 687 comments | Create New Account

Comments belong to whoever posts them. Please notify us of inappropriate comments.

Sorry, but you can see the SSO for yourself

Authored by: Anonymous on Saturday, April 28 2012 @ 09:36 AM EDT

go to developer.android.com

click on the reference tab

select the tree view using the link/button in the bottom left

expand all the trees that start with java and javax

Oracle wrote a section of it in their brief/reply to jury instructions/special
verdict where they agree/argue that names are not protected except where they
are part of the SSO.

Which is why Google lose the big fat manual, but then if you apply the same
standard of the documentation to the code (as suggested by Oracle) the code
goes free (so conceded).

Some question remains where you draw the "whole work" for the code
line. Around the 37? No. 160? is that versus android as a whole? or dalvik?
should it be Java(tm) as a whole? is it going to matter? the SSO isn't there
when you take the names out of the source code which you must.

[ Reply to This | Parent | # ]

Sorry, but you can see the SSO for yourself - Authored by: Ian Al on Saturday, April 28 2012 @ 10:24 AM EDT
- Sorry, but you can see the SSO for yourself - Authored by: Anonymous on Saturday, April 28 2012 @ 11:29 AM EDT
  - Only if Sun Registered the compilation of 37 or 166 - Authored by: Ian Al on Sunday, April 29 2012 @ 04:05 AM EDT
    - Only if Sun Registered the compilation of 37 or 166 - Authored by: PJ on Sunday, April 29 2012 @ 05:22 AM EDT
      - Were you referring to the litigation without registration? - Authored by: Ian Al on Sunday, April 29 2012 @ 05:58 AM EDT
      - Dodgems - Authored by: Ian Al on Sunday, April 29 2012 @ 11:41 AM EDT

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 )