7127 2009-07-21 21:11:53 +0000 Eventing: Can event information contained in notification be bound to soap:headers 2009-09-10 13:59:54 +0000 1 1 1 Unclassified WS-Resource Access Eventing FPWD PC Windows XP CLOSED WONTFIX P2 normal --- 1 tom tom public-ws-resource-access-notifications oldest_to_newest 26024 0 tom 2009-07-21 21:11:53 +0000 I think there is a general understanding the concept of “information content associated with event”. This is the “stuff” which is relevant to applications which want to receive the application level information for an event report which is conveyed in a notification. For example, the delivery “stuff’ , (eg. Notify to for the default “push” semantics) is not part of the application data for the event. This distinction is important when considering implementations which recieve a ws-eventing notification, and, subsequently, distribute the application relevant event information to downstream subscribers outside of the ws-eventing model (e.g, using JMS). Proposed solution: Define a concept of “event information” which is that part of the notification which conveys the application specific data associated with the event. Have the spec clarify that this event information MUST not be bound to soap:headers. 27013 1 bob 2009-09-10 13:59:49 +0000 2009-09-08 closed with no action