- From: Jonathan Marsh <jonathan@wso2.com>
- Date: Fri, 16 Feb 2007 09:58:35 -0800
- To: "'Jean-Jacques Moreau'" <jean-jacques.moreau@crf.canon.fr>
- Cc: <www-ws-desc@w3.org>
OK, that makes sense, but I still think there's a hole, namely how to construct the "In" message when the content model is #any. The intent of CR120 was to allow #none, not to allow #any and #other to be bound to SOAP Response... Perhaps we simply make it explicit for SOAP Response that 'The {message content model} MUST be either #element or #none. The "In" message is empty when the content model is #none.' Jonathan Marsh - http://www.wso2.com - http://auburnmarshes.spaces.live.com > -----Original Message----- > From: Jean-Jacques Moreau [mailto:jean-jacques.moreau@crf.canon.fr] > Sent: Friday, February 16, 2007 7:57 AM > To: Jonathan Marsh > Cc: www-ws-desc@w3.org > Subject: Re: CR120 (was: Status: Editorial action items) > > Some more... > > Jonathan Marsh wrote: > > ---------- > > Re CR120, can you point me to where the fix has been made? I can't find > it where I expected it - the second sentence of 6.8.2. > > > I've implemented the fix in 5.10.4.2.2, i.e. set the value of "In" only > when the type is #element. (Hence, by implication, do nothing when #none.) > > My reading of 6.4.3, bullet 1.2: > > If the value is "#none" then the payload MUST be empty and the value > > of the corresponding serialization property ({http input > > serialization} or {http output serialization}) is ignored. > .. was that there was no other change to perform. > > Am I missing something? > > JJ.
Received on Friday, 16 February 2007 17:58:40 UTC