Comments on WSA document

I want to raise two issues that are not made explicitly clear in the WSA
document, but in my opinion are important to cover in the WSA document
itself.

First is the notion of requirements regarding the capabilities of the
service requestor and service provider.

In the SOA it is common to have requestor and providers that are not peers
(aka client-server). This is also very common in the Web. A service
requester can be a Web browser, and the service provider a Web server. There
is no need for the requester to also be a Web server in order to interact
with service providers.

That requirement is fulfilled in WSDL - it only requires the service
provider to define access points. ebXML represents a different model in
which all roles must be able to act as to act as service providers (peers).

My opinion is that the WSA document should cover both uses cases and explain
the role that WSDL plays in the SOA, but without precluding the use of ebXML
and other technologies where they are applicable (e.g. when all participants
are peer services, or the messaging layers requires them to be peer
services)

Second is the notion of performing activities at both sides (requestor and
provider) where the WS interface captures the message exchange that
demarcates these activities (e.g. input and output of operation). A
definition of these activities are how they relate to communication would
help in defining synchronous/asynchronous and other interesting artifacts.

arkin


----------------------------------------------------------------------
Assaf Arkin                                          arkin@intalio.com
Intalio Inc.                                           www.intalio.com
The Business Process Management Company                 (650) 577 4700

This message is  intended  only for the  use of  the Addressee and may
contain information  that is PRIVILEGED  and CONFIDENTIAL.  If you are
not the  intended recipient,  dissemination of  this  communication is
prohibited.  If you have received this communication  in error, please
erase all copies  of the  message and  its  attachments  and notify us
immediately.

Received on Sunday, 23 February 2003 20:24:37 UTC