[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: [ebxml-msg] Re: SyncReply Module
David: My understanding is that the SyncReply module is equivalent to the renaming of the former Via module, minus the TraceHeaderList. As such, shouldn't it stay in Part II (Additional Features) and under the Multi-hop chapter? The syncReply attribute under QualityOfServiceInfo goes away because the use of syncReply between the From and To parties is governed by a static (not per pessage) parameter in the CPA. In the single-hop case, it should be sufficient to indicate in the CPA that sync reply is to be used, without explicitly including a SyncReply element in the SOAP header. Regards, -Arvola -----Original Message----- From: David Fischer <david@drummondgroup.com> To: ebXML Msg <ebxml-msg@lists.oasis-open.org> Date: Friday, November 16, 2001 3:59 PM Subject: [ebxml-msg] v1.09 This includes all the edits I have received including those decided upon at the F2F this week. I do not yet have a Conformance Clause or the new sub-section dealing with Signature Security (Galvin). Regards, David Fischer Drummond Group ebXML-MS Editor.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC