PUBLIC MARKS with tags soap & vs

I think we had one person inquire about using the SOAP version of the API. I don't know if any apps were actually built. There is at least one application built on XML-RPC. But all the others--I don't even know how many there are--are built on the REST AP

REST is for data-oriented applications that focus on create/read/update/delete scenarios. Solution based on WS-* for service/method-oriented applications, especially those that need more advanced behaviors such as transactions and more-than-basic security

A hallmark of fundamentalism is a desire to apply simple rules ("programs are declarative," "there is no operation but POST", "services are stateless") to all situations. But computing is a large and varied world, with few opportunities for absolutist statements.

to implement Web Services Security with the X.509 Certificate Profile, you also need to implement XML Signature (which includes XML Canonicalization and XML Exclusive Canonicalization) and XML Encryption. To correctly handle imports of WSDL1.1 documents (and validate the traffic they describe), you need to support the entire behemoth that is XML Schema -- in particular if you are attempting to support RPC-oriented SOAP, which informally requires you to support the entire XML Schema Datatypes specification. Don't forget support for SOAP with Attachments, either!

A couple of years ago Water Supply-Strategic Tactical Air Recycling (WS-STAR) opened up a branch in our town. WS-* (as my IM crazy kids would type) came about from the merger of Secure Operations Air and Power (SOAP) with Expert Machine Lubrication: Radiators, Power, and Cooling (XML-RPC).

how to handle an internal product debate around REST vs. SOAP