SOAP and HTTP binding: definition of {soap fault code} and wsoap:code

This is an issue which has already been addressed (LC130[1]) and
editorially implemented incorrectly.

It therefore is editorial. Details follow.

Part 2's section 5.7 Binding Faults defines:

     * {soap fault code} OPTIONAL. A xs:QName, to the Binding Fault
       component. The value of this property identifies a possible SOAP
       fault for the operations in scope. If this property is empty, no
       assertion is made about the value of the SOAP fault code.


     * wsoap:code OPTIONAL attribute information item

          * A [local name] of code

          * A [namespace name] of ""

          * A type of union of xs:QName and xs:token where the allowed token
            value is "#any"


   │       Property        │                     Value                     │
   │                       │ The actual value of the code attribute        │
   │ {soap fault code}     │ information item if present and if its value  │
   │                       │ is not "#any"; otherwise empty.               │

Why do we need "#any" as a possible value if the wsoap:code attribute
is optional?

It turns out that the resolution to LC130 was not properly

* Jonathan Marsh <> [2005-06-04 01:08-0700]
>   Issue LC130: Binding fault defaulting?
>     RESOLUTION: wsoap:subcode and wsoap:code will be optional,
>               wsoap:subcode and wsoap:code will allow #any as a token,
>               missing attribute will map to #any in the component model,
>               #any => no assertion is made about the value,
>               http:code will be similarly modified.


wsoap:subcode, wsoap:code and whttp:code need to be revised to reflect
the correct resolution of LC130.

Hugo Haas - W3C -

Received on Wednesday, 24 August 2005 10:12:32 UTC