This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Section 4.4 Unsubscribe, describes the message to be returned if an Unsubscribe message is accepted. However it does not mention what to return if the Unsubscribe request is not accepted. Proposal: Add a new fault to section 6. 6.15 UnableToUnsubscribe This fault is generated when an unsubscribe request has failed. [Code] s12:Sender [Subcode] wse:UnableToUnsubscribe [Reason] The Unsubscribe request has failed [Detail] none
just record my comment before forgetting it. Agree there should be a fault message for Unsubscribe, for example, when the subscription does not exist. However, in that case, the fault should be InvalidSubscription as proposed in Issue 7553 [1]. If we create an UnableToUnsubscribe fault, it would allow a service to fail a request with any reason beyond the listed ones. If that is the case, should we also add UnableToXXX to each request as well? Thanks. [1] http://www.w3.org/Bugs/Public/show_bug.cgi?id=7553
Latest proposal at http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Sep/0052.html.
consolidated with 7553 Resolution to 7553 will also resolve 7554