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
Copyright on a compilation v copyright on its components | 394 comments | Create New Account
Comments belong to whoever posts them. Please notify us of inappropriate comments.
Copyright on a compilation v copyright on its components
Authored by: calris74 on Wednesday, April 25 2012 @ 10:55 PM EDT
Lets assume you published a compendium of out-of-print public domain journals. Lets say you agonise over many months what order to put them in (it was a really hard decision your honour, honestly, really hard) and you decide upon chronological order. Claiming copyright on that order would be like Oxford University Press claiming copyright on the order of words in their dictionary.

The thing is, Google probably chose the SSO which has been published in every Java book from day one. The SSO is logical to everyone in the Java ecosystem

Imagine this:
Question to Google: Why did you pick such a weird SSO for you class libraries - It's so confusing switching between JDK and Dalvik
Answer: We thought we would get sued
Response: HAHAHA - You have got to be kidding me. Man, that is the dumbest thing I have every heard. Like, helloooo, there are thousands of books which copy that info, not to mention ClassPath and Apache Harmony. You guys need your head read. I'm going to use iOS instead, this Java fragmentation is just too confusing

[ Reply to This | Parent | # ]

Non-literal elements of a compilation vs. non-literal elements of a computer programme
Authored by: Anonymous on Wednesday, April 25 2012 @ 11:08 PM EDT

IIRC, what is protected for compilations (aside from any copyright that may adhere in any given work included in the compilation - that copyright belongs to the creator of that work, and not the creator of the compilation) is the selection and arrangement (and possibly coordination in the U.S.) of the included works.

This is different from the structure, sequence, and organisation of computer programmes, which is also protected. I'm not sure if the protection of SSO applies to works that are not computer programmes in the U.S..

It's important to keep these concepts separate as they really are different things, although conceptually similar as they are kinds of what are called "non-literal elements" which are protected by copyright.

There seems to have been quite a bit of confusion about what is protected in each case here over the past few days.

There also seems to have been an assumption by the court and some of the lawyers that the API was somehow a computer programme and protectable that way, thus all the talk of SSO.

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