Re: revised-ebMS V1.01 Editorial changes

[Colleen Evans <cevans@sonicsoftware.com>]

Hi Iwasa,
I have incorporated your suggested text (along with the clarification
provided by Shimamura in the referenced archived email) in the V1.02 version
distributed to the list this afternoon. See section 7.4.8 on page 33, line
numbers 1265 through 1280.  I hope it accurately reflects the use of
SequenceNumber.

Best regards,
Colleen

iwasa wrote:

>
> I have some feedback to the updated spec as follows:
>
> [Issue63, 64]
> As I made comments on the teleconference,
> the proposed sentence doesn't solve the problem. Because
> it doesn't say when SequenceNumber is required.
>
> My proposed sentence for Line#1070-1074 is:
> --------------------------------------------
> The SequenceNumber element MUST appear
> when deliverySemantics has a value of
> OnceAndOnlyOnce and messageOrderSemantics
> has a value of Guaranteed. Otherwise, SequenceNumber
> MAY NOT appear. If deliverySemantics doesn't
> have a value of OnceAndOnlyOnce, SequenceNumber
> MUST NOT appear. If this criterion is not met,
> an error MUST be reported to the From Party MSH with
> an errorCode of Inconsistent and a severity of Error.
> -------------------------------------------
>
> This explanation is based on the original sentence,
> and made clarification as we concluded.
>
> The point here is:
>   - SequenceNumber MUST appear when:
>             deliverySemantics="OnceAndOnlyOnce" and
>             messageOrderSemantics="Guaranteed"
>   - Otherwise it is NOT REQUIRED. (And spec doesn't
>      preclude to put sequenceNumber, when
>      deliverySemantics="OnceAndOnlyOnce")
>   - SequenceNumber MUST NOT appear when
>      deliverySemantincs="BestEffort"
>
> This was discussed already, and came to a conclusion.
> See :
>  <http://lists.ebxml.org/archives/ebxml-transport/200103/msg00104.html>.
>
> Iwasa
>
> ----- Original Message -----
> From: "Colleen Evans" <cevans@sonicsoftware.com>
> To: "ebXML Msg" <ebxml-msg@lists.oasis-open.org>
> Sent: Monday, September 24, 2001 3:34 PM
> Subject: revised-ebMS V1.01 Editorial changes
>
> > Based on today's TC call, there are a few changes required
> > to the draft version I sent out earlier (ebMS V1.01 draft 21
> > Sep 2001).  The attached spec (ebMS V1.01 draft 24 Sep 2001)
> > includes those modifications. The accompanying issues list
> > documents what evolved on today's call, resulting in the
> > changes to the draft spec.  Effected issues are highlighted.
> >
> > After Thursday's deadline for comment (9/27), I will accept
> > changes in the document, and add the T1 modifications from
> > Ralph.  Then we can start the whole process over again next
> > week at the f2f with the remaining issues.
> >
> > Colleen
> >
> >

--
Colleen Evans
Principal Product Manager
Sonic Software Corporation
phone:  720 480-3919 or 303 791-3090
email:  cevans@sonicsoftware.com
website:  http://www.sonicsoftware.com