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
