{"id":303,"date":"2004-03-11T17:52:00","date_gmt":"2004-03-11T21:52:00","guid":{"rendered":"http:\/\/www.markbaker.ca\/wp\/?p=303"},"modified":"2004-03-11T17:52:00","modified_gmt":"2004-03-11T21:52:00","slug":"savas-misunderstands","status":"publish","type":"post","link":"http:\/\/www.markbaker.ca\/blog\/2004\/03\/savas-misunderstands\/","title":{"rendered":"Savas misunderstands"},"content":{"rendered":"<p>Savas <a href=\"http:\/\/savas.parastatidis.name\/2004\/03\/11\/fc1d823c-1157-4743-83c5-cb0f7e97590c.aspx\">writes<\/a>;<\/p>\n\n<blockquote>\nMark Baker talks about the WSDL WG&#8217;s decision not to require the name of an operation in the body of a SOAP message\n<\/blockquote>\n\n<p>Just to be clear, the issue wasn&#8217;t about placing the operation name\nanyplace in particular.  It was just that I wanted a self-descriptive path to find\nit, no matter where it&#8217;s located.  That could be in the body, the headers, the\nunderlying transfer protocol, in a spec, or in a WSDL document someplace.<\/p>\n\n<p>Of course, I think having the method name in the SOAP message is harmful.  I&#8217;d\nmuch rather it were inherited from the underlying transfer (not transport!) protocol,\nat least when used with a transfer protocol.<\/p>\n\n<p>And to respond to this comment of his;<\/p>\n\n<blockquote>\nWeb Services are all about exchanging information and not identifying methods, operations, functions, procedures that must be called. What services do with the information they receive, through message exchanges, it&#8217;s up to those services.\n<\/blockquote>\n\n<p>I&#8217;d just say that, well, at some layer you have to worry about operations.\nIf Web services aren&#8217;t that layer, then whatever goes on top of them will\nhave to worry about it.  And my understanding was that Web services wanted\nto tackle this layer.  FWIW, I think <a href=\"http:\/\/jim.webber.name\/\">Jim<\/a>\nand I agreed on this in a recent private exchange.<\/p>","protected":false},"excerpt":{"rendered":"Savas writes; Mark Baker talks about the WSDL WG&#8217;s decision not to require the name of an operation in the body of a SOAP message Just to be clear, the issue wasn&#8217;t about placing the operation name anyplace in particular. It was just that I wanted a self-descriptive path to find it, no matter where [&hellip;]","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[26],"class_list":["post-303","post","type-post","status-publish","format-standard","hentry","category-uncategorized","tag-soap"],"_links":{"self":[{"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/posts\/303","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=303"}],"version-history":[{"count":0,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/posts\/303\/revisions"}],"wp:attachment":[{"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/media?parent=303"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/categories?post=303"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/tags?post=303"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}