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

RE: /service/@targetResource ?

From: Sedukhin, Igor S <Igor.Sedukhin@ca.com>
Date: Thu, 29 May 2003 16:52:35 -0400
Message-ID: <87527035FDD42A428221FA578D4A9A5B03209DF5@usilms24.ca.com>
To: "Arthur Ryman" <ryman@ca.ibm.com>, <www-ws-desc@w3.org>
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?
 
 

-- 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 16:52:43 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:58:24 GMT