W3C home > Mailing lists > Public > public-ws-chor@w3.org > May 2003

RE: Web Services Management and Choreography

From: Stanislaw Ambroszkiewicz <sambrosz@ipipan.waw.pl>
Date: Thu, 8 May 2003 13:19:19 +0200 (CEST)
Message-Id: <200305081119.h48BJKh15360@ns.ipipan.waw.pl>
To: James.McGovern@thehartford.com
Cc: public-ws-chor@w3.org

  >  James.McGovern wrote: 
  >  Management platforms provide a level of indirection which is useful for
  >  adding into an architecture the concept of metering, monitoring, billing,
  >  routing, security, and so on. Check out Talking Blocks and Amberpoint for
  >  vendors who provide implementations.
I do not consider it as an answer to my question: What do you mean by "request"?

However, generally you are right that a complex client's request (task) may be 
broken into a number of sub-requests and routed separately to different 
services. Some of these services (if they are composite) may again decompose 
the sub-request into sub-sub-requests and send separately to different services, 
and so on recursively. 
Note that these different services may come from different providers / vendors. 
Hence, there MUST be *platform independent* uniform standard way/language to 
express requests. 

There is an attempt in this direction, 
see M. Papazoglou, M. Aiello, M. Pistore, and J. Yang. 
XSRL: A Request Language for Web Services. Published at 
However, specs of XSRL are not available. 

IMO the concept of request is crucial for web services technology. 
Perhaps this very issue should be addressed by W3C and the "great" IT vendors 
instead of trying to recover dying or already dead technologies. 

 Best regards,
   -- Stanislaw Ambroszkiewicz
   Institute of Computer Science,    mailto:sambrosz@ipipan.waw.pl
   Polish Academy of Sciences,       http://www.ipipan.waw.pl/mas/
Received on Thursday, 8 May 2003 07:19:25 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:30:04 UTC