- From: <noah_mendelsohn@us.ibm.com>
- Date: Wed, 22 Aug 2007 12:08:23 -0400
- To: harbhanu@huawei.com
- Cc: ranjit@huawei.com, xml-dist-app@w3.org
You are correct that in principle SOAP envelopes can be transmitted in a
wide variety of forms, and that for interoperability there is a need to
know in advance what those form(s) will be. In SOAP, this is addressed
primarily by having the specifications for having particular SOAP Protocol
Bindings [1] document the particular representation used for the SOAP
envelope. In the case of SOAP 1.2, the binding included with the
Recommendation is very widely deployed, and it specifies [2] that the
envelope will be of media type application/soap+xml [3]. The
specification for that media type says: "This document defines the
"application/soap+xml" media type which can be used to describe SOAP 1.2
messages serialized as XML 1.0." So, when you use the typical SOAP HTTP
binding, the encoding is as an ordinary XML 1.0 document, transported
using HTTP.
Note that other representations can be used if the binding supports them.
For example: MTOM [4] provides for optimization of certain information
that is better represented as large binary objects than as text. When
MTOM is used with the SOAP http binding, the HTTP Content-type is used to
signal the use of the MTOM representation.
Noah
[1] http://www.w3.org/TR/soap12-part1/#transpbindframew
[2] http://www.w3.org/TR/soap12-part2/#httpmediatype
[3] http://www.ietf.org/rfc/rfc3902.txt
[4] http://www.w3.org/TR/soap12-mtom/
--------------------------------------
Noah Mendelsohn
IBM Corporation
One Rogers Street
Cambridge, MA 02142
1-617-693-4036
--------------------------------------
harbhanu <harbhanu@huawei.com>
Sent by: xml-dist-app-request@w3.org
08/22/2007 07:48 AM
Please respond to harbhanu
To: xml-dist-app@w3.org
cc: ranjit@huawei.com, (bcc: Noah Mendelsohn/Cambridge/IBM)
Subject: SOAP: Query regarding different infoset
realisations.
Hi all,
While going through the SOAP specification I found that SOAP specification
always describes at the level of XML INFOSET
So, when I say that we receive a SOAP message that message can be an XML
1.0 document, or any other XML Infoset representation (realization)….
My doubt is that how will the server specify the types of encoding (If I
may say so, for different XML Infoset realization) that if supports.
Please let me know about your comments..
Regards,
Harbhanu
Received on Wednesday, 22 August 2007 16:08:23 UTC