RE: Requirements: Describing WS Capabilities

Sandeep,

	I would like to add :

	4.	Cachability parameters about the message. 

		A simple example is a query web service from a database
which is updated once a day. So the web service output message can be
cached for 24 hrs, or more precisely cached till say 6:00 AM. There
could be other metadata associated with the caching of that message.

	Would it be a better idea to change 1 to :

	1.	Security Information which might be authC, authZ, ...

cheers

 | -----Original Message-----
 | From: www-ws-desc-request@w3.org 
 | [mailto:www-ws-desc-request@w3.org] On Behalf Of Sandeep Kumar
 | Sent: Wednesday, March 20, 2002 8:30 PM
 | To: www-ws-desc@w3.org
 | Subject: Requirements: Describing WS Capabilities
 | 
 | 
 | A WS description allows it to publish the message 
 | interactions it is capable
 | of handling. However, this description alone does not
 | capture any meta-information associated with the message interaction
 | definitions. The message interactions are meaningful in a
 | given business domain, or more precisely, as defined as part 
 | of W3C work on
 | ontology [1].
 | 
 | A Web Service description SHOULD be able to define 
 | extensible mechanisms for
 | capturing meta-information associated with a message.
 | 
 | Some of the examples of the meta-information are:
 | 
 | 1. Some messages of a WS may require authentication information.
 | 
 | 2. Some messages of a WS may deal with in a particular 
 | Business Domain. For
 | instance, submitPO, may be an overloaded
 | message where one such message primarily deals with RosettaNet.
 | 
 | 3. QoS parameters
 | 
 | Comments are welcome.
 | 
 | Reference:
 | -------------
 | 
 | [1] http://www.w3.org/TR/2002/WD-webont-req-20020307/
 | 
 | Thanks,
 | Sandeep Kumar
 | Cisco Systems
 | 
 |

Received on Thursday, 21 March 2002 13:46:07 UTC