- From: Martin Gudgin <marting@develop.com>
- Date: Wed, 7 Nov 2001 10:39:09 -0000
- To: "Rich Salz" <rsalz@zolera.com>
- Cc: "Jacek Kopecky" <jacek@systinet.com>, "XML Protocol Discussion" <xml-dist-app@w3.org>
So, you're proposing something like <soap:Fault xmlns:soap='http://www.w3.org/2001/09/soap-envelope' > <faultcode> <value>soap:Reciever</value> <value xmlns:app='http://example.org/apps' >app:SomeError</value> </faultcode> </soap:Fault> the corresponding schema would be; <xs:schema xmlns:xs='http://www.w3.org/2001/XMLSchema' xmlns:tns='http://www.w3.org/2001/09/soap-envelope' targetNamespace='http://www.w3.org/2001/09/soap-envelope' > <xs:complexType name='faultcodeType' > <xs:sequence> <xs:element name='value' type='xsd:QName' minOccurs='1' maxOccurs='unbounded' /> </xs:sequence> </xs:complexType> </xs:schema> This doesn't imply a hierarchy to me but rather that all the fault codes are of equal 'importance'. But I can see the argument that the order of the siblings determines importance. Gudge ----- Original Message ----- From: "Rich Salz" <rsalz@zolera.com> To: "Martin Gudgin" <marting@develop.com> Cc: "Jacek Kopecky" <jacek@systinet.com>; "XML Protocol Discussion" <xml-dist-app@w3.org> Sent: Tuesday, November 06, 2001 11:45 PM Subject: Re: Proposal for hierarchical fault codes > suppose it's an array, rather then nested? > > Martin Gudgin wrote: > > I did consider the approach you suggest. I rejected it because there is ( > > currently ) no way to assign a type to the text content of <faultcode> in > > such a design. That is, there is no way to say that the text must be a > > QName. This is a problem/design choice regarding mixed content in XML > > Schema. > > -- > Zolera Systems, Securing web services (XML, SOAP, Signatures, > Encryption) > http://www.zolera.com
Received on Wednesday, 7 November 2001 05:40:13 UTC