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


Help: OASIS Mailing Lists Help | MarkMail Help



   Re: [xml-dev] What Does SOAP/WS Do that A REST System Can't?

[ Lists Home | Date Index | Thread Index ]

Michael Champion wrote:
> On Wed, 30 Mar 2005 12:32:11 -0500, Joe Gregorio <joe.gregorio@gmail.com> wrote:
>>>Mu.  REST is a protocol, SOAP is a message format.  <duck>
>>REST is an architectural style, SOAP is a message format.
> You're right of course.  SOA is also an architectural style.

Where is that style documented?

>   I *think* the whole SOAP vs REST permathread  comes down to
> Resource-orientation vs Service-orientation ... complicated by the
> fact that services are also resources, and services can be invoked by
> HTTP+XML just fine.  Joe's
> http://www.xml.com/pub/a/2005/03/02/restful.html  is the clearest I've
> ever seen on what "resource orientation" means :

I agree with this and I agree with Dare, who doesn't seem to agree with 
this. Which is to say I doubt things can be boiled down to a single A vs 
B position. Selecting an approach is much more involved.

> In *both* REST and SOA there is a very large hairy wookie of an
> unanswered question screeching for attention: What are the semantics
> of the resources / services?  In practice this is handled explicitly
> or implicitly by human understanding in both styles. In theory both
> could be handled by some sort of formal semantic mapping a la the
> Semantic Web.

That's not a specific to either. It does however becomes much more 
obvious as the low hanging fruit get eaten and you ask, 'what's left?'. 
If that's now the main problem, we've made progress this decade.



News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS