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

Re: Separate concepts for "service" and "targetResource?" (was RE: /service/@targetResource ?)

From: Mark Baker <distobj@acm.org>
Date: Wed, 21 May 2003 13:34:39 -0400
To: www-ws-arch@w3.org
Message-ID: <20030521133439.G24973@www.markbaker.ca>

I have a related but different concern than Ugo.

There will be services that operate on no resources (i.e. those with
no state), services that operate on one resource, and services that
operate on many resources.  More importantly, there will be services
that operate on resources whose identity is only determined at runtime,
and I suggest that this will be the common case, not the exception.
That pretty much rules out specifying this information as part of the
interface, I believe.

This seems like a really wacky idea to me, but I'd like to know more
about the problem that this attempts to solve.  As Arthur described[1],
it sounded more like documentation than anything, but it seems from
further discussion[2] that it may be more.

 [1] http://lists.w3.org/Archives/Public/www-ws-desc/2003May/0048.html
 [2] http://lists.w3.org/Archives/Public/www-ws-desc/2003May/0059.html

MB
-- 
Mark Baker.   Ottawa, Ontario, CANADA.        http://www.markbaker.ca
Web architecture consulting, technical reports, evaluation & analysis
  Actively seeking contract work or employment
Received on Wednesday, 21 May 2003 13:31:50 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 3 July 2007 12:25:19 GMT