{"id":222,"date":"2003-11-26T10:39:00","date_gmt":"2003-11-26T14:39:00","guid":{"rendered":"http:\/\/www.markbaker.ca\/wp\/?p=91"},"modified":"2003-11-26T10:39:00","modified_gmt":"2003-11-26T14:39:00","slug":"feedback-on-building-the-web","status":"publish","type":"post","link":"http:\/\/www.markbaker.ca\/blog\/2003\/11\/feedback-on-building-the-web\/","title":{"rendered":"Feedback on "Building the Web""},"content":{"rendered":"

Stefan Tilkov thoughtfully responded<\/a>\nto my “Building the Web with Web services” blog. Here are some of his comments.<\/p>\n\n

In response to my assertion that documents\/state don’t ask anything of anyone, he writes;<\/p>\n\n

\nEr … well, I think I can see the point, but I can’t really make sense of the examples. So, a purchase order isn’t asking anything from anyone? That can’t be true – so obviously, these are counter examples – a purchase order is asking something. Looking at the paragraph, even for some length of time, I have problems finding out what exactly Mark is getting at – I fail to see the similarity between a pure piece of data like current time and a very concrete, business level document like purchase order. Arguably, it’s just not phrased very clearly, or maybe it’s because I’m not a native English speaker.\n<\/blockquote>\n\n

A purchase order isn’t asking anything of anyone; it’s just capturing the state of\nsome order. It can be used to ask something of somebody. For example, I could give\nit to a skywriter, and they could write the XML out in smoke overhead. Or I could give\nit to an archiving service which promises to keep a copy around for some period of time.\nOr, I could give it to a purchasing department with the intent that they fulfill the\norder. But all those actions are where I’m asking somebody to do something. What would\nyou do if you found a paper purchase order lying in the street? Do you know the intent\nof its author? No.<\/p>\n\n

He also added this;<\/p>\n\n

\nWhile Mark obviously was thinking of content negotiation, support for Expired headers and so on, he doesn’t talk about it at all. How is anybody supposed to make sense of that?\n<\/blockquote>\n\n

I quite intentionally (though I slipped some in at the last minute, sigh) tried to avoid mentioning Web\nterms where I could, and just talk about the general approach. I did this because in my experience, once\nyou start using Web terms, people automatically import their preconceived views of the Web … which\nis what I’m trying to fix.<\/p>\n\n

And then this;<\/p>\n\n

\nOK, I’m a bit puzzled by now, but surely things are going to be clarified in the next few sections. (Seriously, that’s what I thought when I first read the article). Imagine my surprise when I saw that the next paragraph’s title is Conclusions:\n<\/blockquote>\n\n

Well, that’s all there is! 8-) The intent of the essay was to describe how the Web relates to\ndocument style Web services; that if you add identification of the things whose state is\nrepresented by those documents, make semantics uniform and explicit on the wire in the form of\nan application protocol, and dereferencing of identifiers to request a document, that you’ve\ngot the Web.<\/p>\n\n

Thanks for the constructive comments, Stefan. I know how easy it is to get\nall kneejerky on this. It just seems that the industry is SO<\/em> close to\nfinally understanding the Web, that I feel an obligation to jump up and down and\nyell “Yo, over here, we’ve already got one of those!”.<\/p>","protected":false},"excerpt":{"rendered":"Stefan Tilkov thoughtfully responded to my “Building the Web with Web services” blog. Here are some of his comments. In response to my assertion that documents\/state don’t ask anything of anyone, he writes; Er … well, I think I can see the point, but I can’t really make sense of the examples. So, a purchase […]","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[40],"class_list":["post-222","post","type-post","status-publish","format-standard","hentry","category-uncategorized","tag-xml"],"_links":{"self":[{"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/posts\/222","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=222"}],"version-history":[{"count":0,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/posts\/222\/revisions"}],"wp:attachment":[{"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/media?parent=222"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/categories?post=222"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/tags?post=222"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}