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 documentation can be treated as a separable component of the source code | 687 comments | Create New Account
Comments belong to whoever posts them. Please notify us of inappropriate comments.
The documentation can be treated as a separable component of the source code
Authored by: bugstomper on Friday, April 27 2012 @ 04:32 PM EDT
I don't have a problem with the specification document being generated from the
comments in the source code. That isn't so different from the notion that a book
might be created in WordPerfect or LaTeX files, but eventually run through
software that formats and prints it. Would you argue that Harry Potter Volume I
is a derivative work of whatever file was sent to the printer? Whoever wrote a
piece of the Java Class Library Specification wrote it in the form of comments
in source code following a certain template and rigid writing style. To the
degree that the elements of what they wrote were determined by the
functionality, which would be true of the signatures and lists of parameter and
fields names and types, and to the degree that the order of listing is
alphabetical, then it is not copyrightable material. But the English
descriptions should be copyrightable even if they are written in comments in a
source file which are extracted to the print format of the Specifications book.

Of course, it is exactly those English specifications that nobody argues Google
copied.

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