RE: Copyright of data

Putting code "in escrow" isn't to protect the vendor, but to 
protect the customer in case the vendor goes "belly up".

Or so I always thought anyway.

I think the simple way to handle copyright is to just not 
distribute the source code.

This works for a horizontal application (Like FaxServer/401) but 
would be much harder if not impossible for a "line of bushiness" 
type app.

Regards,
Bob Crothers
Cornerstone Communications


-----Original Message-----
From:   HankHeath [SMTP:HankHeath@aol.com]
Sent:   Thursday, January 22, 1998 6:20 AM
To:     MIDRANGE-L@midrange.com
Subject:        Re: Copyright of data

Actually, in one place that I worked with, the proposal was to 
put the source
in a bank vault "in escrow" to protect it. Thought that was an 
interesting
tack on the subject.

Hank Heath

In a message dated 98-01-22 00:03:32 EST, you write:

<< DAsmussen <DAsmussen@aol.com> wrote:
 >I don't know about Internationally, but in the US you used to 
be
 >able to mail a copy of the source code or manuscript in 
question to
 yourself
 >in a sealed envelope.  Opened in court with the seal and 
postmark intact,
 it
 >was generally considered "compelling evidence" of copyright. 
 Don't know if
 >this still holds, as US litigators (if possible) have become 
even more
 >"sneaky" in recent years... >>
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to 
"MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to 
MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: 
david@midrange.com
+---

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---