W3C home > Mailing lists > Public > www-ws-arch@w3.org > May 2003

RE: WSA architectural concepts and relationsihips related to WS, SOA, and the Web

From: Champion, Mike <Mike.Champion@SoftwareAG-USA.com>
Date: Tue, 6 May 2003 14:03:14 -0600
Message-ID: <9A4FC925410C024792B85198DF1E97E40598582A@usmsg03.sagus.com>
To: Ugo Corda <UCorda@SeeBeyond.com>, "Champion, Mike" <Mike.Champion@SoftwareAG-USA.com>, www-ws-arch@w3.org



> -----Original Message-----
> From: Ugo Corda [mailto:UCorda@SeeBeyond.com]
> Sent: Tuesday, May 06, 2003 3:59 PM
> To: Champion, Mike; www-ws-arch@w3.org
> Subject: RE: WSA architectural concepts and relationsihips related to
> WS, SOA, and the Web
> 

> Instead of "does not depend ..." I would say "whose 
> invocation does not depend ...". The AGENT itself might very 
> well depend internally on the context related to the 
> invocation of other SERVICES (typical example: a BPEL 
> process, which is offered externally as a Web service but 
> depends internally on the invocation and coordination of a 
> bunch of other Web services).

Good point, I wrestled with that wording and i like yours better.  I think
the informal sense is that a SERVICE should look to the outside world as if
it were a discrete component, or at least a "good" service is one that acts
as if it were decoupled from the application that physically implements it.
So, I should be able to invoke someone's "purchase order processing service"
even if that is deeply imbedded in an SAP system or whatever, without
knowing about all the implementation complexity.
Received on Tuesday, 6 May 2003 16:03:31 GMT

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