W3C home > Mailing lists > Public > xml-dist-app@w3.org > October 2002

SOAP 1.2 Specification and confusion around Subcode

From: <Ed.Morassut@bmo.com>
Date: Fri, 4 Oct 2002 08:30:31 -0400 (EDT)
To: xml-dist-app@w3.org
Message-ID: <OFEF883AB9.76E05413-ON85256C48.004430D0@notes.bmo.com>




I read through the specifications and I have a question around Subcode:



5.4.1.3 SOAP Value element (with Subcode parent)


The Value element information item has:

     A [local name] of Value .
     A [namespace name] of http://www.w3.org/2002/06/soap-envelope .

The type of the Value element information item is QName in the "
http://www.w3.org/2001/XMLSchema" namespace. The value of this element is
an application defined subcategory of the value of the Value child element
information item of the Subcode element information item's parent element
information item (see 5.4.6 SOAP Fault Codes).


NOTE. What is not clear here is whether you can make this element
information item a  faultCodeEnum from an application specific namespace
(the spec doesn't make this clear).  A further concern is that Subcode
appears to be disconnected from WSDL implying a developer has no way of
understanding the domain values of this Enum because it is not documented
as part of the interface.


Is this someting you folks have already thought through?  The debate in our
shop is that we should avoid Subcode and put such meaning into the fault
detail (especially being that the current tooling doesn't yet support
Subcode).  If we end up putting such meaning into the detail we'll end up
coupled to non-standard detailed parsers in order to isolate an equivalent
of Subcode.  Am I missing something here?  Can we make the Enum from an
application specific namespace and how do we expose in WSDL?
Received on Friday, 4 October 2002 08:37:46 GMT

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