#10 wse:Identifier is not usable

[steph96]

Add a note (requirement?) to the standard, that wse:Identifier could not be used (in conjuction with WS-Adressing).

Background:

When sending a SOAP message to an EPR with reference parameters, the SOAP header block requires the attribute wsa:IsReferenceParameter to indicate it is a WSA reference parameter.
https://www.w3.org/TR/ws-addr-soap/#additionalinfoset section 3.3 specifies this attribute as required.

WS-Eventing (old version from W3 submission) provides a wse:Identifier global element as a xsd simple element:
<xs:element name="Identifier" type="xs:anyURI" />
XSD Simple Elements have no attributes, the only contain text. It is not possible to add the wsa:IsReferenceParameter (which is required by WS-Adressing)

Conclusion: It is not possible to use wse:Identifier (from old WS-Eventing standard) with wsa:IsReferenceParameter attribute (from new WS-Adressing standard). This is fine, since wse:Identifier usage is optional in contrast to the required wsa:IsReferenceParameter attribute.

[Stefan Schlichting]

Add should requirements to section "7. Eventing":

RXXX. It is recommended that a Service Provider does not use wse:Identifier with wsa:IsReferenceParameter attribute.
RXXX: its is recommanded that a Service Consumer does not use wse:Identifier with wsa:IsReferenceParameter attribute.

Add Note: A Service Consumer can use a distinguishing path element for its event sink to receive the data.