- From: Doug Davis <dug@us.ibm.com>
- Date: Fri, 9 Jan 2009 08:14:06 -0500
- To: antoine.mensch@odonata.fr
- Cc: public-ws-resource-access@w3.org
- Message-ID: <OF277A561F.DFAC5984-ON85257539.00481AC6-85257539.0048B447@us.ibm.com>
Hi Antoine, we may need to bring in people who are more BP experts (and have the history of this issue) but I'm sure everyone knows the semantics of Notifications in general so I don't think that was the issue for the BP folks. I think it was more related to the notion that WSDL typically describes what a client is expected to do to talk to the service so to then have WSDL be used in the reverse direction seems to be counter to that idea. There are probably several options for fixing these types of issues but in the end I'd like to be able to use my BP-compliant tooling on the WSDLs produced by this WG and with these output-only operations it'll generate errors. thanks -Doug ______________________________________________________ STSM | Web Services Architect | IBM Software Group (919) 254-6905 | IBM T/L 444-6905 | dug@us.ibm.com Antoine Mensch <antoine.mensch@odonata.fr> 01/09/2009 07:27 AM Please respond to antoine.mensch@odonata.fr To Doug Davis/Raleigh/IBM@IBMUS cc public-ws-resource-access@w3.org Subject Re: [NEW ISSUE] WS-Eventing Notifications violates WS-I BP Doug, don't you think that because WS-Eventing actually defines a clear semantics for Notification and Solicit-Response operations, the rationale for prohibiting them in BP1.1 somewhat disappears? Cheers Antoine
Received on Friday, 9 January 2009 13:14:53 UTC