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

[Bug 8169] New: Eventing: dup WSA refP text

From: <bugzilla@wiggum.w3.org>
Date: Tue, 03 Nov 2009 21:22:01 +0000
To: public-ws-resource-access-notifications@w3.org
Message-ID: <bug-8169-2780@http.www.w3.org/Bugs/Public/>

           Summary: Eventing: dup WSA refP text
           Product: WS-Resource Access
           Version: FPWD
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Eventing
        AssignedTo: public-ws-resource-access-notifications@w3.org
        ReportedBy: dug@us.ibm.com
         QAContact: public-ws-resource-access-notifications@w3.org

Section 5 says:
However, if a subscriber wishes to have notifications specifically marked, it
MAY specify literal SOAP header blocks in the Subscribe request, in the
element; per WS-Addressing [WS-Addressing], the event source MUST include each
such literal SOAP header block in every notification sent to the endpoint
addressed by /s:Envelope/s:Body/wse:Subscribe/wse:Delivery/wse:NotifyTo. 

Saying that the NotifyTo can be annotated with extra refP's is ok, but
I'm not comfortable with repeating the normative language of WSA where it
talks about copy refP into soap headers.

change it to:
However, if a subscriber wishes to have notifications annotated with unique
SOAP header blocks then it MAY includes reference parameters within the
wse:NotifyTo element.

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 Tuesday, 3 November 2009 21:22:02 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:06:36 UTC