- From: Sandeep Kumar <sandkuma@cisco.com>
- Date: Fri, 15 Feb 2002 13:51:30 -0800
- To: "Champion, Mike" <Mike.Champion@SoftwareAG-USA.com>, <www-ws-arch@w3.org>
I wonder if we can take the following approach: 1. Gather all high level architectural requirements, such as the ones mentioned below (I would like to get these addressed) esp. keeping in mind that Microsoft would like to propose (in the works) specs on WS Licensing, Routing, etc. as part of the GXA strategy. 2. Define & deliver a Web Services Architecture Stack and work towards defining each of the stack elements Cheers, Sandeep Kumar Cisco Systems -----Original Message----- From: www-ws-arch-request@w3.org [mailto:www-ws-arch-request@w3.org]On Behalf Of Champion, Mike Sent: Friday, February 15, 2002 10:02 AM To: www-ws-arch@w3.org Subject: Goals for asych messaging / orchestration ? (was RE: Thinking abo ut Web Services Architecture) > -----Original Message----- > From: David Orchard [mailto:david.orchard@bea.com] > Sent: Thursday, February 14, 2002 1:41 PM > To: www-ws-arch@w3.org > Subject: RE: Thinking about Web Services Architecture > ... our rough priorities are: > > 1. Asynchronous, Conversational, Reliable messaging > 2. Secure messaging (Given that XMLE as a presumably pre-requesite > technology is not yet at CR) > 3. Simple discovery > 4. Orchestration Those are important priorities for us too, but I only see secure messaging on the strawman goals list. What about asynch and orchestration? Are these not required features of the Web Services Architecture, or are the "goals" at a higher level of abstraction and we're not talking about "requirements" yet?
Received on Friday, 15 February 2002 16:52:14 UTC