> > From: Henry S. Thompson > > . . . . > > _What's a URI and why does it matter?_ > > http://www.ltg.ed.ac.uk/~ht/WhatAreURIs/ > > > > Feedback welcome, Very nice write-up! FYI, regarding the question posed near the end: "There is real debate underway at the moment as to whether it is correct for a web server to return a 200 OK response code in a response to a request for a URI which identifies a non-information resource." I believe I have provided a fairly compelling line of reasoning to conclude: http://dbooth.org/2007/splitting/#httpRange-14 "Therefore, the use of a URI to directly denote both an information resource and a non-information resource should be viewed as a violation of good practice, but *not* a violation of Web architecture." Though of course your mileage may vary. :) David Booth, Ph.D. HP Software +1 617 629 8881 office | dbooth@hp.com http://www.hp.com/go/software Statements made herein represent the views of the author and do not necessarily represent the official views of HP unless explicitly so stated.Received on Monday, 26 January 2009 21:14:59 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:56:23 GMT