- From: Francis McCabe <fgm@fla.fujitsu.com>
- Date: Tue, 18 Mar 2003 08:50:24 -0800
- To: "Assaf Arkin" <arkin@intalio.com>
- Cc: <www-ws-arch@w3.org>, <public-ws-chor@w3.org>
Assaf: >> >> 3b. Not associating an identifier with a Web service at all: Web >> services would become epiphenomena of the interaction of Web service >> agents. I.e., the WSDL description would identify the identity of the >> providing agent for each message exchange pattern, rather than any Web >> service itself. > > What about another alternative. The composed Web service is known by > it's > definition like any other Web service (WSDL). For the purpose of > interaction > there is no distinction between a composed Web service, a non-composed > Web > service. That is precisely what I am suggesting. However, this is an issue, because in the Architecture group the description of a Web service need not be a resource (in the WWW sense). Frank
Received on Tuesday, 18 March 2003 11:51:06 UTC