RE: Issue on WS-Security and WSDL definitions

WS-Security defines a soap header block.  Instances of this block gets
interchanged between software components.  WSDL allows for definition of
soap header blocks.  WS-Security does not provide WSDL definitions for the
ws-security header block, and we think they should.

Cheers,
Dave

> -----Original Message-----
> From: [email protected] [mailto:[email protected]]On
> Behalf Of Mark Baker
> Sent: Monday, November 11, 2002 4:17 PM
> To: [email protected]
> Subject: Re: Issue on WS-Security and WSDL definitions
>
>
>
> (to www-ws-arch only)
>
> On Mon, Nov 11, 2002 at 03:47:24PM -0800, David Orchard wrote:
> > As a best practice, members
> > of theweb services architecture group believe that WSDL
> definitions should
> > be part of any specification of SOAP Modules.
>
> I didn't follow the WS-Security discussion, but having just read this
> liason message, I'm quite confused by the text I quoted above.  Does
> anybody have an example of a SOAP module that needs a WSDL definition?
>
> The latest editor's draft of the SOAP 1.2 spec, part 1,
> defines a module
> as;
>
> "[...]the set of syntax and semantics associated with implementing a
> particular feature (see 3.1 SOAP Features) as SOAP header blocks[...]"
>
> which, to me, is a completely different thing than a software
> component
> with a network interface which needs describing.
>
> Am I understanding this correctly?
>
> MB
> --
> Mark Baker.  Ottawa, Ontario, CANADA.   http://www.markbaker.ca
>
>    Will distribute objects for food
>
>