W3C home > Mailing lists > Public > xml-dist-app@w3.org > November 2007

mistake in SOAP envelope XMLSchema

From: Alessandro Pira <apira@kion.it>
Date: Mon, 12 Nov 2007 10:44:25 +0000
Message-ID: <567B12C7C33B3D47BDB7E00867D65D1F016999E8@ercole.kion.it>
To: <xml-dist-app@w3.org>
Hi all,
I am writing to this mailing list since I think I found a mistake in the
official xml schema for SOAP envelopes:
The error involves the encodingStyle attribute which (as stated in
examples in the note and also in [1]) seems possible to use in the
Envelope element.
But the official XMLSchema (http://schemas.xmlsoap.org/soap/envelope/)
forbids this since it states:
<xs:complexType name="Envelope">
   <xs:element ref="tns:Header" minOccurs="0"/>
   <xs:element ref="tns:Body" minOccurs="1"/>
   <xs:any namespace="##other" minOccurs="0" maxOccurs="unbounded"
 <xs:anyAttribute namespace="##other" processContents="lax"/>
I think it should say namespace="##any" in the xs:anyAttribute element
(or explicitly define the encodingStyle attribute).
I wrote you because the company I work for publishes some webservices
for our customers, and we use 3rd party libraries for managing SOAP
communication. Now some of our customers for some reason are accusing us
to be not compliant to the official SOAP protocol, which I think is not
true, but even W3C XMLSchema validator shows that the Envelope we use is
not valid because of the "encodingStyle" attribute.
Can you please check if it's possible to correct the XMLSchema?
Thank you in advance for your time,
Alessandro Pira
[1] : the SOAP 1.2 part 0 Primer in Chapter 6 (Changes Between SOAP 1.1
and SOAP 1.2) states:
"SOAP 1.2 does not allow the env:encodingStyle attribute to appear on
the SOAP env:Envelope, whereas SOAP 1.1 allows it to appear on any
element. SOAP 1.2 specifies specific elements where this attribute may
be used."
Received on Tuesday, 13 November 2007 14:06:43 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 22:01:31 UTC