Thanks Erlend. So, escrowing w.r.t bankrupcy or dropping support for the
product is clear.
There's one more request the EDI implementing company ("BIG" one) is making,
that is to "trigger escrow" in case the documentation accompanying the
sofware do not "match". In this case, they will send us several reminders
for meeting/correcting the documented feature and if within reasonable time
(1-2-3 months) we are still unable to, then they can trigger the escrow
account. They say that they will use the source only for supporting their
clients and will not do anything else with it and will not claim for IPR.
I'll highly appreciate some comment on this. There's total disagreement with
them on this one.
I've told them of software being "licensed" and NOT "sold" and a DEVELOPER
disclaims all warranty w.r.t "merchantibility", "fitness for particular
use", conformance with documented features etc. and that they are standard
part of any pre-packaged software license agreement and that our liability
is limited to only refund of the software they paid for, in case we are
unable to correct the behaviour.
Their concern is that replacing EDI software is not plug and play and
therefore rules associtated with "pre-packaged" cannot be applied in it's
entirety.
Please let me know.
Thank you,
Regards,
Ajay
=======================================================================
To signoff the EDI-L list, mailto:[EMAIL PROTECTED]
To subscribe, mailto:[EMAIL PROTECTED]
To contact the list owner: mailto:[EMAIL PROTECTED]
Archives at http://www.mail-archive.com/edi-l%40listserv.ucop.edu/
