Computer Software and Copyright
13. Proper Copyright Notice
As mentioned above, copyright notice informs the public that the author
is asserting rights under copyright law. Notice is not required for an
author to have a copyright in works published after 1989.
However, as mentioned in
§ 11, proper notice
coupled with federal registration will greatly increase one's chances of
prevailing in a lawsuit. Omission of proper copyright notice may enable
a defendant in a lawsuit to claim the defense known as ³innocent infringement.²
That is, a defendant may successfully claim that she was unaware that she
violated a copyright. This could sometimes result in the defendant prevailing
or, at the very least, limiting the amount of damages available. This defense
would likely not be available if proper notice was used.
Therefore, if a computer program is to be marketed or distributed to
multiple parties, it is highly recommended that it include proper notice.
At the Berkeley Lab of course, DOE must first grant permission to the University
of California to assert a copyright before any notice can be used.
Proper notice will contain the copyright symbol, or acceptable substitute;
the year of first publication, described above; and the name of the author.
If the program was published by a Berkeley Lab employee in 1996 the preferred
notice would be:
© 1996 The Regents of the University of California
or
Copyright 1996 The Regents of the University of California
or
Copyright © 1996 The Regents of the University of California
Also acceptable as a subordinate choice is
(c) 1996 The Regents of the University of California
or better yet
Copyright (c) 1996 The Regents of the University of California
If the program is a revision of a previous work it might have two dates,
one for the original work and one for the revision:
Copyright © 1994, 1996 The Regents of the University of California
or it could have a range for several revisions.
Copyright © 1991-1996 The Regents of the University of California
Typically, the copyright notice will appear along with the title such
as:
Hacker Tracer Program Copyright © 1990 Cliff Cybercop
If the work is unpublished, notice might look like this.
Hacker Proof OS. Unpublished Copyright © 1996 Cliff Cybercop
13.1 Where Should Notice Appear in a Computer Program?
Generally, the copyright notice on a computer program should appear in
several places. First, it should appear on or near the first page of the
source code. This is usually the "commented out" section at the beginning
of the program that also includes the title, revision information and introductory
remarks. Second, on application programs, it should be either briefly displayed
at program startup, at sign-on, or continuously displayed on program screens.
Third, it should appear on the labels affixed to disks or tapes that contain
either the source code or the executable code.
Finally, copyright notice should also appear on or near the first page
of any manuals that accompany the computer program.
13.2 DOE Also Requires a Separate Notice
Under the University of California¹s contract with DOE, the U.S. Government
is granted a paid-up, non-exclusive, irrevocable worldwide license for
5 years after permission is granted by DOE to the University of California
to assert the copyright. This license is renewable for two more 5 year
periods.
A notice reflecting this requirement must appear in the software and
accompanying manuals for computer programs federally registered by the
University of California . The
notice should
be in a prominent place in the source code and accompanying manuals.
The University of California¹s contract with DOE also requires
a ³Restricted Rights Notice.² This notice covers Restricted Computer
Software, which is defined as : ³. . . computer software developed
at private expense and that is a trade secret; is commercial or financial
and is confidential or privileged; or is published copyrighted computer
software; including minor modifications of such computer software.²
This notice essentially dictates the conditions under which the U.S.
Government has rights to the software. See the example in
Appendix
3.
*Written by John E. Wehrli, formerly of the Patent Department, Lawrence
Berkeley National Laboratory. Available as LBL Report No. 38995.
|