SequenceNumber element

[Scott Werden <scottw@wrq.com>]

I propose that SequenceNumber element be required, but the text say that it
will be ignored (or perhaps we can say it must be empty) except for when
message ordering is being used. It makes header processing a little cleaner
and certainly makes the schema more precise. Having a header element
required or disallowed depending on the presence of an element (the
DuplicateElimination element) in a different header block seems a little
strange to me. 

Scott


> -----Original Message-----
> From: Sunil Kunisetty [mailto:Sunil.Kunisetty@oracle.com] 
> Sent: Tuesday, September 16, 2003 12:00 PM
> To: wsrm@lists.oasis-open.org
> 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.