Re: [wsrm] Fix for Message ID and Sequence Number sections

[Sunil Kunisetty <sunil.kunisetty@oracle.com>]

 
 Tom,

 While I've some specific comments inlined below, I've a general comment about
 the tables in Section 3.0.

 I'd like to propose that we remove the Fault row from each of tables for
 elements for the following reasons:
 - We anyway explain the Faults in section 4. So this information is redundant
   and duplicate. The request came in when we didn't have elaborate Section 4.
 - Not every Fault happens because of Header elements
- Some elements can cause more than one Fault because of sub-elements or
   attributes. For ex., a MessageHeader element can cause InvalidMessageParameters
   fault or InvalidReplyPattern fault or InvalidMessageId etc. WHile some such nested
   faults are captured, all of them are not.

Tom Rutt wrote:

I propose the attached changes for sections 3.1.1 and 3.1.2 (

This change involves:
- nesting of the existing 3.1.2 inside 3.1.1.
- the proper use of MUST, and MAY for element and attribute inclusion, and
- moving the staement on presence of group termination parameters to a 
more proper location.

Tom Rutt

-- 
----------------------------------------------------
Tom Rutt                email: tom@coastin.com; trutt@fsw.fujitsu.com
Tel: +1 732 801 5744          Fax: +1 732 774 5133

---

3.1.1 MessageId Element

The sender MUST include the MessageId element MUST be present forina Reliable
 
 

Message, an Acknowledgment message, a Fault message and a PollRequest message. In a request message, the sender MUST include A request message MUST contain a groupId attribute and MAY contain either groupExpiryTime attribute or groupMaxIdleDuration attribute corresponding to the group termination parameters specified in section 2.5.1:

There are couple of editorial & technical mistakes in it. Here is a reworded one:

The sender MUST include the  MessageId element for  a Reliable Request Message, an Acknowledgment message, a Fault message and a Poll Request message. This element MUST contain a groupId attribute
 
 
 

oa groupId attribute

Table 3 MessageId Element

 

Cardinality	1
Value	None
Attributes	groupId (RFC2396 *See 3.1.1 for details)
Child elements	SequenceNum
Fault	InvalidMessageId InvalidMessageParameters

(1) groupId attribute

The sender MUST include this attribute MUST be presentin the MessageId element. This attribute is to identify a sequence of messages, where each sequence is of length 1 or more. The sending RMP MUST use a distinct globally unique groupId for any distinct group of messages. Any group of messages will have a common groupId value. The syntax of this identification is URI, as defined in [RFC2396]. It is RECOMMENDED to use the Message-ID schema, as defined in [RFC2392].

First sentence seem to have extra MUST. Here is a reworded one:

The MessageId element MUST include a groupId attribute.This attribute is to identify a sequence of messages, where each sequence is of length 1 or more. The sending RMP MUST use a distinct globally unique groupId for any distinct group of messages. Any group of messages will have a common groupId value. The syntax of this identification is URI, as defined in [RFC2396]. It is RECOMMENDED to use the Message-ID schema, as defined in [RFC2392].
 

3.1.2 1.1 SequenceNum Element

The sender must include tThe SequenceNum element MUST be present for a Group of with more than one message.

Again an extra MUST here.

When a message includes a MessageOrder element, the SequenceNum element is used for guaranteeing the message order within the group of messages specified by the same groupId value. In other words, the sequence of numbered messages that the receiver node presents to the application MUST be sent in the same order as the sequence of numbered messages that the sender application has produced, within the group of messages having the same groupId value.

When the sender requests Guaranteed Message Ordering, the sender MUST use Guaranteed Message Delivery and Duplicate Elimination for that message as well. In particular, the sender MUST include both anAckRequested element and a DuplicateElimination element, as well as the MessageOrder element for Guaranteed Message Ordering.

This element includes the following attributes:

- agroupExpiryTime attribute

- agroupMaxIdleDuration attribute

- a number attribute attribute

- a status attribute

In a request message, the sender MAY include either agroupExpiryTime attribute or a groupMaxIdleDuration attribute corresponding to the group termination parameters specified in section 2.5.1:

If the MessageOrder element appears in the message sent, the receiver of the message MUST make messages available to the application layer only after all messages with lower number with the same groupId have been made available to the application. Example 6 illustrates some message fragments with SequenceNum element:

To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/wsrm/members/leave_workgroup.php.