- From: Sanjiva Weerawarana <sanjiva@watson.ibm.com>
- Date: Tue, 22 Jul 2003 02:02:28 +0600
- To: "Savas Parastatidis" <Savas.Parastatidis@newcastle.ac.uk>, "Christopher B Ferris" <chrisfer@us.ibm.com>
- Cc: <www-ws-desc@w3.org>, <www-ws-desc-request@w3.org>
"Christopher B Ferris" <chrisfer@us.ibm.com> writes:
>
> Not sure I would agree... WS-I Basic Profile 1.0 has constrained SOAP1.1
> such that there must be but a single
> child element of the SOAP:Body element. I am not convinced that this
> constraint will be changed for SOAP1.2.
Hey, excellent!
If WS-I BP has already outlawed multiple child elements, then why
would we do @body at all?? We're just setting up for profiling to
say "only use @element, never use @body"!!!
Now I have a basis for arguing that we should only do @element. Note
that that makes the syntax very natural and simple:
<operation name="ncname">
<input [body="qname-of-elem"] [headers="list-of-qnames-of-elems"]/>
<output [body="qname-of-elem"] [headers="list-of-qnames-of-elems"]/>
</operation>
Clearly at least one of @body or @headers is required.
Sanjiva.
Received on Monday, 21 July 2003 16:02:48 UTC