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 8277 - Eventing: editorial: Section 5 "Notifications"
Summary: Eventing: editorial: Section 5 "Notifications"
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
Keywords: hasProposal
Depends on:
Reported: 2009-11-13 06:52 UTC by Gilbert Pilz
Modified: 2010-03-17 11:05 UTC (History)
1 user (show)

See Also:


Description Gilbert Pilz 2009-11-13 06:52:15 UTC
Section 5 "Notifications" begins with the following text:

"This specification does not constrain notifications because any message MAY be a notification.

However, if a subscriber wishes to have notifications annotated with unique SOAP header blocks then it MAY include reference parameters within the wse:NotifyTo element. These reference parameters will be processed as specified by [WS-Addressing 1.0 SOAP Binding]."

1.) What does it mean to say that "any message MAY be a notification"? Why is it necessary to point this out?

2.) The "However, . . ." is incongruous; seems like there was something there before that got removed.

3.) Why do we need to point out that reference parameters can be used? That's a given for anything that uses WS-Addressing.

Proposal: substitute both paragraphs with the following:

"Notifications are SOAP messages that are transmitted to the event sink as the result of a successful Subscribe operation."
Comment 1 Robert Freund 2010-03-17 11:05:03 UTC
resolved 2009-11-17 as proposed