Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!ucbvax!ucdavis!iris!lim
From: lim@iris.ucdavis.edu (Lloyd Lim)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Publishing Software
Message-ID: <9071@ucdavis.ucdavis.edu>
Date: 31 May 91 01:38:47 GMT
References: <1991May28.105610.29170@crash.cts.com> <11293@bunny.GTE.COM>
Sender: usenet@ucdavis.ucdavis.edu
Reply-To: lim@iris.ucdavis.edu (Lloyd Lim)
Organization: U.C. Davis - Department of Electrical Engineering and Computer Science
Lines: 59

In article <11293@bunny.GTE.COM> CAH0@bunny.gte.com (Chuck Hoffman) writes:
>In article <1991May28.105610.29170@crash.cts.com> stuart1@pro-sol.cts.com 
>(Stuart Schechter) writes:
>> number.  The cost for this is around $40 and the forms may be obtained 
>
>... The cost is $10 if you copyright the 
>source as "text" (form TX).  You can get the forms by calling a recording 
>at the Library of Congress in Washington.  Call directory assistance for 
>that area code to get the number.  You do need to send in TWO copies of 
>your source, showing at least the first 50 and last 50 pages...

It's 50 pages total, the first and last 25.  First and last can mean almost
anything when you have separate source code files so you have quite a bit of
leeway in choosing what you want to give them.  Also, if you ask for "special
relief" you can routinely get away with the first and last 10 pages for a
total of 20.  There are other options too.  For source code, you only need
to send in ONE copy.

>Software is protected in the U.S. by a hodgepodge of overlapping 
>copyright, patent, and trade secret laws.  They aren't necessarily 
>mutually supportive.  For example, when you file a copyright you lose 
>trade secret protection.  A good book is "Legal Care for your 
>Software" published by Nolo Press, Berkeley, CA.  It also tells you
>how to fill out the form, which can be ambiguous and confusing.

Yes, a good book, now in 3rd edition.  Nolo Press has an excellent program
where you can recycle out-of-date books and get 25% off.  You can copyright
something and still have it be a trade secret but it's tricky.

>If you have shown something in a newsletter, or in a talk or presentation, 
>or have just showed off copies of it to some other people, before you 
>declare your copyright (by putting the copyright notice in), you will *NOT* 
>have a valid copyright claim later.  Put the copyright notice in when
>you first write the code.

This is not true.  In all countries in the Berne Convention (U.S. and
probably every country on the net), no copyright notice is required.
Copyright protection is automatic from the time of creation.  But it's a
good idea to always put a notice in to avoid confusion and hassles.  A notice
also gives you a stronger position if there's trouble.

>The word "Copyright" and the copyright symbol ")" are both okay...
                                               ^^^
You know what he means, option-g.

>For programmers, I recommend that for any significant legal work, use the
>services of a professional attorney.  (And for attorneys, I recommend that
>for any significant programming work, use the services of a professional
>programmer.)

I'd also recommend trying to find one that is familiar with computer law.
It's getting really complex these days and you can't expect just any lawyer
to know what's going on.

+++
Lloyd Lim     Internet: lim@iris.eecs.ucdavis.edu
              America Online: LimUnltd
              Compuserve: 72647,660
              US Mail: 215 Lysle Leach Hall, U.C. Davis, Davis, CA 95616