- From: Jacek Kopecky <jacek.kopecky@systinet.com>
- Date: Mon, 16 Feb 2004 10:14:05 +0100
- To: Sanjiva Weerawarana <sanjiva@watson.ibm.com>
- Cc: WS-Description WG <www-ws-desc@w3.org>, saikat.saha@commerceone.com
Sanjiva, personally I have no experience with such issues, perhaps Saikat could give us some details on the issues mentioned in http://groups.yahoo.com/group/soapbuilders/message/9761 . While I agree that inside the element WSDL puts in the SOAP Body it's XML Schema's job to specify whitespace handling, it's our SOAP binding that should specify this for the actual SOAP Body content, i.e. whether there can or cannot be whitespace *around* the message element. It can do that by saying that SOAP Body's type becomes a complex type with a sequence of exactly one of that element, deferring the whitespace issue back to XML Schema, but it can also directly specify what happens. Jacek Kopecky Systinet Corporation http://www.systinet.com/ On Mon, 2004-02-16 at 04:33, Sanjiva Weerawarana wrote: > "Jacek Kopecky" <jacek.kopecky@systinet.com> writes: > > > > it was noted on the soapbuilders list that there are some interop > > problems regarding whitespace handling in SOAP Body. > > Could you expand on what some of the issues were please? > > > I believe this is > > an issue for WSDL because for SOAP, whatever is in the Body, belongs to > > the application. > > > > WSDL describes in its SOAP binding what the Body will look like, > > therefore it probably should say something about whether whitespace > > characters can be children of the Body and how they are treated. > > > > I consider this an issue against the SOAP binding. > > Why? I thought that that's the role of XSD in WSDL .. to describe > the structure of what the soap:Body will look like; all WSDL does > is say "its that element." > > Sanjiva. > >
Received on Monday, 16 February 2004 04:14:10 UTC