Closing Rel-88

["iwasa" <kiwasa@jp.fujitsu.com>]

I think Rel-88 can be closed, since:
    - RefToMessageId was replaced with
      RefToGroupId and RefToSequenceNumber.
    - The following text was added in the spec at 3.1.1.
       "This REQUIRED element is to identify a sequence
        of messages, where each sequence is of length 1
        or more."
    - A new issue Rel-98 was raised for proposal 4) below.

Thanks,

Iwasa

--
REL-88 Spec  meta Design Completed Sunil Kunisetty Sunil Kunisetty

Title: Change RefToMessaageId to RefToGroupId/RefToSequenceNumber
Description: Change to have consistency with changes
made to MessageId into GroupId/SequenceNo.

Proposal:
Change RefToMessaageId to RefToGroupId/RefToSequenceNumber

Agreement to replace RefToMessageID with two new elements:

RefToGroupID
RefToSequenceNo

Four alternative proposals:
1) As Sunil suggested above: Move sequenceNo sub
    element from Message header to Request:MessageOrder
    sub element.
2) Un ordered messages use seq no = 0 always, in Message
    header (for use in Response/RefToSequenceNo), and
    messageOrder subelement is not present in Request header
    Ordered messages use seq no >=1 in Message header, and
   the messageOrder subelement is present in Request header
   element.
3) Un ordered message does not have seq no present in
    Message header (no RefToSequenceNo element present
    in Response header), and the messageOrder subelement
    is not present in Request header element.
    Ordered messages use seq no >= 0 in Message header, and
    the messageOrder subelement is present in Request header element.
4) same as 3, except move messageOrder status attribute to
    be attribute of sequence number element, and remove
    messageOrder element.

Meeting consensus on alternative 4) above.

Add text to clarify that:
Group ID is to identify a sequence of messages, where each sequence is of
length 1 or more.

Resolution: Accept proposal
--