"Jacob" <ja***@yahoo.com> wrote in message
news:Pf********************@telenor.com...
I am writing commersial code for clients.
In which case, you'd better make sure you have a clear
understanding as to who owns the code. If you're doing
this on a work-for-hire basis, they do. If you have no
explicit agreement, you do. But you'll save a lot of
grief if you clarify such matters up front.
It sometime seems like common practice to add a copyright
header to each source file (.cpp and .h). The header might
look something like this:
/*
* Copyright (C) 2005, SomeCompany
*/
Possibly followed by a lot of blah-blah.
My questions are these:
First, chase the link offered by Alan Johnson in a separate
post. Looks like a good one to me.
o Is developers (and others) free to steal a piece of code
if this heading is not there?
"Free to steal" is an oxyomron. You may be free to use code
or you might steal it, but you can't do both at once. Such
phraseology is bound to get you in trouble, sooner or later,
with others who might feel they have a stake in code you
write.
But to answer your question (already answered in the link
above), every expression is born with a copyright. You add
the notice out of "due diligence." If you have to enforce
your copyright, it helps that you put others on notice that
you own the work.
o What significance has the year in the example above?
Am I free to steal this piece of code in 2006 unless
the year is then updated?
Copyrights have a finite lifetime. This is the year the
clock starts ticking.
o What significance has the blah-blah that often follows the
copyright statement. Is the "(C)" not strong enough, but
requires qualifications?
The qualifications more often grant limited usage. They can't
impose more than the copyright law.
o What significance has the company name in the example above?
If the company is acquired (as is often the case with
development companies) should every header be updated in
order for them to be valid?
If you put a company name on the copyright, then that's who
owns the copyright. It is an asset that goes with the company.
No need to update all the headers if the path of ownership
over time is clear.
o What significance has a "file" in this context? Being just
bits and bytes on a storage medium, am I free to steal
the part of a storage (i.e. file) which does _not_ contain
the copyright statement?
o What about the directory structure? It is information as
well, but typically not copyrighted. Am I free to steal
its structure?
The basic principle is that you copyright a unique expression.
If there's something unique in any accompanying structure,
you'd better assume it's covered too.
o What do you do, and why?
(I just have the fealing that this practice is followed
beacause "everybody else" does it and it feels safe that way,
but without an explicit stated rationale).
I've done it ever since I went into the commercial software
business in 1978. I've done it on the advice of counsel, which
does change in small ways over time, but is pretty consistent
in the area of copyright notices. And those copyright notices
have paid off, in one out-of-court settlement and one knock-down,
drag-out trial in federal court.
In my current project we don't yet follow this copyright-header
practice, but I will suggest we do in case there are good reasons
for doing so. In that case, is there a copyright template I can
copy (!) :-) from somewhere?
You need:
-- the word "copyright"
-- the copyright symbol, though people seem to think (c) is an
acceptable alternative these days
-- the year(s) when the material was created, which evidently can
be a hyphenated range these days
-- the name of the copyright owner
If you also add "all rights reserved", you're putting people on
notice that they'd better contact you before doing anything that
might require permission.
Finally, if you think there's a real risk of infringement, and
serious losses possible if that happens, then by all means
register the copyright, the sooner the better. Otherwise, don't
bother.
P.J. Plauger
Dinkumware, Ltd.
http://www.dinkumware.com 
