W3C home > Mailing lists > Public > public-ws-resource-access@w3.org > September 2009

Re: Issue 7553: Eventing - GetStatus Fault Message (action item 102)

From: Gilbert Pilz <gilbert.pilz@oracle.com>
Date: Thu, 17 Sep 2009 14:41:32 -0700
Message-ID: <4AB2AD0C.1060408@oracle.com>
To: Katy Warr <katy_warr@uk.ibm.com>
CC: public-ws-resource-access@w3.org
+1

On 9/17/2009 9:47 AM, Katy Warr wrote:
>
> Following discussions from Tuesday's call, here's a proposed fix for 
> http://www.w3.org/Bugs/Public/show_bug.cgi?id=7553 action item 102 
> http://www.w3.org/2002/ws/ra/tracker/actions/102
>
> 1) Add text to 4.3 GetStatus:
> "If the event source is unable to perform the request because the 
> subscription is not valid, the request MUST fail and the subscription 
> manager MUST generate a wse:InvalidSubscription fault.""
>
> 2) Add the following fault section:
>
> 6.13 InvalidSubscriotion
> This fault is generated when a request specifies a subscription that 
> is not valid.
> [Code]           s12:Sender
> [Subcode]   wse:InvalidSubscription
> [Reason]     The subscription is not valid
> [Detail]         <wse:SubscriptionExpired>?
>                        Optional.
>
> 3) Extend section 6.1 to correctly detail the subscriptionExpired 
> element:
>
> 6.1 Fault Detail Elements
> The following elements are used to convey additional information in 
> the faults.
> 6.1.1 RetryAfter
> /wse:RetryAfter
>     This element (whose content is of type xs:unsignedLong) is a 
> suggested minimum duration in milliseconds to wait before 
> retransmitting the message. Omission of this element indicates that a 
> retry is never likely to succeed.
> /wse:RetryAfter/@any
>     Optional extensibility attributes that do not affect processing.
> 6.1.2 SubscriptionExpired
> /wse:SubscriptionExpired
>     This empty element MAY be used by a subscription manager to 
> indicate that it was unable  to process a request because the 
> subscription to which the request refers has expired.  
> This is an optional element.  Implementations are not required to 
> retain information about expired subscriptions.
> /wse:SubscriptionExpired/@any
>     Optional extensibility attributes that do not affect processing
>
> 4) The current wording in the spec implies that expired subscriptions 
> are valid.  This contradicts the above usage of faults (where expired 
> subscriptions are not valid).  Replace the following text in 4.3 
> GetStatus:
> "If the subscription is valid and has not expired, the subscription 
> manager MUST reply with a response of the following form: "
> with
> "A subscription is not valid if it has expired.  If the subscription 
> is valid, the subscription manager MUST reply with  a response of the 
> following form: "
>
>
> ------------------------------------------------------------------------
>
> /
> /
>
> /Unless stated otherwise above:
> IBM United Kingdom Limited - Registered in England and Wales with 
> number 741598.
> Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 
> 3AU/
>
>
>
>
>
>


Received on Thursday, 17 September 2009 21:42:48 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 18 December 2010 18:18:13 GMT