A couple of high-level comments on this proposal:
1.) Before we start discussing solutions to support the use of XML
elements in addition to SOAP messages I think the group needs to decide
if this is a use case we need to support. I confess to being confused
by the distinction that is being drawn here. The contents of a SOAP
Body are XML elements that are generally described by XSD. I
don't understand why you couldn't (a) create wsdl:messages from these
XML elements and use them as input messages for an Event Sink operation
or (b) include these XML elements in a wrapped Notification.
2.) If we do decide that this is a use case we need to support,
I'm a bit hesitant about pulling in a entirely new specification. Right
now we are working from a base of SOAP 1.1 and SOAP 1.2, WSDL 1.1, BP
1.1, and WS-Addressing. These are pretty commonly supported across our
industry. Requiring implementations to support SAWSDL in order to
implement WS-Eventing seems like a rather large imposition to me.
- gp
p.s. Please submit future proposals in plain text.
Chou, Wu (Wu) wrote:
Wu
Chou, IEEE Fellow, Ph.D. | Director
|Avaya Labs Research |
AVAYA
|
233
Mt. Airy Road|
Rm.
2D48 |
Basking Ridge, NJ 07920 |
Voice/Fax:
908-696-5198 / 908-696-5401
|
wuchou@avaya.com