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.