OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

asap message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Fwd: [service-orientated-architecture] Pass-by-RESTference

I suppose some of the ideas are that
by explicitly defining resources, we can explicitly associate properties with them
and that separating out the resource identifier would
preserve independence of the resources themselves
and how they are accessed, so different services or access methods
could be used to access the same resource?

I'm tempted by the ability to reason about resources with the WS-Resource
specs, but cautious given some of what's been written about the inherent
power of URIs and stripped down, simple interfaces.

Begin forwarded message:

From: Mark Baker <distobj@acm.org>
Date: February 2, 2004 8:13:24 AM CST
To: service-orientated-architecture@yahoogroups.com
Subject: Re: [service-orientated-architecture] Pass-by-RESTference

On Mon, Feb 02, 2004 at 06:32:22AM -0600, John Fuller wrote:
> I suppose a related question is what do you all think of passing
> WS-Addressing
> endpoint references to explicitly refer to resources at endpoints
> rather than
> encoding the resource references in a URI?
> (Ex:  WS-Resource specs from the grid community v. classic REST)

I don't understand why anybody would want to do that.

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

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]