- From: Munter, Joel D <joel.d.munter@intel.com>
- Date: Wed, 7 May 2003 08:37:26 -0700
- To: "Jim Webber" <jim.webber@arjuna.com>, <www-ws-desc@w3.org>
- Cc: "Savas Parastatidis" <Savas.Parastatidis@newcastle.ac.uk>
Jim, Savas, This is a neat and simple idea. From an editorial nature, you may have left an inadvertent wstx:transactional on page 2 (in the description following the XML example). It looks as though you replaced all of these with wstx:supports. Why do you refer to security as a non-functional requirement? Joel Munter, Intel desk: 480.552.3076 cell: 602.790.0924 -----Original Message----- From: Jim Webber [mailto:jim.webber@arjuna.com] Sent: Wednesday, May 07, 2003 8:01 AM To: www-ws-desc@w3.org Cc: 'Savas Parastatidis' Subject: Proposal for advertising QoS features of a Web service in WSDL Hello everyone, This is out-of-the-blue I know, but Savas Parastatidis and I have been kicking round a few ideas as to how we might expose certain non-functional requirement capabilities (like security or transactions) for a Web service. That said, we have created a (lightweight) framework to allow a service to advertise various non-functional aspects which we think might be useful for inclusion in WSDL 1.2. Jim -- Dr. Jim Webber Web Services Architect Arjuna Technologies http://www.arjuna.com
Received on Wednesday, 7 May 2003 11:39:12 UTC