Proposal for Issue
http://www.w3.org/Bugs/Public/show_bug.cgi?id=6429
depends on
http://www.w3.org/Bugs/Public/show_bug.cgi?id=6428

WS-Eventing section 1.2 discusses two delivery formats: unwrapped and wrapped but does not specify a standard WSDL for wrapped event delivery. As the result, an Event Source has to assemble different event notification messages with different wrapper element, thus negating the benefit of a standard wrapped event delivery format.

To address this issue, we propose to add a new Appendix IV to WS-Eventing as follows:

Appendix IV — WSDL for Standard Wrapped Delivery

If an Event Subscriber specifies the wrapped event delivery format “http://schemas.xmlsoap.org/ws/2004/08/eventing/DeliveryFormats/Wrap” 

in the Subscribe request message, then the Event Sink must implement the following abstract WSDL and the Event Source must send the notification messages wrapped in the element defined in the WSDL. If necessary, the concrete WSDL can be conveyed to the Event Source using the <wse:NotifyTo> EPR in the Subscribe request message, or retrieved by the Event Source using WS-MetadataExchange.

<definitions 
xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:xs="http://www.w3.org/2001/XMLSchema" 
xmlns:tns="http://schemas.xmlsoap.org/ws/2004/08/eventing/wrap" 
targetNamespace="http://schemas.xmlsoap.org/ws/2004/08/eventing/wrap">
	<types>
	<xs:schema targetNamespace="http://schemas.xmlsoap.org/ws/2004/08/eventing/generic_sink">
	<xs:complexType name="EventType" mixed="true">
	<xs:sequence>
		<xs:any namespace="##any" processContents="lax" minOccurs="0" maxOccurs="unbounded"/>
	</xs:sequence>
	<xs:element name="Notify" type="tns:EventType" />
	</xs:complexType>
	</xs:schema>
	</types>
	<message name="notifyEvent">
		<part name="parameter" element="tns:Notify"/>
	</message>
	<portType name="GenericSinkPortType">
		<operation name="NotifyEvent">
			<input message="tns:notifyEvent"/>
		</operation>
	</portType>
</definitions>