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

Re: Proposal for describing MIME serialization/deserialization

From: <noah_mendelsohn@us.ibm.com>
Date: Wed, 7 Jan 2004 12:38:41 -0500
To: Jacek Kopecky <jacek.kopecky@systinet.com>
Cc: Herve Ruellan <herve.ruellan@crf.canon.fr>, XMLP Dist App <xml-dist-app@w3.org>
Message-ID: <OFCA010782.B1C0D322-ON85256E14.0057CBEB@lotus.com>

Jacek Kopecky proposes:

> When this feature is used in combination with the SOAP
> Request-Response Message Exchange Pattern (ref) or the
> SOAP Response Message Exchange Pattern (ref) described
> in SOAP 1.2, Part 2 (ref), the data model generated for
> the SOAP message MUST be represented in the value of
> the property corresponding to the sent SOAP message,
> i.e.,
> http://www.w3.org/2003/05/soap/mep/OutboundMessage or
> http://www.w3.org/2003/05/soap/mep/InboundMessage. Similar
> rules should be applied for other MEPs, as appropriate.

I don't think we can quite say it this way, as this conflicts with the 
definition of the property as an Infoset.  I think what we need is in 
rough outline:

the Outbound message propoerty is the Infoset derived from the supplied DM 
per Appendix A.1 (Mapping between Infosets and Data Models).

On receipt, the MTOM DM is derived from the InboundMessage per Appendex 
A.2, where the appendices as are in the MTOM DM Editors' copy [1].

Slightly better wording is needed, but I think this is the idea we want.

Noah

[1] 
http://www.w3.org/2000/xp/Group/3/06/Attachments/OptimizationMechanism.html#MappingInfosets


--------------------------------------
Noah Mendelsohn 
IBM Corporation
One Rogers Street
Cambridge, MA 02142
1-617-693-4036
--------------------------------------
Received on Wednesday, 7 January 2004 12:46:34 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 5 February 2014 22:28:13 UTC