- From: Doug Davis <dug@us.ibm.com>
- Date: Tue, 6 Jan 2009 23:23:07 -0500
- To: public-ws-resource-access@w3.org
- Message-ID: <OFD782DB39.750FED91-ON85257537.000F41B3-85257537.001828C4@us.ibm.com>
WS-Transfer allows for multiple children in the SOAP Body of the GetResponse. The description of the GetResponse has the following (bolding is mine): /s:Envelope/s:Body/child::*[position()=1] The representation itself MUST be the initial child element of the SOAP:Body element of the response message. The presence of subsequent child elements is service-specific and MAY be controlled by the presence or extension-specific SOAP headers in the original request. The implication is that multiple children may appear. It is worth noting that the WSDL/XSD of the specification only allows for one child - however, in terms of precedence, the normative text overrides the WSDL/XSD - as noted in section 2.4: Normative text within this specification takes precedence over normative outlines, which in turn takes precedence over the XML Schema and WSDL descriptions. WS-I Basic Profile has the following requirement: R9981 An ENVELOPE MUST have exactly zero or one child elements of the soap:Body element. Proposal: Align the text of the GetResponse message with the WSDL/XSD by removing the text that implies more than one child my appear. thanks -Doug ______________________________________________________ STSM | Web Services Architect | IBM Software Group (919) 254-6905 | IBM T/L 444-6905 | dug@us.ibm.com
Received on Wednesday, 7 January 2009 04:23:46 UTC