I would be a lot happier about requiring SOAP than WSDL because that would include ebXML, and I would be extremely unhappy if we put that outside the entire WS fence. I still think my simple example is a Web service, but would be willing to join a consensus that it is not. I don't think it's a real big deal either way. -----Original Message----- From: Jim Webber [mailto:jim.webber@arjuna.com] Sent: Tuesday, April 15, 2003 10:24 AM To: www-ws-arch@w3.org; www-ws-arch-request@w3.org Subject: RE: Is This a Web Service? Roger: > Do other people think that if it doesn't use WSDL it's not a > Web service? I personally don't like this at all. Nor do I, but then I have the seemingly contrarian view that SOAP is implicitly involved :-) (and not necessarily anything to do with the Web). While I can appreciate that this group does not necessarily have to have a commercially-facing outlook, we are at risk of marginalisation if the architecture fragments into X different flavours of Web services. JimReceived on Tuesday, 15 April 2003 11:39:05 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 3 July 2007 12:25:17 GMT