There are several references in whenToUseGet-20030509.html which reference RFC 2396 (URI) which are clearly intended to reference RFC 2616 (HTTP). I think there is an architectural blind spot in this DRAFT TAG Finding, in that it does not note that there are URIs other than "http" URIs or give any consideration for the use of such. "An important principle of Web architecture is that all important resources be identifiable by URI. " Is it an architectural principle that they be identifiable by HTTP URI? By a URI in a particular set of preferred schemes for which "GET" and "POST" make sense? Most of the finding is nonsense if the URI scheme is "mailto" or "data" or "urn". Larry -- http://larry.masinter.netReceived on Friday, 30 May 2003 23:26:48 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 26 April 2012 12:47:17 GMT