On 11/07/06, Jan Algermissen <[EMAIL PROTECTED]> wrote:
>
>
>
>
>
>
>
>
>
>  On Jul 11, 2006, at 3:21 PM, Steve Jones wrote:
>
>  > On 10/07/06, Mark Baker <[EMAIL PROTECTED]> wrote:
>  > >
>
>  > > Steve - it is *axiomatic* in REST that all services expose the same
>  > > "operational interface", so yes, we do know that.
>  > >
>  > > http://roy.gbiv.com/pubs/dissertation/rest_arch_style.htm#sec_5_1_5
>  > >
>  >
>  > Nope, that is the INVOCATION mechanism (the execution context to use
>  > the SOA RM term), that isn't the operational interface that consumers
>  > use.
>  >
>  > With our lightbulb we have
>  > 1) The URI
>  > 2) The data format of the request/response
>  > 3) The meaning of that request/response
>  >
>  > "PUT" is not an operational interface for a service consumer, it is
>  > the execution context that enables the consumer to be connected with
>  > the producer.
>  >
>
>  Sorry Steve, I am afraid you just have to accept that HTTP indeed
>  does define just that, an operational interface. Or do you really
>  want to suggest that the authors of that spec did not know what they
>  wanted to specify?

The authors of the specification are defining a technical mechanism
that could be used to  link a producer and consumer.  They are
explicitly NOT defining how capabilities are defined on services and
the specifics for that part of the problem.

HTTP does NOT define an operational interface beyond the interface it
provides to browsers.  When considering system->system interfaces it
most certainly does not provide the required information to make both
systems understand the interaction.

>
>  I am confused - why do not simply accept what that spec says??

Because the specification says nothing (unless I've missed the
section) about the definition of capabilities or service but just
provides another technical implementation approach for the execution
context.

>
>  Jan
>
>  >
>
>
>
>                   





------------------------ Yahoo! Groups Sponsor --------------------~--> 
See what's inside the new Yahoo! Groups email.
http://us.click.yahoo.com/2pRQfA/bOaOAA/yQLSAA/NhFolB/TM
--------------------------------------------------------------------~-> 

 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/service-orientated-architecture/

<*> To unsubscribe from this group, send an email to:
    [EMAIL PROTECTED]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/
 



Reply via email to