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

Re: targetResource wording

From: Umit Yalcinalp <umit.yalcinalp@oracle.com>
Date: Fri, 20 Jun 2003 15:47:08 -0700
Message-ID: <3EF38EEC.7050008@oracle.com>
To: Savas Parastatidis <Savas.Parastatidis@newcastle.ac.uk>
CC: www-ws-desc@w3.org


Savas Parastatidis wrote:

>>At 10:48 PM 6/20/2003 +0100, Savas Parastatidis wrote:
>>    
>>
>>>So, I guess it's a matter of preference. The @targetResource
>>>      
>>>
>introduces
>  
>
>>>identity to a web service . . . .
>>>      
>>>
>>Careful.  The targetResource doesn't identify the *service*, it
>>    
>>
>identifies
>  
>
>>some *other* resource that the service "manipulates".  We don't have
>>    
>>
>an
>  
>
>>accepted term for that "other resource".  In the WS Architecture WG
>>    
>>
>we've
>  
>
>>been calling it a "turtle". :)
>>    
>>
>
>I understand that targetResource does not identify the service but the
>combination of interface + targetResource does. Or doesn't it?
>
>All of the printer services were supporting the same interface but they
>had a different targetResource, hence making those services
>distinguishable from each other. Perhaps, you don't call it "identity"
>but when everything else is the same, it seems to me that the "turtle"
>:-) becomes an "id".
>  
>
Not quite. The service element is essentially the ID for the service and 
targetResource is the identifier for the resource that it manipulates. 
The printerService and the printerManagementService are not the same 
services. They work on the same resource.

--umit

>At the end of the day you do end up having a bunch of web services whose
>only difference is their targetResource.
>
>.savas.
>
>
>  
>

-- 
Umit Yalcinalp                                  
Consulting Member of Technical Staff
ORACLE
Phone: +1 650 607 6154                          
Email: umit.yalcinalp@oracle.com
Received on Friday, 20 June 2003 18:47:34 GMT

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