8169 2009-11-03 21:22:01 +0000 Eventing: dup WSA refP text 2009-12-08 22:23:00 +0000 1 1 1 Unclassified WS-Resource Access Eventing LC PC Windows XP CLOSED REMIND P2 normal --- 1 dug dug public-ws-resource-access-notifications oldest_to_newest 29284 0 dug 2009-11-03 21:22:01 +0000 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. 29424 1 dug 2009-11-06 23:12:27 +0000 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. 29425 2 bob 2009-11-06 23:13:38 +0000 resolved with comment #1