David, On Wed, 05 Dec 2001 07:49:32 -0600 David Fischer <
david@drummondgroup.com> wrote: > Dan, > > There are other kinds of RM. We are explicitly excluding them in the case of > MessageOrder? No, my change proposal for MessageOrder section does not exclude other kinds of RM (reliable communication protocols). Please see my change proposal again: > Date: Wed, 05 Dec 2001 16:09:17 +0900 > From: SHIMAMURA Masayoshi <
shima.masa@jp.fujitsu.com> > Subject: [ebxml-msg] Re: Comments on the 1.09 about MessageOrder > In-reply-to: <
NFBBIIHJNFIEBFENACIJKEKECDAA.david@drummondgroup.com > > To: David Fischer <
david@drummondgroup.com>, >
ebxml-msg@lists.oasis-open.org > Message-id: <
20011205153549.158E.SHIMA.MASA@jp.fujitsu.com > ... > P. 49, Line 2009 > This line should be deleted, and insert following sentences after > line 2016. > > When the value of the messageOrderSemantics attribute is set to > guaranteed , delivery behavior Once-and-Only-Once MUST be used. > In the specification, the Once-and-Only-Once delivery behavior > means that two conditions below are satisfied at same time: > > 1) No lost message by one of following two mechanisms > - Reliable messaging described in 7.5 ebXML Reliable > Messaging Protocol . It means that the messages includes > AckRequested element or Acknowledgment element. > - Reliable communication protocol > 2) No duplicate message by the mechanism described in 7.5.6 > Duplicate Message Handling . It means that > duplicateElimination attribute is set to true. Regards, -- SHIMAMURA Masayoshi <
shima.masa@jp.fujitsu.com> TEL:+81-45-476-4590(ext.7128-4241) FAX:+81-45-476-4726(ext.7128-6783) Planning Dep., Strategic Planning Div., Software Group, FUJITSU LIMITED