MessageOrder is not listed, below, as part of the Request, but it is talked
about in section 3.2 of the most recent version of the spec. I assume the
working draft has not been updated with all the results from the F2F. I
think this is a mistake to have some of the capabilities defined in one
header (the Request header has AckReq and DupElim), but other behavior
coming from the MessageHeader (if the SequenceNumber is present, Ordering is
enabled).
Also, the spec (sec 3.3) says that RefToSequenceNumber is REQUIRED when the
original message was guaranteed message ordering. Does this mean it is
OPTIONAL/REQUIRED/DISALLOWED when message-ordering is not being used? I
assume it is DISALLOWED, but this needs to be clarified.
Scott
> -----Original Message-----
> From: Sunil Kunisetty [mailto:]
> Sent: Tuesday, September 16, 2003 12:00 PM
> To:
> Subject: [wsrm] [Rel-87]schema for Headers
>
>
>
> All -
>
> Before Scott & I work on the Schema for the RM Headers, we
> would like to
> know that this is what we have decided so far. Please
> correct us if we missed
> something or didn't capture any resolution properly.
>
> -Sunil
>
> --------------------------------------------------------------
> -------------------------------
> MessageHeader
> - GroupId - "mid URI" scheme from RFC2392 - Mandatory
> - SequenceNo - unsignedLong - Long
> -- status attribute - xsd:string - Begin, Continue, End
> - TimeStamp - UTC - Mandtory
> - ExpiryTime - UTC - Mandatory
> - ReplyPattern - xsd:string - Optional
> - replyTo attribute - uri - Optional
>
> Request
> - AckRequested - Optional
> - DuplicateElimination - Optional
>
> Response
> RefToGroupId - "mid URI" scheme from RFC2392 - Mandatory
> RefToSequenceNo - unsignedLong - Optional
>
> Fault - QName - Mandatory
>
> Namespace:
>
> urn:oasis:names:tc:wsrm:schema:1.1:SOAP1.1
> urn:oasis:names:tc:wsrm:schema:1.1:SOAP1.2
>
> URL Location:
>
http://www.oasis-open.org/committees/wsrm/schema/1.1/SOAP1.1
http://www.oasis-open.org/committees/wsrm/schema/1.1/SOAP1.2
----------------------------------------------------------------------------
---------------------
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.ph
p.
