{"id":1916,"date":"2007-02-23T10:55:33","date_gmt":"2007-02-23T14:55:33","guid":{"rendered":"http:\/\/www.markbaker.ca\/blog\/2007\/02\/23\/that-human-targetted-argument-again\/"},"modified":"2007-02-23T10:55:33","modified_gmt":"2007-02-23T14:55:33","slug":"that-human-targetted-argument-again","status":"publish","type":"post","link":"http:\/\/www.markbaker.ca\/blog\/2007\/02\/that-human-targetted-argument-again\/","title":{"rendered":"That human-targetted argument again"},"content":{"rendered":"

I wanted to expand a little on\nmy dismissal<\/a>\nof Sanjiva’s argument<\/a> that “The Web is necessarily human centric”.<\/p>\n\n

Sanjiva, in his support for – and authorship of – WSDL, presumably wants to permit developers to publish their own service-specific interfaces, such as ones supporting methods like the canonical “getStockQuote”, or even “getRealtimeStockQuote”. And I’m certain he’d claim that these are very much machine-facing interfaces, since that’s supposed to be the whole point of Web services. So far so good?<\/p>\n\n

So why is a system built around GET suddenly not<\/em> machine facing? I’ve said before that the one thing<\/a> that most distinguishes SOA and REST is the uniform interface of the latter; it says , in part, that the more general the operation, the more reusable the interface. In other words, using the example above, getStockQuote is more reusable than getRealtimeStockQuote. Moreover, GET is more reusable than getStockQuote.<\/p>\n\n

By following that logic – that more general means more human-targetted – then one can only conclude that the methods most suited for machine-targetting will be the most specific ones. So never mind getRealtimeStockQuote, we’d need getRealtimeStockQuoteForGOOGonNASDAQ.<\/p>\n\n

Of course, that’s silly. So is the argument that the Web is only for humans. I hope (hah! 8-) that this finally puts that argument to rest (pun intended).<\/p>","protected":false},"excerpt":{"rendered":"I wanted to expand a little on my dismissal of Sanjiva’s argument that “The Web is necessarily human centric”. Sanjiva, in his support for – and authorship of – WSDL, presumably wants to permit developers to publish their own service-specific interfaces, such as ones supporting methods like the canonical “getStockQuote”, or even “getRealtimeStockQuote”. And I’m […]","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[22,25,48,37,38],"class_list":["post-1916","post","type-post","status-publish","format-standard","hentry","category-uncategorized","tag-rest","tag-soa","tag-softarch","tag-webarch","tag-webservices"],"_links":{"self":[{"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/posts\/1916","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=1916"}],"version-history":[{"count":0,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/posts\/1916\/revisions"}],"wp:attachment":[{"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/media?parent=1916"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/categories?post=1916"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/tags?post=1916"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}