Rather than have Duxbury be responsible for securing documents, I think it
should be up to the creator/editor to do so. This issue is important to
all creators of alternative text, not just Duxbury aficionados.
There are a variety of encryption/security techniques that could be used.
One person suggested encrypted .zip -- that's one option. Another would be
to secure the web directory where the online versions are being made
available for download. A variety of techniques could be used to do this,
depending on the type of web server used. We've used .htaccess for Apache
web servers in the past, and that does a decent job at limiting access to
certain directories and files.
The problem of securing copyrighted information is a responsibility both
for producers of alt text and the consumer. Producers shouldn't be making
copyrighted information available "in the clear" and users shouldn't be
illegally distributing the files they receive.
-*- Dan Comden danc@xxxxxxxxxxxxxxxx
Access Technology Lab http://www.washington.edu/computing/atl/
University of Washington
* * *
* This message is via list duxuser at freelists.org.
* To unsubscribe, send a blank message with
* unsubscribe
* as the subject to <duxuser-request@xxxxxxxxxxxxx>. You may also
* subscribe, unsubscribe, and set vacation mode and other subscription
* options by visiting //www.freelists.org. The list archive
* is also located there.
* Duxbury Systems' web site is http://www.duxburysystems.com
* * *
