{"id":46,"date":"2002-10-30T11:29:00","date_gmt":"2002-10-30T15:29:00","guid":{"rendered":"http:\/\/www.markbaker.ca\/wp\/?p=26"},"modified":"2002-10-30T11:29:00","modified_gmt":"2002-10-30T15:29:00","slug":"dave-winers-soap-definition","status":"publish","type":"post","link":"http:\/\/www.markbaker.ca\/blog\/2002\/10\/dave-winers-soap-definition\/","title":{"rendered":"Dave Winer’s SOAP definition"},"content":{"rendered":"

Dave made the following suggestion<\/a> for a SOAP definition;<\/p>\n\n

\nIt’s a simple way to call procedures running on other machines, on other OSes, written in other languages, using different economic systems, without being forced to pay a tax to Microsoft, IBM, Apple, Sun or the W3C.\n<\/blockquote>\n\n

SOAP isn’t that at all. That’s XML-RPC. Dave’s a bright guy who writes great software<\/a>, but when it comes to distributed systems, there’s a lot he doesn’t understand.<\/p>\n\n

The SOAP 1.2 spec defines SOAP as;<\/p>\n\n

\nSOAP Version 1.2 (SOAP) is a lightweight protocol intended for exchanging structured information in a decentralized, distributed environment. It uses XML technologies to define an extensible messaging framework providing a message construct that can be exchanged over a variety of underlying protocols. The framework has been designed to be independent of any particular programming model and other implementation specific semantics.\n<\/blockquote>\n\n

Which is a pretty decent definition, though not very detailed as to how one actually might use it. For a better definition, I look to SOAP’s brethren<\/a>, PEP<\/a>. It’s defined as;<\/p>\n\n

\nThe Protocol Extension Protocol (PEP) is an extension mechanism designed to accommodate dynamic extension of HTTP applications by software components; and to address the tension between private agreement and public specification.\n<\/blockquote>\n\n

Of course, SOAP isn’t tied to HTTP, but PEP didn’t really need to be either. It could also be patched to be an extension protocol for non-HTTP protocols, as SOAP 1.1 was “patched” in the form of SOAP 1.2.<\/p>\n\n

Please, if SOAP has any<\/em> chance of success, let’s try to distance it from RPC.<\/p>","protected":false},"excerpt":{"rendered":"Dave made the following suggestion for a SOAP definition; It’s a simple way to call procedures running on other machines, on other OSes, written in other languages, using different economic systems, without being forced to pay a tax to Microsoft, IBM, Apple, Sun or the W3C. SOAP isn’t that at all. That’s XML-RPC. Dave’s a […]","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[26,32,34,40],"class_list":["post-46","post","type-post","status-publish","format-standard","hentry","category-uncategorized","tag-soap","tag-travel","tag-w3c","tag-xml"],"_links":{"self":[{"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/posts\/46","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/comments?post=46"}],"version-history":[{"count":0,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/posts\/46\/revisions"}],"wp:attachment":[{"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/media?parent=46"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/categories?post=46"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/tags?post=46"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}