Re: proposal: minor syntax improvement for soap fault bindings

• From: Roberto Chinnici <Roberto.Chinnici@Sun.COM>
• Date: Mon, 03 May 2004 17:05:23 -0700
• To: Sanjiva Weerawarana <sanjiva@watson.ibm.com>
• Cc: www-ws-desc@w3.org
• Message-id: <4096DE43.1020604@sun.com>

How about a further improvement? Instead of

       <wsoap:code value="xs:QName">
         <wsoap:subcode value="xs:QName">
           <wsoap:subcode>...</wsoap:subcode>
         </wsoap:subcode>?
       </wsoap:code>

we do:

       <wsoap:code value="list of xs:QName">
       </wsoap:code>

I.e. the value of @code is a list of QNames, the first one being
the code and the other ones its subcodes. And of course we cshould
constrain the list to have length > 0.

Roberto


Sanjiva Weerawarana wrote:
> I suggest we move wsoap:code/wsoap:value to an attribute:
> 
> That is, instead of:
> 
>       <wsoap:code>
>         <wsoap:value>xs:QName</wsoap:value>
>         <wsoap:subcode>
>           <wsoap:value>xs:QName</wsoap:value>
>           <wsoap:subcode>...</wsoap:subcode>
>         </wsoap:subcode>?
>       </wsoap:code>
> 
> we do:
> 
>       <wsoap:code value="xs:QName">
>         <wsoap:subcode value="xs:QName">
>           <wsoap:subcode>...</wsoap:subcode>
>         </wsoap:subcode>?
>       </wsoap:code>
> 
> This makes the syntax more consistent with the rest of the
> SOAP binding which is rather attribute-heavy.
> 
> Sanjiva.

Received on Monday, 3 May 2004 20:05:11 UTC