SOAP Schema

• From: Adonis Amore <infoletter@myrealbox.com>
• Date: Wed, 19 Feb 2003 11:33:51 +0100
• To: <xml-dist-app@w3.org>
• Message-ID: <007601c2d802$67023f90$6800a8c0@ventus2>

Hi,

from http://www.w3.org/TR/2002/CR-soap12-part1-20021219/#soapfault :
"To be recognized as carrying SOAP error information, a SOAP message MUST
contain a single SOAP Fault element information item as the only child element
information item of the SOAP Body ."


from http://www.w3.org/2002/12/soap-envelope/ :

 <xs:element name="Body" type="tns:Body"/>
 <xs:complexType name="Body">
  <xs:sequence>
   <xs:any namespace="##any" processContents="lax" minOccurs="0"
maxOccurs="unbounded"/>
  </xs:sequence>
  <xs:anyAttribute namespace="##other" processContents="lax"/>
 </xs:complexType>


With that XSD-extract above it is possible to merge Fault-Elements and anykind
of other XMLStuff in the Body.
So, just want to know why there is no 'choice' between 'any' XML-content and the
'Fault'-Element?


Why not something like that:

 <xs:element name="Body" type="tns:Body"/>
 <xs:complexType name="Body">
  <xs:choice minOccurs="0">
   <xs:any namespace="##any" processContents="lax" maxOccurs="unbounded"/>
   <xs:element ref="tns:Fault"/>
  </xs:choice>
  <xs:anyAttribute namespace="##other" processContents="lax"/>
 </xs:complexType>

Alois

Received on Wednesday, 19 February 2003 05:33:32 UTC