Issue 106 Alternative Proposal - Rough idea

As an alternative to the proposal I made in http://lists.oasis-open.org/archives/ws-rx/200603/msg00185.html the following will also satisfy my concerns:

Since implementations may have various methods of delivering messages to the application and may or may not include some sort of persistence, it may be instructive to annotate the ack sequence with information indicating which messages were actually delivered or otherwise safely transferred to the RMD.

Sequence acknowledgements indicate simply that the RMD layer has received the message, and provides no information concerning their subsequent processing or delivery. SequenceAcknowlwdgement/Final received upon sequence closure may therefore provide ambiguous information to the RMS concerning the potential deliverability or delivery status of received messages based in part on message ordering contracts that may exist between the RMD and the application which are invisible to the RMS.

What is proposed is the inclusion of two additional attributes to the SequenceAcknowledgement/AcknowledgementRange element that would define message upper and lower bound ranges that have been delivered by the RMD to the application

A partial proposal is contained in the attached pdf based on CD03.

Please see the insertions in lines 560 and 603.

If this proposal is accepted, then the exemplar in lines 570-580 would need to be expanded as well as schema.

ws-rx message