Two license questions

Richard Bondi richardbondi at
Thu Mar 30 16:21:11 UTC 2000

Dear All,

My book will be my publisher's first to include open source licensed code. 
(The book is "Cryptography for Visual Basic: A Programmer's Guide to the 
Microsoft CryptoAPI", and includes open source COM wrappers for the 
CryptoAPI.) Can someone help me with the following questions please?

1) I think this belongs on an FAQ at if I use one of 
the approved licenses, can I rename it? I'm going to use the Ricoh license 
for my book's code; can I call it the Wiley Open Source Public License 

2) My publisher is very confused about whether they should replace their 
standard CD software statement with the Ricoh license, or put both on the 
page facing the CD. Do they contradict each other because the Wiley 
statement says "All rights reserved"? What confuses me is that the Ricoh 
license's Exhibit says "All Rights Reserved:" doesn't it actually grant a 
ton of rights?!! Here's the old Wiley statement:

OPENING THE PACKAGE.This software contains files to help you utilize the
models described in the accompanying book.
By opening the package, you are agreeing to be bound by the following
agreement: This software product is protected
by copyright and all rights are reserved by the author, John Wiley & Sons,
Inc., or their licensors. You are licensed to use
this software as described in the software and the accompanying book.
Copying the software for any other purpose
may be a violation of the U.S. Copyright Law.This software product is sold as
is without warranty of any kind, either
express or implied, including but not limited to the implied warranty of
merchantability and fitness for a particular purpose.
Neither Wiley nor its dealers or distributors assumes any liability for any
alleged or actual damages arising from the use
of or the inability to use this software. (Some states do not allow the
exclusion of implied warranties, so the exclusion may not apply to you.)

TIA for your help!

Richard Bondi

More information about the License-discuss mailing list