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 8169 - Eventing: dup WSA refP text
Summary: Eventing: dup WSA refP text
Status: CLOSED REMIND
Alias: None
Product: WS-Resource Access
Classification: Unclassified
Component: Eventing (show other bugs)
Version: LC
Hardware: PC Windows XP
: P2 normal
Target Milestone: ---
Assignee: Doug Davis
QA Contact: notifications mailing list for WS Resource Access
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-11-03 21:22 UTC by Doug Davis
Modified: 2009-12-08 22:23 UTC (History)
0 users

See Also:

Attachments

Description Doug Davis 2009-11-03 21:22:01 UTC 
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 /s:Envelope/s:Body/wse:Subscribe/wse:Delivery/wse:NotifyTo/wsa:ReferenceParameters 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.

Proposal:
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.
Comment 1 Doug Davis 2009-11-06 23:12:27 UTC 
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.
Comment 2 Robert Freund 2009-11-06 23:13:38 UTC 
resolved with comment #1