W3C home > Mailing lists > Public > public-ws-resource-access-notifications@w3.org > June 2009

[Bug 6401] Eventing: Notifications violates WS-I BP

From: <bugzilla@wiggum.w3.org>
Date: Tue, 23 Jun 2009 11:58:20 +0000
To: public-ws-resource-access-notifications@w3.org
Message-Id: <E1MJ4do-0004tC-Ch@wiggum.w3.org>

--- Comment #7 from Robert Freund <bob@freunds.com>  2009-06-23 11:58:20 ---
2009-06-11 Issue 6661 is merged with this issue.
Text from 6661 is as follows:
Appendix I of the WS-Eventing Member Submission, "Service Metadata for
Eventing", is incomplete in a number of areas. Firstly it does not indicate how
an Event Sink is expected to derive the binding details for the Notifications.
Will the Notifications be sent as RPC/Encoded, Doc/Literal? Will the
Notifications be sent using SOAP 1.1 or SOAP 1.2? Secondly, the relationship
between the "endpoint reference for the event source" and the annotated
portType is unclear. One might think that the "endpoint reference for the event
source" is equivalent to the wsdl:port that implements a binding of the
annotated portType, but this conjecture is not supported by any text or

"Service Metadata for Eventing" is also technically incorrect in that it
requires Event Sources to process a WSDL containing output-only operations in
order to generate the code necessary to correctly process and dispatch
Notification messages which is a violation of BP 1.1 R2303. While one could
argue about the relevance of WS-I profiles to infrastructure-level protocols,
it is clear that creation of Notification handlers is, in this context, an
application-level activity as the type and structure of Notifications is driven
by the application and not WS-Eventing.

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Tuesday, 23 June 2009 11:58:25 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:06:34 UTC