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

Proposed text for issues rec20 and rec22 in XOP/MTOM

From: Herve Ruellan <herve.ruellan@crf.canon.fr>
Date: Mon, 26 Apr 2004 16:48:52 +0200
Message-ID: <408D2154.4060105@crf.canon.fr>
To: XMLP Dist App <xml-dist-app@w3.org>

Dear all,

Here is the proposed text for resolving issues rec20 and rec22, 
regarding XML 1.x, in XOP and MTOM.

See [1] for more information about these issues and their proposed 
resolution for the main SOAP 1.2 spec.

Cheers,


Hervé.

--- XOP ---

1.1 Terminology
<current>
- XOP Document - A serialization of the XOP Infoset using XML 1.0.
</current>

<proposed>
- XOP Document - A serialization of the XOP Infoset using any W3C 
recommendation-level version of XML.
</proposed>

---
2.1 MIME Multipart/Related XOP Packages
<current>
The root MIME part is the root part of the package, and MUST be an XML 
1.0 serialization [XML 1.0] of the XOP Infoset, as defined below, and 
MUST be identified with the [ TBD ] media type.
</current>

<proposed>
The root MIME part is the root part of the package, and MUST be a 
serialization of the XOP Infoset using any W3C recommendation-level 
version of XML (e.g., [XML 1.0] or [XML 1.1]), as defined below, and 
MUST be identified with the [ TBD ] media type.

Specifications building on the MIME Multipart/Related XOP Packages MAY 
restrict the version of XML allowed for serializing the XOP Infoset.
</proposed>

Rationale:
I think that for extensibility purpose, it is better to allow any XML 
serialization for the MIME Multipart/Related XOP Packages, while 
allowing for applications to restrict the serialization used.

---
4.1 Creating XOP Packages
<current>
6. Serialize the resulting XOP Infoset into the package as XML 1.0 and 
identify it as the root part according to the packaging mechanism's 
convention.
</current>

<proposed>
6. Serialize the resulting XOP Infoset into the package using any W3C 
recommendation-level version of XML (e.g., [XML 1.0] or [XML 1.1]) and 
identify it as the root part according to the packaging mechanism's 
convention.
</proposed>

Rationale:
I think that at this generic level, we want to allow any XML 
serialization. Each application of XOP can restrict the serialization 
available for it.

---
4.2 Interpreting XOP Packages
<current>
1. Parse the root part of the package as an XML 1.0 document to 
construct an XML Infoset (see [XML InfoSet]).
</current>

<proposed>
1. Parse the root part of the package as an XML document, according to 
the specification of any W3C recommendation-level version of XML (e.g., 
[XML 1.0] or [XML 1.1]), to construct an XML Infoset (see [XML InfoSet]).


--- 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.
</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.

---
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.

-------

[1] http://www.w3.org/mid/OFC9A3A98D.6EB0ED5D-ON85256E7D.00157D6E@lotus.com
Received on Monday, 26 April 2004 10:49:39 GMT

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