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
You are wrong | 751 comments | Create New Account
Comments belong to whoever posts them. Please notify us of inappropriate comments.
You are wrong
Authored by: Anonymous on Wednesday, October 03 2012 @ 01:43 PM EDT
"Software, just as any other creative product, is copyrighted from the
moment it
is created with all rights reserved."

This is the traditional position. There was a time when word came from the
legal department where I worked and we had to check all source code files and
make sure that each and every one had a copyright statement. We were told that
this was required to protect the company trade secrets. At that time, the term
"intellectual property" was not widely used. It was explained to us
that the copyright was not enforceable for software unless the source code
declared the copyright.

I think that what the legal profession had decided was that the creator had the
exclusive authority to reserve rights under copyright law but without a
declaration of copyright, the presumption of the legal profession was that the
creator did not wish to exercise those rights. In this case, they decided that
to error on the side of the user over the interest of the creator was justified.
This amounts to a kind of "use it or loose it" argument.

I do not know where things stand now in the shifting sands of the legal
profession but the assumption we were to operate on as engineers is that
"copyright is not enforceable unless rights are specifically reserved by
declaration in the document in question." I have seen two answers to this
in open source: put a copyright statement at the top of all files, or put a
COPYRIGHT document in the top directory of the source code tree.

IANAL. The simplest copyright state reserves all rights but this is not
compatible with FOSS by itself. When source code is shared as FOSS then the
rights retained by each rights-holder needs to be clearly understood. Does the
original creator have rights over all modifications of his document? Do
copyrights aggregate to all contributors? Is there an explicit license stated
that manages these rights? You can see just as much confusion can be created by
how copyrights are declared as to the ambiguous condition where they were not
declared at all.

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