RE: Choreography and REST

I believe assembly, sequencing, and interdependecies among Web services is an essential element of Web services architecture, whether it's called choreography, process flow, or coordination...

Eric

-----Original Message-----
From: Champion, Mike [mailto:[email protected]]
Sent: Wednesday, August 14, 2002 8:52 AM
To: [email protected]
Subject: RE: Choreography and REST





> -----Original Message-----
> From: Paul Prescod [mailto:[email protected]]
> Sent: Wednesday, August 14, 2002 8:29 AM
> To: Martin Chapman; [email protected]
> Subject: Re: Choreography and REST
> 
> 
> 
> Martin Chapman wrote:
> > 
> > Firstly lets not argue the usefulness of the factory pattern:-)
> > 
> > Secondly in your example, I could get a c_obj from a
> > trader/uddi/directory, without
> > there being any explicit make_c. 
> 
> That's a feature, not a bug.

I've lost the thread of this thread.  As I understand it, Paul was arguing
that "choregraphy" is not necessary, I think because web services developers
can "just know" what state a resource/object needs to be in in order to
invoke some service that accesses it. By analogy, there are no machine
processable, declarative descriptions of the filesystem objects, but we
somehow manage to build programs that open, close, read, write, and delete
files all the time.

So, 1) Does this summary do justice to what we're discussing in this thread?
2) Does Paul or anyone else think that "choreography" (somewhat loosely
defined, see the thread on terminology) is an intrinsically bad idea, or
merely a low priority for the WSA WG even if it is a popular idea at the
mement?  3) Do the objections stem from a "REST" viewpoint, a "semantic web"
or RDF viewpoint, or what?  

Thanks...