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

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

From: Walden Mathews <waldenm@optonline.net>
Date: Thu, 22 May 2003 09:56:55 -0400
To: Mark Baker <distobj@acm.org>, www-ws-arch@w3.org
Message-id: <002701c3206a$01c33b60$1702a8c0@WorkGroup>

That's true, but is one target going to be enough, or will the
spec have to accommodate arbitrarily many targets?  Consider
the transfer service that affects two accounts.

And then if it is going to support many, then their roles have to
be specified, and so on.....Burdensome and stiff.


----- Original Message -----
From: "Mark Baker" <distobj@acm.org>
To: <www-ws-arch@w3.org>
Sent: Thursday, May 22, 2003 9:29 AM
Subject: Re: Separate concepts for "service" and "targetResource?" (was RE :
/service/@targetResource ?)

> +1
> I think that's the best way to think about it.  While it seems far
> simpler to just use the printer via HTTP methods invoked on the URI
> identifying the printer, if Web services still feel the need to continue
> to use "open interfaces", at least this approach draws a clean dividing
> line between the two approaches.
> On Thu, May 22, 2003 at 08:48:13AM -0400, David Orchard wrote:
> > That's why there are 2 URIs.  One for the "target", and one for the
> > "service".  A printer is a different concept than a printer service.  I
> > don't know why this is so hard for people to understand.  There may be
> > services associated with a printer.  Hence there may be many different
> > service URIs, yet only one target URI.  And these services could be in
> > different wsdl definitions.
> >
> > Cheers,
> > Dave
> --
> Mark Baker.   Ottawa, Ontario, CANADA.        http://www.markbaker.ca
> Web architecture consulting, technical reports, evaluation & analysis
>   Actively seeking contract work or employment
Received on Thursday, 22 May 2003 09:52:39 GMT

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