{"id":112,"date":"2003-03-16T22:05:00","date_gmt":"2003-03-17T02:05:00","guid":{"rendered":"http:\/\/www.markbaker.ca\/wp\/?p=201"},"modified":"2003-03-16T22:05:00","modified_gmt":"2003-03-17T02:05:00","slug":"strawmen","status":"publish","type":"post","link":"http:\/\/www.markbaker.ca\/blog\/2003\/03\/strawmen\/","title":{"rendered":"Strawmen"},"content":{"rendered":"<p>Sam, in apparent response to my claims that some people see constraints\nas bad things, <a href=\"http:\/\/intertwingly.net\/stories\/2003\/03\/15\/nounVsVerb.html\">writes this<\/a>;<\/p>\n\n<blockquote>\nThere are those who appear to advocate a null architectural style with respect to data.  Who claim that content type independence is not a bug but a feature.  Who imply that few constraints on data is a good thing.  Of course, there are no such people, this is only a strawman argument.\n<\/blockquote>\n\n<p>Very well.  I was hoping to not have to name names, but here are\nsome quotes from some very smart people who don&#8217;t understand what an\narchitectural constraint is, or its value (or at least didn&#8217;t when they\nsaid what I&#8217;m quoting 8-), and who are implicitly suggesting that less\nconstraints are better.  And FWIW, I never said that anybody was advocating\nusing the null style, only that it was the implicit result when you make\narguments such as these.<\/p>\n\n<ul>\n<li><a href=\"http:\/\/lists.w3.org\/Archives\/Public\/www-ws-arch\/2002Sep\/0142.html\">&#8220;Constraint implies limitation.\nThe way Web services uses layering removes limitations&#8221;<\/a><\/li>\n\n<li><a href=\"http:\/\/lists.w3.org\/Archives\/Public\/www-ws-arch\/2002Sep\/0084.html\">&#8220;The criteria should be at the architecture level, not at the implementation level.  I would say that web services architecture allows for stateless web services&#8221;.<\/a>  Needs to be read in context.<\/li>\n\n<li><a href=\"http:\/\/lists.w3.org\/Archives\/Public\/www-ws-arch\/2002Sep\/0084.html\">&#8220;As before, there is nothing in web service architecture that precludes caching&#8221;<\/a>.  Same message as the last one, but further demonstrates a misunderstanding of software architecture, as I explained in my <a href=\"http:\/\/lists.w3.org\/Archives\/Public\/www-ws-arch\/2002Sep\/0086.html\">response<\/a>.<\/li>\n<\/ul>","protected":false},"excerpt":{"rendered":"Sam, in apparent response to my claims that some people see constraints as bad things, writes this; There are those who appear to advocate a null architectural style with respect to data. Who claim that content type independence is not a bug but a feature. Who imply that few constraints on data is a good [&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-112","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/posts\/112","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=112"}],"version-history":[{"count":0,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/posts\/112\/revisions"}],"wp:attachment":[{"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/media?parent=112"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/categories?post=112"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/tags?post=112"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}