Lists Home |
Date Index |
I don't think so. I read somewhere that Lloyds is about
to provide indemnity insurance of some kind but I don't
remember the details. Also, some companies such as Red
Hat are picking up some responsibility for open source
indemnity. Today in the contracts I read, it is a
caveat vendor clause: you build it, you indemnify it.
How that will work for the a la cart services (built a
web site, opened it for free access, maintain it
sporadically, but it gets used for serious work) is
likely caveat emptor. Again, the heck of this is until
the lawyers process a case or two, we don't know.
Critique of that topic is still fresh, but when one
reads RFPs and contracts daily, one gets a different
perspective on the evolution and marketing of web
systems. Hyping technologies into being is only
one part and a very early part of the evolution.
Then the real work of making them mercantile begins.
From: Chiusano Joseph [mailto:firstname.lastname@example.org]
> The same for services. It is the question I ask repeatedly:
> what is the culpability for services created on top of
> services, for example, using Google addresses and a separate
> geocoding service?
> I'd think long and hard before building an application over
> unvetted and non-indemnified web services. That this is also
> true of standards and specifications built by polite
> aggregation and published prior to serious implementation
> goes without saying.
Exactly. How about service insurance? I posed this idea to this listserv
and the W3C Semantic Web Services Public Listserv in Oct last year:
Is this a radical idea?