- From: Ugo Corda <UCorda@SeeBeyond.com>
- Date: Wed, 31 Jul 2002 10:54:53 -0700
- To: "'Mark Hapner'" <mark.hapner@sun.com>, ws-arch-public <www-ws-arch@w3.org>
>I also include the ebXML stack as part of the larger Soap web services umbrella This reminds me that it would be great if WSA could address the ebXML stack, not just at the level of harvesting some of its architectural aspects, but more directly discussing those areas that ebXML covers but are missing in WSs (e.g. ebMS's reliable messaging) and those areas that overlap in WS and ebXML (e.g. UDDI vs. ebXML's repository). This type of work might not involve foundational aspects of Web Services, but can still provide invaluable help to the real world WS and ebXML communities, and might clarify once for all (too much to ask, probably) what is the relationship between Web Services and ebXML. >Soap WSDL should be able to provide a basic description of a URI, its >support for GET, its GET 'query' and the MIME type it returns. Ditto for >POST. Soap should provide a binding that allows web service endpoints to >offer services at the HTTP level without requiring enclosing Soap wire >enveloping on request or response. In fact, isn't this already addressed by WSDL 1.2, "HTTP GET and POST Binding"? Ugo
Received on Wednesday, 31 July 2002 13:55:28 UTC