Re: targetResource wording

On Sun, Jun 15, 2003 at 08:51:07PM +0600, Sanjiva Weerawarana wrote:
> > So why not have the spec mint a URI which identifies a resource
> > which represents *every* other resource (i.e. every resource
> > everywhere, that exists, has existed, or will exist)?  Then
> > you won't need targetResource at all, as it can be assumed
> > that its value will always be this URI.
> 
> Huh? Either I don't understand what you said or you have
> totally misunderstood the purpose of @targetResource.

The former, I believe.

Ok, rather than dig deeper into that admitedly esoteric example, let me
boil this down to a simple position statement ...

The resource(s) that a service uses are part of the implementation of a
service, not its interface.  Please don't conflate the two.

Thanks.

MB
-- 
Mark Baker.   Ottawa, Ontario, CANADA.        http://www.markbaker.ca

Received on Sunday, 15 June 2003 14:01:17 UTC