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
The only thing you need is the names | 270 comments | Create New Account
Comments belong to whoever posts them. Please notify us of inappropriate comments.
APIs and copyrights
Authored by: Anonymous on Friday, April 20 2012 @ 01:48 PM EDT
Fixed in a tangible medium is not the only requirement for copyright protection.
Read the often cited Baker vs Selden. The court was quite clear that even if you
copied Selden's forms exactly, you would not be infringing copyright. More
recent and applicable to computers is Lotus vs Borland. Again, the menu
structure was certainly fixed in a tangible medium (source code and binary) and
was copied exactly. But the court found no infringement.

[ Reply to This | Parent | # ]

The only thing you need is the names
Authored by: Anonymous on Friday, April 20 2012 @ 02:39 PM EDT

Which receive no protection.

The good Judge A said so. And the parties agreed to the stipulation. Beyond the
names, what's left in an API specification is little more than fluff, font
selection, table layout etc. etc.

The names are not protected, everyone already agreed to that.


[ Reply to This | Parent | # ]

APIs and copyrights
Authored by: scav on Friday, April 20 2012 @ 04:23 PM EDT
When you take an API specification that was recorded on some fixed medium (printed or electronic), and you type it into your source code editor in order to implement the API, you have made a copy of the API.
Nope. You don't do anything of the kind. The API specification document is NOT copied into the source code of an implementation of the API. There are functional elements in the implementation that correspond to facts described in the specification, but:
  1. They are unprotectable elements because functional and required for interoperability.
  2. They are not the API itself, nor a copy of it (whatever that means). They are part of an implementation of it and separate work.
  3. As a matter of industry practice and common sense, they are not a derivative work, and Oracle's position that they are is flat out untenable. It goes beyond estoppel - it's like some kind of super-meta-estoppel, where everybody ever, including Oracle has been acting all along as though the whole point of published specifications is to allow independent implementations, and suddenly Oracle wants to change the rules purely because they need it to be otherwise temporarily to rescue their hopeless badly- conceived litigation.

Entertain the possibility that you are mistaken about this.

---
The emperor, undaunted by overwhelming evidence that he had no clothes, redoubled his siege of Antarctica to extort tribute from the penguins.

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