{"id":401,"date":"2004-06-15T00:57:00","date_gmt":"2004-06-15T04:57:00","guid":{"rendered":"http:\/\/www.markbaker.ca\/wp\/?p=398"},"modified":"2004-06-15T00:57:00","modified_gmt":"2004-06-15T04:57:00","slug":"rest-workflow-paper","status":"publish","type":"post","link":"http:\/\/www.markbaker.ca\/blog\/2004\/06\/rest-workflow-paper\/","title":{"rendered":"REST Workflow paper"},"content":{"rendered":"<p><a href=\"http:\/\/www.innoq.com\/blog\/st\/2004\/06\/developing_web_services_choreography_standards_the_case_of_rest_vs_soap.html\">Stefan found<\/a>\na paper with a very interesting title, that I hadn&#8217;t heard\nanything about;\n<a href=\"http:\/\/www.workflow-research.de\/Publications\/PDF\/MIZU.JENI.KESW-DSS(2004).pdf\">Developing Web Services Choreography Standards &#8211; The Case of REST vs. SOAP<\/a>.<\/p>\n\n<p>I&#8217;d heard Keith Swenson&#8217;s name a few days earlier in the context of\n<a href=\"http:\/\/www.oasis-open.org\/committees\/tc_home.php?wg_abbrev=asap\">ASAP<\/a>\nand some of the recent\n<a href=\"http:\/\/www.infoworld.com\/article\/04\/06\/11\/HNasap_1.html\">buzz<\/a>\nsurrounding it, but I&#8217;ve known about his work for a while.  I spent some\ntime studying both <a href=\"http:\/\/www.endtech.com\/pdfs\/swap.pdf\">SWAP<\/a>\n(co-authored with a buddy of mine,\n<a href=\"http:\/\/endeavors.com\/bios.html#GBCTO\">Greg Bolcer<\/a>)\nand\n<a href=\"http:\/\/www.pwg.org\/ipp\/\">IPP<\/a>\nduring their development.<\/p>\n\n<p><em>Aside;<\/em> IPP actually slowed my studies into the Web (along with\n<a href=\"http:\/\/www.w3.org\/Protocols\/HTTP-NG\/\">HTTP-NG<\/a>, sigh) because I, for\nwhatever reason, started by assuming that IPP was a <em>good<\/em> use of HTTP.\nOnly later did I realize that the exact opposite was true (as was only recently\n<a href=\"http:\/\/www.w3.org\/2003\/02\/06-tag-summary\">confirmed<\/a> by Roy).<\/p>\n\n<p>On the upside, IPP&#8217;s use of POST spawned an important and interesting exchange,\nvia Internet draft, that I studied very carefully (which lead to a\n<a href=\"http:\/\/www.markbaker.ca\/2001\/09\/draft-baker-http-resource-state-model-01.txt\">draft of my own<\/a>);\n<a href=\"http:\/\/www.ics.uci.edu\/pub\/ietf\/http\/draft-cohen-http-ext-postal-00.txt\">Don&#8217;t go Postal<\/a><\/li>,\nand\n<a href=\"http:\/\/www.ics.uci.edu\/pub\/ietf\/http\/draft-debry-http-usepost-00.txt\">The Use of POST<\/a>.<\/p>\n\n<p>Anyhow, all of this to say that I <em>was<\/em> quite surprised to see\nREST reasonably well represented &#8230; except for perhaps this part;<\/p>\n\n<blockquote>\nSeveral standards for REST style workflow interaction have been proposed, namely SWAP, Wf-XML\n[26, 52, 58], AWSP [49] and ASAP [38]. Instead of relying on the HTTP 1.0 commands, these standards\nprovide higher level operations that are specifically designed for the interaction with remote processes.\n<\/blockquote>\n\n<p>Hint; if you&#8217;re trying to provide operations at a higher level than the\napplication layer (e.g. HTTP), you&#8217;re abusing HTTP, not using it.  But, the\noperations being tunneled are themselves reasonably generic, which is good\ndesign practice for this space, and what I think the authors were trying to\npoint out as nearly RESTful.<\/p>\n\n<p>It&#8217;s really encouraging to see REST mentioned in the context of workflow,\nsince I believe it provides a superior base for scalable solutions than does\nSOA.  I think this paper could be an important piece of work if the authors were\nto spend some time studying both architectural styles from a software architecture\nPOV, as well as actually building some systems with each.  As is, the analysis is\npretty decent, but the conclusion &#8211; basically that it&#8217;s a crap shoot over which\none is superior &#8211; needs some major work.<\/p>","protected":false},"excerpt":{"rendered":"Stefan found a paper with a very interesting title, that I hadn&#8217;t heard anything about; Developing Web Services Choreography Standards &#8211; The Case of REST vs. SOAP. I&#8217;d heard Keith Swenson&#8217;s name a few days earlier in the context of ASAP and some of the recent buzz surrounding it, but I&#8217;ve known about his work [&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,40],"class_list":["post-401","post","type-post","status-publish","format-standard","hentry","category-uncategorized","tag-soap","tag-xml"],"_links":{"self":[{"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/posts\/401","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=401"}],"version-history":[{"count":0,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/posts\/401\/revisions"}],"wp:attachment":[{"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/media?parent=401"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/categories?post=401"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/tags?post=401"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}