W3C home > Mailing lists > Public > www-ws-arch@w3.org > March 2002

Re: architecture question

From: Tim Coote <tim@coote.org>
Date: Wed, 20 Mar 2002 18:29:57 -0000
Message-ID: <00d501c1d03d$3cbcc070$801fa8c0@homebox>
To: "David Booth" <dbooth@w3.org>
Cc: <www-ws-arch@w3.org>
Hi David
A typical example here would be the current account systems of most UK
clearing banks whose 'current balance' is actually the amount in the account
after yesterday's transactions have been applied and don't know about
anything that has already happened today, or what transactions were queued
up to be applied today.  These systems may also assume that they will only
be interrogated between 8am and 8pm, the currency is assumed, not explicit,
the applications have no real service levels for response times, and they
can show confidential information that is expected to be filtered and
interpreted by an employee.

I think that my fear is that there'll be a different set of assumptions for
each company's web services and that it won't be possible to capture these
within the discovery protocols so that discovery will not be automatic and
the interoperability challenges will be of a similar size to those of
implementing EDI, but with an even larger legal bickering process over who's
responsible for errors.

tc
----- Original Message -----
From: "David Booth" <dbooth@w3.org>
To: "Tim Coote" <tim@coote.org>; <www-ws-arch@w3.org>
Sent: Wednesday, March 20, 2002 4:21 PM
Subject: Re: architecture question


> Tim,
>
> At 12:50 PM 3/20/2002 +0000, Tim Coote wrote:
> >The biggest challenges tend to come from very old assumptions (~20 years
> >old) in line of business applications.
>
> Can you elucidate?   What are some of these assumptions?
>
>
> David Booth
> W3C Fellow / Hewlett-Packard
> Telephone: +1.617.253.1273
>
>
Received on Wednesday, 20 March 2002 13:30:04 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 3 July 2007 12:24:56 GMT