- From: Shi, Xuan <xshi@GEO.WVU.edu>
- Date: Thu, 26 Jan 2006 11:35:16 -0500
- To: "'Yves Lafon '" <ylafon@w3.org>, "'Battle, Steven Andrew '" <steve.battle@hp.com>
- Cc: "'public-sws-ig@w3.org '" <public-sws-ig@w3.org>, "Shi, Xuan" <xshi@GEO.WVU.edu>
I agree. In the initial discussion and description about OSRR approach in paper: http://ftp.informatik.rwth-aachen.de/Publications/CEUR-WS/Vol-140/paper1.pdf the title of section three is just "3. MESSAGE-ORIENTED SEMANTIC WEB SERVICES". By transferring message in XML document directly via HTTP, we can connect distributed machines and programs together without the WSDL/SOAP framework. Thus semantic Web services should describe the meaning inside the message/XML document, without concerning about the framework by which the message is transferred. SOAP is good for programmers by the OOP approach. However, in OSRR, the first task for programmers is to process the XML document before they jump into OOP. That's the only difference. You can do whatever you want to do in the traditional OOP approach. Please take a quick look on the diagram I draw for my article, you may find that in SOAP, computer will do the serialization/deserialization to create an XML document (SOAP message). In OSRR, programmers have to do such work themselves because most of the consumers of their services may not be programmers, thus such message does not need to contain varied jargons. Best wishes, Xuan -----Original Message----- From: Yves Lafon To: Battle, Steven Andrew Cc: public-sws-ig@w3.org Sent: 1/26/06 10:20 AM Subject: RE: OSRR vs. OWL-S, WSMO, and others On Wed, 25 Jan 2006, Battle, Steven Andrew wrote: > The REST vs. SOAP debate is interesting and each style has its place. > For B2B web-services I prefer SOAP, for B2C REST provides a lightweight > alternative. However, the process model should be independent of these > concerns. The REST vs SOAP debate as in "eating a soup with a spoon and with pleasure" and the spoon vs pleasure debate? :) SOAP is not an architectural style, it's a message processing format mixed with protocol bits. I'd rather see a debate between REST vs Message Oriented Architecture. Thanks, -- Yves Lafon - W3C "Baroula que barouleras, au tiéu toujou t'entourneras."
Received on Thursday, 26 January 2006 16:36:45 UTC