W3C home > Mailing lists > Public > www-ws-desc@w3.org > May 2003

Re: /service/@targetResource ?

From: Jacek Kopecky <jacek@systinet.com>
Date: 21 May 2003 16:03:17 +0200
To: WS-Description WG <www-ws-desc@w3.org>
Message-Id: <1053525797.6140.25.camel@localhost>

Is it the intended semantics that two services with the same value of
@targetResource (or whatever it ends up being called) with ports of the
same interface, a client may use either of the service to reach the same

If not, someone please describe the semantics.

If yes, we're basically splitting the old service construct into a
number of the new service constructs limited to one interface each,
linked together by the value of the new attribute, right?


On Wed, 2003-05-14 at 17:10, Arthur Ryman wrote:
> In the discussion with the architecture group today, there seemed to
> be confusion between a service and the resource is acts on. The
> architecture group defines a Web service to have something that has a
> URI, but that URI is not the same as the resource that the Web service
> acts on.
> For example, a bank might have a personal banking Web service. The
> account Web service acts on the bank.
> We can build a URI from the QName of the personal banking Web service,
> e.g. http://xml.fredsbank.com#service(PersonalBanking). The bank
> itself might have the URI http://fredsbank.com.
> We agreed to add an optional @resource attribute to <service>. I
> suggest it would be clearer to rename that attribute to
> @targetResource to make it clear that the service acts on that
> resource as opposed to it being the URI of the Web service.
> Arthur Ryman
Received on Wednesday, 21 May 2003 10:03:32 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:06:30 UTC