This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 6661 - WS-Eventing Appendix I is incomplete and incorrect
Summary: WS-Eventing Appendix I is incomplete and incorrect
Status: CLOSED DUPLICATE of bug 6401
Alias: None
Product: WS-Resource Access
Classification: Unclassified
Component: Eventing (show other bugs)
Version: FPWD
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Gilbert Pilz
QA Contact: notifications mailing list for WS Resource Access
URL:
Whiteboard:
Keywords: hasProposal
Depends on: 6401
Blocks:
  Show dependency treegraph
 
Reported: 2009-03-06 22:47 UTC by Gilbert Pilz
Modified: 2009-06-23 11:57 UTC (History)
0 users

See Also:


Attachments

Description Gilbert Pilz 2009-03-06 22:47:21 UTC
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 example.

"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.
Comment 1 Robert Freund 2009-03-12 02:04:26 UTC
2009-03-11 
proposal at http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Mar/0060.html
Comment 2 Robert Freund 2009-06-23 11:56:59 UTC
2009-06-11 Agreed to merge with Issue-6401

*** This bug has been marked as a duplicate of bug 6401 ***