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

RE: /service/@targetResource ?

From: Philippe Le Hegaret <plh@w3.org>
Date: 29 May 2003 17:43:15 -0400
To: "Sedukhin, Igor S" <Igor.Sedukhin@ca.com>
Cc: www-ws-desc@w3.org
Message-Id: <1054244594.1192.232.camel@jfouffa.w3.org>

On Thu, 2003-05-29 at 16:52, Sedukhin, Igor S wrote:
> What is the difference between targetResource and target namespace of
> the <service> element? Aren't they identifying "functionality" and all
> the other things related to the service "semantics"? Why two
> identifiers are so necessary?

targetResource doesn't identify a functionality but a resource. It is
orthogonal to the target namespace. Two services may use the same target
namespace and still work on a different resource. Two services could
provide access to the same resource using two differents interfaces. In
such case, you can express the relation between the two services using
the targetResource attribute.

Your previous example:
>  There is a service A that has an endpoint that binds the interface
>  A1. There is a service B and interface B1 similarily. Those are
>  internal services. I'd like to offer service C that is an aggregate
>  of two functionalities to a partner. I may have an intermediary that
>  may merely represent an aggregate. So, in the WSDL I'd have service C
>  that has two endpoints, one binds interface A1 and another binds
>  B1. Both may or may not share the same address.

transform into:

<service name="C.1"
 <endpoint ... >
   <http:address href='http://www.example.com/myService'/>
<service name="C.2"
 <endpoint ... >
   <http:address href='http://www.example.com/myService'/>

or you can also create an interface F, that inherits from A1 and B1:

<service name="C.3"
 <endpoint ... >
   <http:address href='http://www.example.com/myService'/>


> -- Igor Sedukhin .. (igor.sedukhin@ca.com)
> -- (631) 342-4325 .. 1 CA Plaza, Islandia, NY 11788
>         -----Original Message-----
>         From: Arthur Ryman [mailto:ryman@ca.ibm.com] 
>         Sent: Wednesday, May 14, 2003 11:11 AM
>         To: www-ws-desc@w3.org
>         Subject: /service/@targetResource ?
>         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 Thursday, 29 May 2003 17:43:17 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:54:42 UTC