W3C home > Mailing lists > Public > xml-dist-app@w3.org > February 2003

RE: SOAP Schema

From: Martin Gudgin <mgudgin@microsoft.com>
Date: Wed, 19 Feb 2003 12:20:32 -0800
Message-ID: <92456F6B84D1324C943905BEEAE0278E02D30CF3@RED-MSG-10.redmond.corp.microsoft.com>
To: "Adonis Amore" <infoletter@myrealbox.com>, <xml-dist-app@w3.org>

Because that content model is non-deterministic. That said, we could say


<xs:choice>
  <xs:element ref='tns:Fault' />
  <xs:any namespace='##other' minOccurs='0' maxOccurs='unbounded' />
</xs:choice>

Although this would rule out sending soap:Envelope ( or soap:Header or
soap:Body ) as a child of soap:Body, which I don't think we want to
preclude, so maybe:

<xs:choice>
  <xs:element ref='tns:Fault' />
  <xs:element ref='tns:Envelope' maxOccurs='unbounded' />
  <xs:element ref='tns:Header' maxOccurs='unbounded' />
  <xs:element ref='tns:Body' maxOccurs='unbounded' />
  <xs:any namespace='##other' minOccurs='0' maxOccurs='unbounded' />
</xs:choice>

Thoughts anyone?

Gudge

> -----Original Message-----
> From: Adonis Amore [mailto:infoletter@myrealbox.com] 
> Sent: 19 February 2003 10:34
> To: xml-dist-app@w3.org
> Subject: SOAP Schema
> 
> 
> 
> 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 15:21:08 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:59:13 GMT