WSDL SOAP Binding schema does not reflect the spec

• From: Prasad Yendluri <pyendluri@webmethods.com>
• Date: Wed, 26 Jun 2002 14:58:41 -0700
• To: www-ws-desc@w3.org
• Message-ID: <3D1A3910.C1859316@webmethods.com>

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 Wednesday, 26 June 2002 17:55:03 UTC