W3C home > Mailing lists > Public > www-ws-desc@w3.org > September 2002

Re: How to specify the operational requirement in bindings ?

From: Ricky Ho <riho@cisco.com>
Date: Sun, 08 Sep 2002 10:26:25 -0700
Message-Id: <4.3.2.7.2.20020908101919.02780328@franklin.cisco.com>
To: "Sanjiva Weerawarana" <sanjiva@watson.ibm.com>, <www-ws-desc@w3.org>

Do you think this is part of the "contract" between the client and server 
provider ?  I mean the client has to learn about these before they can 
properly make their invocation request.  If WSDL "Bindings" is to provide 
the mapping from an abstract operation to what needs to go into the wire, 
then it seems to a good place to cover this.  Or, where else (in any WS??) 
have we covered it ?

Best regards,
Ricky

At 05:19 PM 9/7/2002 +0600, Sanjiva Weerawarana wrote:
>IMO this is out of scope for WSDL. This is basically a policy
>assertion about a Web service - undoubtedly a critical capability,
>but not in the domain of WSDL.
>
>Sanjiva.
>
>----- Original Message -----
>From: "Ricky Ho" <riho@cisco.com>
>To: <www-ws-desc@w3.org>
>Sent: Saturday, September 07, 2002 3:02 AM
>Subject: How to specify the operational requirement in bindings ?
>
>
> >
> > Hi,
> >
> > Regarding how a simple web services can be aggregated in complex real-life
> > scenario, any thoughts on how one can specify a certain operation of a
> > particular port type requires the caller to be authenticated and possess
> > certain security tokens ?  Or how to specify if the operation has to be
> > called within an already established conversation (some sort of
>correlation
> > properties) ?  Or how to specified if the operation has to be called
>within
> > a transaction (so the invoker has to pass in the "transaction context" and
> > a registration service so that the service provider can be enrolled in the
> > transaction as a participant) ?
> >
> > Best regards,
> > Ricky
Received on Sunday, 8 September 2002 20:34:46 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:58:21 GMT