{"id":1581,"date":"2006-06-30T08:36:00","date_gmt":"2006-06-30T12:36:00","guid":{"rendered":"http:\/\/www.markbaker.ca\/wp\/2006\/06\/30\/the-prima-facie-case-against-service-description\/"},"modified":"2006-06-30T08:36:00","modified_gmt":"2006-06-30T12:36:00","slug":"the-prima-facie-case-against-service-description","status":"publish","type":"post","link":"http:\/\/www.markbaker.ca\/blog\/2006\/06\/the-prima-facie-case-against-service-description\/","title":{"rendered":"The prima facie case against service description"},"content":{"rendered":"<img decoding=\"async\" src=\"http:\/\/www.markbaker.ca\/images\/coins.jpg\" \/>\n\n<p><a href=\"http:\/\/www.windley.com\/archives\/2006\/06\/crying_out_for.shtml\">Phil Windley says<\/a>\nthat we need a RESTful service interface description language.\nI don&#8217;t think we do.<\/p>\n\n<p>Interoperability requires agreement, and agreement begets\ncommoditization.  If all the interfaces are the\n<a href=\"http:\/\/www.ics.uci.edu\/~fielding\/pubs\/dissertation\/rest_arch_style.htm#sec_5_1_2\">same<\/a>,\nwhat would you describe?<\/p>\n\n<p>What Phil (and those he links to) needs, I suggest, is\nsimply for these apps to to expose <em>all<\/em> their data via\nURIs in as standardized a form as possible, including parameterized\nstate transitions (i.e. a forms language).  Implicit in that\nrecommendation is that the data formats used must support and\nencourage linking, otherwise discovery of all the data becomes\nproblematic.<\/p>\n\n<p>Many self-described Web 2.0 apps, unfortunately, don&#8217;t\ndo those things.  They focus on only one aspect of Web 2.0 &#8211; more\ninteractive UIs &#8211; while forgoing the benefits offered by other\nimportant integration-simplifying aspects of it, such as\n<a href=\"http:\/\/www.paulhammond.org\/2006\/05\/opendata\/xtech.pdf\">open data<\/a>.<\/p>.<\/p>\n\n<p>Tags:\n<a href=\"http:\/\/del.icio.us\/tag\/rest\">rest<\/a>,\n<a href=\"http:\/\/del.icio.us\/tag\/wsdl\">wsdl<\/a>,\n<a href=\"http:\/\/del.icio.us\/tag\/integration\">integration<\/a>,\n<a href=\"http:\/\/del.icio.us\/tag\/web\">web<\/a>.<\/p>","protected":false},"excerpt":{"rendered":"Phil Windley says that we need a RESTful service interface description language. I don&#8217;t think we do. Interoperability requires agreement, and agreement begets commoditization. If all the interfaces are the same, what would you describe? What Phil (and those he links to) needs, I suggest, is simply for these apps to to expose all their [&hellip;]","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[22],"class_list":["post-1581","post","type-post","status-publish","format-standard","hentry","category-uncategorized","tag-rest"],"_links":{"self":[{"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/posts\/1581","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=1581"}],"version-history":[{"count":0,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/posts\/1581\/revisions"}],"wp:attachment":[{"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/media?parent=1581"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/categories?post=1581"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/tags?post=1581"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}