Re: Resolution of issue Rec39


I believe your note accurately reflects the decision we made a couple of 
weeks ago.  That was a decision I actively supported.  As we discussed on 
the 12/14 telcon, I've since somewhat changed my position and new think it 
may be in the best interest of the community to focus on the ambiguity in 
the existing rec, and allow ourselves to make the envelope (but not the 
whole response) in the Req/Resp optional, and to document that in an 
erratum  (see [1]).  So, I suppose that's a request to reopen the just 
closed Rec39.  The alternative, which I think I would also support, would 
be to publish a new (and arguably "incompatible") SOAP 1.2 2nd edition, 
SOAP 1.2b, SOAP 1.3 with the new feature and take it through a full CR/PR 

Sorry for any confusion caused by my change of position.  Thank you.



Noah Mendelsohn 
IBM Corporation
One Rogers Street
Cambridge, MA 02142

Anish Karmarkar <>
Sent by:
12/14/2005 12:48 AM
        cc:     "Xml-Dist-App@W3. Org" <>, (bcc: Noah 
        Subject:        Resolution of issue Rec39

At the 07-dec-2005 concall the XMLP WG decided to close issue Rec39 [1] 
by including the requirement for an optional-response/empty HTTP 
entity-body in the new MEP/binding work that the WG is undertaking.

The WG also decided that per the existing binding defined in SOAP 1.2 
[2], it is not possible to send back an empty HTTP entity body for the 
non-fault case when using the request-response MEP. The reasons for this 
are listed in the email at [3].

-Anish Karmarkar
on behalf of XMLP WG

PS: as the person who raised this issue, I'm happy with the resolution.


Received on Thursday, 15 December 2005 23:13:33 UTC