- From: Sergey Beryozkin <sberyozkin@zandar.com>
- Date: Fri, 20 Jun 2003 09:48:34 +0100
- To: "VAMBENEPE,WILLIAM \(HP-Cupertino,ex1\)" <vbp@hp.com>, "'David Booth'" <dbooth@w3.org>, <www-ws-desc@w3.org>
- Cc: "Mark Baker" <distobj@acm.org>, "Sanjiva Weerawarana" <sanjiva@watson.ibm.com>, "Champion, Mike" <Mike.Champion@SoftwareAG-USA.com>
Hello, > > The targetResource attribute has nothing to do with describing a > > service. It is used to indicate a relationship *between* > > services. Its > > purpose is to allow two WSDL <service> descriptions, d1 and > > d2, to assert > > that (behind the scenes) the services s1 and s2 that they > > describe are > > actually "manipulating" the same resource. In practical terms, does it mean that a targetResource serves as *an internal hint only* to the services s1 and s2 as to how to process an incoming request ? Can a client processing service d1 and d2 descriptions to avail of this targetResource attribute in any way ? Thanks Sergey Beryozkin
Received on Friday, 20 June 2003 04:48:35 UTC