Re: WSDL SOAP Binding schema does not reflect the spec

This does sound very much like issue 49 [1].

Jean-Jacques.

[1] http://www.w3.org/2002/ws/desc/2/06/issues.html#x49

Prasad Yendluri wrote:

> Not sure if we have an issue open to capture the schema issues but, one
> example I noticed is:
>
> The SOAP binding section makes <soap:body> a required EII and
> <soap:header> and <soap:headefault> optional EIIs that can also occur >
> 1 times:
>
>                 <soap:body parts="nmtokens"? use="literal|encoded"
>                              encodingStyle="uri-list"? namespace="uri"?>
>
>                <soap:header message="qname" part="nmtoken"
> use="literal|encoded"
>                             encodingStyle="uri-list"? namespace="uri"?>*
>
>                  <soap:headerfault message="qname" part="nmtoken"
> use="literal|encoded"
>                                    encodingStyle="uri-list"?
> namespace="uri"?/>*
>
> Where as the schema neither the one in the spec [1] nor the one at [2]
> capture these constraints.
>
> [1] http://www.w3c.org/tr/wsdl
> [2] http://schemas.xmlsoap.org/wsdl/soap
>
> Regards, Prasad

Received on Thursday, 27 June 2002 05:11:57 UTC