6401 2009-01-14 00:05:27 +0000 Eventing: Notifications violates WS-I BP 2009-09-16 08:16:20 +0000 1 1 1 Unclassified WS-Resource Access Eventing FPWD PC Windows XP CLOSED REMIND http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Jan/0009.html hasProposal P2 normal --- 6430 6661 7207 1 dug dug bob gilbert.pilz public-ws-resource-access-notifications oldest_to_newest 23047 0 dug 2009-01-14 00:05:27 +0000 WS-Eventing proposes that the event source define some output-only operations for the events it will send, as shown in the following example from the spec: <wsdl:portType name="Warnings" wse:EventSource="true" > <wsdl:operation name="WindOp" > <wsdl:output message="tns:WindMsg" /> </wsdl:operation> </wsdl:portType> WS-I Basic Profile R2303 says the following: 4.5.2 Allowed Operations Solicit-Response and Notification operations are not well defined by WSDL 1.1; furthermore, WSDL 1.1 does not define bindings for them. R2303 A DESCRIPTION MUST NOT use Solicit-Response and Notification type operations in a wsdl:portType definition. Proposal: Replace this with some WS-Policy that will allow an event source to advertise which events will can generate. 23130 1 bob 2009-01-15 23:26:19 +0000 2009-01-15: discussed and Gil has action to take up the output only issue at WS-I once more with feeling. 24026 2 bob 2009-03-03 12:45:48 +0000 2009-02-17 No member seems to be taking this up with WS-I 24209 3 bob 2009-03-12 14:01:27 +0000 members seem to agree that a practical solution is to shift to imput operations. Action-48 on Gil, Wu, Dug 24428 4 bob 2009-03-29 22:33:38 +0000 proposal at http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Mar/0127.html 24963 5 bob 2009-04-28 21:19:21 +0000 Action-61 25668 6 bob 2009-06-23 11:56:59 +0000 *** Bug 6661 has been marked as a duplicate of this bug. *** 25669 7 bob 2009-06-23 11:58:20 +0000 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 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. 26020 8 bob 2009-07-21 13:35:26 +0000 Proposal at http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Jul/0046.html 26664 9 bob 2009-08-25 20:31:05 +0000 proposal at http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Aug/att-0057/wseventing_6401-6.html 26665 10 dug 2009-08-25 20:35:43 +0000 Amended proposal at: http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Aug/att-0061/ws-eventing-6401-6-dug2.doc 26666 11 bob 2009-08-25 20:41:45 +0000 proposal at http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Aug/att-0061/ws-eventing-6401-6-dug2.doc 26775 12 bob 2009-09-01 19:56:12 +0000 proposal at http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Sep/att-0004/ws-eventing-6401-6-dug5.doc 26791 13 bob 2009-09-02 08:38:13 +0000 2009-09-01 resolved with comment 12