- From: <paul.downey@bt.com>
- Date: Thu, 6 May 2004 17:39:07 +0100
- To: <Roberto.Chinnici@Sun.COM>, <sanjiva@watson.ibm.com>
- Cc: <www-ws-desc@w3.org>
as suggested, verbally on the telcon: <wsoap:code value="xs:QName" subcodes="list of xs:QName" /> solves the problem of the first value having a different meaning to the rest of the list. Paul -----Original Message----- From: www-ws-desc-request@w3.org [mailto:www-ws-desc-request@w3.org]On Behalf Of Roberto Chinnici Sent: 04 May 2004 01:05 To: Sanjiva Weerawarana Cc: www-ws-desc@w3.org Subject: Re: proposal: minor syntax improvement for soap fault bindings 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 Thursday, 6 May 2004 12:39:36 UTC