Draft Resolution for issue 57

This issue is resolved by the SOAP binding to Email, as well as updates to
the Transport binding framework text.  Within the Transport Binding text,
recommendations are given regarding the use of SOAPAction as well as
transport based features:

Bindings MAY depend on state that is modeled as being outside of the SOAP
XML Infoset (e.g. retry counts), and MAY transmit such information to
adjacent nodes. For example, some bindings take a message delivery address
(typically URI) that is not within the envelope; the HTTP binding in Part
2[1] (see Using SOAP in HTTP <soap12-part2.html>) transmits an HTTP field
named SOAPAction that is not contained within the SOAP XML Infoset.



[1] http://www.w3.org/2000/xp/Group/xmlp-issues.html#x57
[2]
http://www.w3.org/2000/xp/Group/1/10/11/soap12-part1-f2fsnap.html#transpbind
framew
[3] http://www.w3.org/2000/xp/Group/2/02/emailbinding.html



Highland Mary Mountain

Intel Corporation
Distributed Systems Lab (DSL)
Corporate Technology Group (CTG)
(480) 552 - 3817

highland.m.mountain@intel.com

Received on Monday, 25 February 2002 10:06:36 UTC