- From: <bugzilla@wiggum.w3.org>
- Date: Fri, 13 Nov 2009 06:52:15 +0000
- To: public-ws-resource-access-notifications@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8277 Summary: editorial: Section 5 "Notifications" Product: WS-Resource Access Version: PR Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: Eventing AssignedTo: public-ws-resource-access-notifications@w3.org ReportedBy: gilbert.pilz@oracle.com QAContact: public-ws-resource-access-notifications@w3.org 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." -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. You are the assignee for the bug.
Received on Friday, 13 November 2009 06:52:25 UTC