OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-msg message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: RE: [ebxml-msg] SOAP 1.2 MTOM and ebMS v3

Microsoft is proposing this for IHE/XDS registry web service interfacing.
Perhaps we should invite them to discuss on conference call?

"The way to be is to do" - Confucius (551-472 B.C.)

-------- Original Message --------
Subject: Re: [ebxml-msg] SOAP 1.2 MTOM and ebMS v3
From: Ric Emery <remery@us.axway.com>
Date: Thu, April 05, 2007 12:28 pm
To: "David RR Webber (XML)" <david@drrw.info>, <ian.c.jones@bt.com>
Cc: <ebxml-msg@lists.oasis-open.org>

SOAP with attachments is expressly supported in the ebMS 3.0 core features. MTOM support is not mentioned.
I would be concerned with MTOM usage since there is no mention of MTOM in the ebMS 3.0 spec. My opinion is that it would be problematic for an MSH to utilize MTOM without the specification outlining its use.

If MTOM usage is important the user base we should be able to discuss its use in a future addendum or part 2 of the ebMS 3 spec. Is there a reason that you think MTOM should be an option?


On 4/5/07 9:04 AM, "David RR Webber (XML)" <david@drrw.info> wrote:

How does this relate to ebMS v3 ?
Is it just transparent - in that if two ebMS are using SOAP 1.2 with MTOM - then they can exchange transmissions accordingly - but controlled by the CPA and ebMS settings?  Or is MTOM re-inventing ebMS routing and handling and therefore likely to cause chaos?
Trying to figure out the implications here!
Thanks, DW

"The way to be is to do" - Confucius (551-472 B.C.)

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]