Re: resolution of 6429

Not hearing any comments - I'm going to assume that this WSDL should 
appear in the ws-eventing WSDL.
This then raises another question - what's the namespace of the elements? 
The proposal uses a "wrapped" namespace (tns and targetnamespace), but 
that will be annoying and tricking if its part of the same wsdl.  For now 
I'm going to give these the ws-eventing namespace - since its all part of 
the same spec its odd to pull them out into a new namespace.
If people have concerns let's discuss it thru email or on the next call.

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.



Doug Davis/Raleigh/IBM@IBMUS 
Sent by: public-ws-resource-access-request@w3.org
05/19/2009 08:40 PM

To
public-ws-resource-access@w3.org
cc

Subject
resolution of 6429







on today's call we resolved 6429.  The new appendix will include the wsdl 
for wrapped notifications.  Should this new wsdl appear in the 
ws-eventing.wsdl file as well - in an unused (unreferenced) portType?  If 
so, I'd like to rename it from "GenericSinkPortType" to 
"WrappedSinkPortType" if that's ok.  If not then where did people expect 
this wsdl to appear (aside from the appendix)? 

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.