- From: Doug Davis <dug@us.ibm.com>
- Date: Wed, 18 Aug 2010 06:20:53 -0400
- To: Stephan Poehlsen <poehlsen@itm.uni-luebeck.de>
- Cc: public-ws-resource-access@w3.org
- Message-ID: <OFC67C55E3.8D271A2B-ON85257783.0037ECEA-85257783.0038D86D@us.ibm.com>
Stephan and WSRA members (Gil and Wu in particular), while updating WS-Eventing and WS-EVD for this issue ( http://www.w3.org/Bugs/Public/show_bug.cgi?id=10376 ) I noticed that A.2.1 of Eventing seemed a bit short. In the EVD section we showed 3 examples of how the EVD data might be retrieved, while in the Notification WSDL section we didn't have any. As part of the agreed solution to this issue I was going to add one example for the Notification WSDL (using mex.GetMetadata), but for consistency with the EVD section it made sense to also include two more example. One for the Notif. WSDL embedded within the EventSource policy assertion directly, and one where a reference to the Notif. WSDL is in the EventSource policy assertion. Note that I also added a comment to the mex.GetMetadata example pointing out that since the FormatName URI is not present in the GetMetadataResponse the user will need to disambiguate the Notification WSDL from other WSDL docs through some other means. Please look over the changes in the editor's copy and let me know if this is still consistent with our approved resolution. http://www.w3.org/2002/ws/ra/edcopies/wseventing.html http://www.w3.org/2002/ws/ra/edcopies/wsevd.html thanks -Doug ______________________________________________________ STSM | Standards Architect | IBM Software Group (919) 254-6905 | IBM 444-6905 | dug@us.ibm.com The more I'm around some people, the more I like my dog. Stephan Poehlsen <poehlsen@itm.uni-luebeck.de> 08/18/2010 03:37 AM To Doug Davis/Raleigh/IBM@IBMUS cc public-ws-resource-access@w3.org Subject Re: MetadataSection in WS-Eventing With the two examples it is clear from my point of view. Thanks, Stephan Doug Davis wrote: > > Maybe it is possible in WS-Event-Descriptions Section 4.1.1 to express > > more clearly, that the EventSource Policy and the MetadataSection are > > two different things, otherwise the solution with the MetadataSection > > might get lost when skimming over the spec. > > What if we added an Example 4-5(section 4.1.1) that showed the EVD data > being > returned within a GetMetadataResponse(), would that help? > > So what about the NotificationWSDLs? From the current editor's > > WS-Eventing spec, it is not clear for me that the NotificationWSDL is > > retrievable via a MetadataSection. Especially since in section A.2.1 > > http://www.w3.org/TR/2010/WD-ws-eventing-20100330/#id35822333 the gray > > box and Section A.3 was removed. > > Like the previous one, what if we added an example in WS-Eventing's > A.2.1 that showed the Notification WSDL being pulled back from a > MEX.getMetadata()?
Received on Wednesday, 18 August 2010 10:21:37 UTC