OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ws-rx message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: [ws-rx] Issue i013 - proposed text changes (typo fixed)


Thank you Doug.  This is exactly the kind of well-formulated change proposal that I was looking for.

 

/paulc

Paul Cotton, Microsoft Canada
17 Eleanor Drive, Nepean, Ontario K2E 6A3
Tel: (613) 225-5445 Fax: (425) 936-7329
mailto:pcotton@microsoft.com

 


From: Doug Davis [mailto:dug@us.ibm.com]
Sent: August 8, 2005 6:51 AM
To: ws-rx@lists.oasis-open.org
Subject: [ws-rx] Issue i013 - proposed text changes (typo fixed)

 


fixed a typo.
-Doug
__________________

Per my AI on the last conference call here are the list of changes I propose for the resolution of issue i013:

In the WS-RM Policy doc:

After line 173, add to the normative outline:
        <wsrm:MaxMessageNumber Number="xs:unsignedLong" ... /> ?

After line 202, add to the more verbose section of the normative outline:
        /wsrm:RMAssertion/wsrm:MaxMessageNumber
        A parameter that specifies the maximum message number that the RM Destination will accept.  If omitted, the default value of the maximum unsigned long will be assumed.

        /wsrm:RMAssertion/wsrm:MaxMessageNumber/@Number
        The maximum message number.

After line 434, add to the schema:
        <xs:element name="MaxMessageNumber" minOccurs="0" >
          <xs:complexType>
            <xs:attribute name="Number"
                          type="xs:unsignedLong" use="required" />
            <xs:anyAttribute namespace="##any" processContents="lax" />
          </xs:complexType>
        </xs:element>

thanks
-Doug



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]