This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 8286 - Eventing: description of Subscription End ambiguous
Summary: Eventing: description of Subscription End ambiguous
Status: CLOSED REMIND
Alias: None
Product: WS-Resource Access
Classification: Unclassified
Component: Eventing (show other bugs)
Version: FPWD
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Gilbert Pilz
QA Contact: notifications mailing list for WS Resource Access
URL:
Whiteboard:
Keywords: hasProposal
Depends on:
Blocks:
 
Reported: 2009-11-13 21:44 UTC by Gilbert Pilz
Modified: 2010-03-17 11:09 UTC (History)
1 user (show)

See Also:


Attachments

Description Gilbert Pilz 2009-11-13 21:44:29 UTC
Section 4.5 "Subscription End" starts with the following paragraph:

"If the event source terminates a subscription unexpectedly, SubscriptionEnd SOAP message SHOULD be sent to the endpoint reference indicated when the subscription was created (see 4.1 Subscribe). This endpoint reference MUST refer to an endpoint that supports the SubscriptionEndPortType portType. The message MUST be of the following form:"

The SHOULD in this sentence is ambiguous. Does it refer to the act of transmitting the message or does it refer to where the message is transmitted? In both cases this should be a "MUST"; the SubscriptionEnd message MUST be transmitted, and it MUST be transmitted to the endpoint referenced by the EndTo EPR.

The sentence "This endpoint reference MUST refer to an endpoint that supports the SubscriptionEndPortType portType" is inappropriate and redundant; this is a constraint on the event sink, not the event source. This same constraint is already documented in the description of /wse:Subscribe/wse:EndTo.

Proposal: replace the above paragraph with the following:

"If the event source terminates a subscription unexpectedly and the wse:EndTo EPR was present in the Subscribe message for that subscription (see 4.1 Subscribe), the SubscriptionEnd message MUST be sent to the endpoint referenced by that EPR. The message MUST be of the following form:"
Comment 2 Robert Freund 2010-01-19 21:08:12 UTC
resolved with proposal in comment 1