W3C home > Mailing lists > Public > xml-dist-app@w3.org > May 2004

MTOM Text for issues rec20 and rec22

From: Herve Ruellan <herve.ruellan@crf.canon.fr>
Date: Fri, 14 May 2004 17:00:13 +0200
Message-ID: <40A4DEFD.3040208@crf.canon.fr>
To: XMLP Dist App <xml-dist-app@w3.org>

Dear all,

Here is an updated proposal for resolving issues rec20 and rec22 
regarding XML 1.x in MTOM.

This proposal builds upon [1], [2] and [3] and the decision to support 
only XML 1.0 in SOAP.

Note that this proposal is very similar to [1], the only change being to 
remind, in 3.1, that a SOAP message infoset must be serializable as XML 1.0.

Cheers,

Hervé.

[1] http://lists.w3.org/Archives/Public/xml-dist-app/2004Apr/0022.html
[2] http://lists.w3.org/Archives/Public/xml-dist-app/2004Apr/0026.html
[3] http://lists.w3.org/Archives/Public/xml-dist-app/2004Apr/0028.html

--- MTOM ---
3. An Optimized MIME Multipart Serialization of SOAP Messages
3.1 Introduction
<current>
The Optimized MIME Multipart Serialization provides the basis for an
implementation of the Abstract Transmission Optimization Feature by
describing how to serialize a SOAP envelope in an optimized way, using
the [XOP] format and a MIME Multipart/Related packaging ([RFC 2387]).
</current>

<proposed>
The Optimized MIME Multipart Serialization provides the basis for an
implementation of the Abstract Transmission Optimization Feature by
describing how to serialize a SOAP envelope in an optimized way, using
the [XOP] format and a MIME Multipart/Related packaging ([RFC 2387]).

More specifically, the SOAP envelope Infoset is transmitted as a MIME
Multipart/Related XOP Package (see [XOP], 2.1 MIME Multipart/Related XOP
Packages). Any W3C recommendation-level version of XML is allowed for
storing the XOP Infoset created from the SOAP envelope Infoset into the
MIME Multipart/Related XOP Package, however note that the SOAP envelope 
Infoset MUST be serializable as XML 1.0.
</proposed>

Rationale:
Two changes are proposed here.
The first one is to link the Optimized MIME Multipart Serialization of
SOPA Messages to the MIME Multipart/Related XOP Packages specification.
The second one is to state that, at this level, any version of XML is
allowed into the XOP Package, but to remind that the SOAP envelope 
Infoset must be valid XML 1.0.

---
4. HTTP Transmission Optimization Feature
4.3 Implementation
<current>
The HTTP Transmission Optimization Feature uses the Optimized MIME
Multipart Serialization (see 3. An Optimized MIME Multipart
Serialization of SOAP Messages) for implementing the Abstract
Transmission Optimization Feature. On the sending side, this feature
serializes the SOAP message as described in 3.2 Serialization of a SOAP
message and puts the resulting MIME Multipart/Related package in the
HTTP body. On the receiving side, this feature extracts the MIME
Multipart/Related package from the HTTP body and deserializes as
described in 3.3 Deserialization of a SOAP message.
</current>

<proposed>
The HTTP Transmission Optimization Feature uses the Optimized MIME
Multipart Serialization (see 3. An Optimized MIME Multipart
Serialization of SOAP Messages) for implementing the Abstract
Transmission Optimization Feature. On the sending side, this feature
serializes the SOAP message as described in 3.2 Serialization of a SOAP
message and puts the resulting MIME Multipart/Related XOP Package in the
HTTP body. On the receiving side, this feature extracts the MIME
Multipart/Related XOP Package from the HTTP body and deserializes as
described in 3.3 Deserialization of a SOAP message.

When using the HTTP Transmission Optimization Feature to transmit a SOAP
Envelope Infoset, the XOP Infoset built from the SOAP Envelope Infoset
MUST be serialized as XML 1.0 in the root part of the MIME
Multipart/Related XOP Package.
</proposed>

Rationale:
Our current HTTP Binding only allows XML 1.0. Keep this restriction when
using XOP Packages in the HTTP Binding.

---
4.3.1.1 Init
<current>
The XOP package is constructed as described in 3. An Optimized MIME
Multipart Serialization of SOAP Messages with the following restriction:
   * Each optimized Node MUST generate exactly one extracted binary part
in the resulting package, i.e., extracted binary parts MUST NOT be
referenced with more than one xop:Include in the SOAP message part.
   * Each MIME part that is refered to by xop:Include MUST have a
Content-Tranfer-Encoding header field.
</current>

<proposed>
The XOP package is constructed as described in 3. An Optimized MIME
Multipart Serialization of SOAP Messages with the following restriction:
   * The XOP Infoset MUST be serialized using XML 1.0 in the root part of
the package.
   * Each optimized Node MUST generate exactly one extracted binary part
in the resulting package, i.e., extracted binary parts MUST NOT be
referenced with more than one xop:Include in the SOAP message part.
   * Each MIME part that is refered to by xop:Include MUST have a
Content-Tranfer-Encoding header field.
</proposed>

Rationnale:
Restate what is added in 4.3.
Received on Friday, 14 May 2004 11:01:37 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:59:18 GMT