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, PrasadReceived on Wednesday, 26 June 2002 17:55:03 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:58:20 GMT