This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
The WS-ResourceTransfer specification introduces boxcarring or batching multiple operations within a single SOAP message. In general, boxcarring causes a lot of problems - especially with transactional rules, sequencing micro operations, fault handling, semantics of the SOAP Action URI - reduces to just "Do Stuff", etc. The SOAP specifications do not explain how boxcarring is performed. The WS-ResourceTransfer specification specifies an one-off boxcarring mechanism. Perhaps work associated with this feature would be better suited to a separate specification, where all the fine details can be worked out and the result can be used by many specs?
Highlights that RT should follow idempotency properties of T, then might depend on specification of restrictions as to frags permitted
http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Sep/0083.html proposes CWNA