{"id":125,"date":"2003-05-21T09:57:00","date_gmt":"2003-05-21T13:57:00","guid":{"rendered":"http:\/\/www.markbaker.ca\/wp\/?p=188"},"modified":"2003-05-21T09:57:00","modified_gmt":"2003-05-21T13:57:00","slug":"gauntlet-tossing","status":"publish","type":"post","link":"http:\/\/www.markbaker.ca\/blog\/2003\/05\/gauntlet-tossing\/","title":{"rendered":"Gauntlet Tossing"},"content":{"rendered":"<p>Yesterday, I <a href=\"http:\/\/lists.w3.org\/Archives\/Public\/www-tag\/2003May\/0069.html\">proposed<\/a>\na new issue to the <a href=\"http:\/\/www.w3.org\/2001\/tag\/\">TAG<\/a> regarding\nwhat I consider factual errors in the recently published draft of the\n<a href=\"http:\/\/www.w3.org\/TR\/2003\/WD-ws-arch-20030514\/\">Web Services Architecture document<\/a>\nconcerning the architectural property of\n<a href=\"http:\/\/www.ics.uci.edu\/~fielding\/pubs\/dissertation\/net_app_arch.htm#sec_2_3_5\">visibility<\/a>.\nYou can read the text for yourself, but I thought I&#8217;d explain why I raised this\nissue and not the more general and abundantly obvious &#8220;Web Services are\nincompatible with Web architecture&#8221; one.<\/p>\n\n<p>My principle motivation was that I wanted a very well defined,\nbite-size topic for the TAG to chew on; one that could be resolved\nin short order, but that still had &#8220;architectural impact&#8221; and\nrelevance to Web architecture.  In addition, I wanted to pick a topic\nthat the WSA WG had already agreed was important, but believed\nthey had it covered.  My end goal is that having this issue resolved in\nmy favour will be enough of a boot-to-the-head to the WG, that they\nmay see where they&#8217;ve erred, especially as the resolution will\npresumably drive home the critical point that application protocols\ndefine application interfaces.<\/p>\n\n<p>It&#8217;s a bit of a risk; perhaps the WG members won&#8217;t see it that way\nand I&#8217;ll have wasted an opportunity.  But I figure that all I need to\ndo is to convince <em>one<\/em> staunch Web services proponent, and then\nthe house of cards will topple.  Plus, it&#8217;s unlikely that discussion on\nthis topic will be able to avoid the more general problems with Web\nservices, so there&#8217;s an opportunity for additional issues to be raised\nby others.<\/p>\n\n<p>Smart move, or missed opportunity?  Time will tell.<\/p>","protected":false},"excerpt":{"rendered":"Yesterday, I proposed a new issue to the TAG regarding what I consider factual errors in the recently published draft of the Web Services Architecture document concerning the architectural property of visibility. You can read the text for yourself, but I thought I&#8217;d explain why I raised this issue and not the more general and [&hellip;]","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-125","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/posts\/125","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=125"}],"version-history":[{"count":0,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/posts\/125\/revisions"}],"wp:attachment":[{"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/media?parent=125"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/categories?post=125"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/tags?post=125"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}