- From: <roconnor@Math.Berkeley.EDU>
- Date: Mon, 19 Nov 2001 14:26:23 -0800 (PST)
- To: <www-talk@w3.org>
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, 19 Nov 2001, Leigh Dodds wrote: > "What is at the end of a namespace" is an FAQ asked by users, not > browsers (at least in my neck of the woods!). > > Using the 'http:' scheme as a NS identifier has caused confusion > because there is an expectation that this can be pasted into a browser > location bar, and the browser will talk to an HTTP daemon and have it > resolve to something. Despite the fact that these http URIs don't > actual appear in a webpage, but in an NS declaration in some arbitrary > XML document (i.e. in a context where it is intended to be used as an > identifier only). This can't be right. ``Clearly'' if http://www.example.com/bar is sitting around somewhere, then telnet www.example.com 80 (some-command) bar HTTP/1.1 ought to do something meaningful for some value of some-command. I guess I'm willing to accept that (some-command) might not be GET. In this case entering ``http://www.example.com/bar'' into a location bar might not do something, and then your right about it not working. Still there should be some value for (some-command) that should return a response code of the form 2xx or 3xx, no?. (204 would be acceptable) (Notwithstanding, 502 errors etc.) - -- Russell O'Connor roconnor@alumni.uwaterloo.ca <http://www.math.berkeley.edu/~roconnor/> ``This is not a time, as it is never a time, to seek vengeance, but a time to seek the courage to forgive'' -- George W. Bush -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (SunOS) Comment: For info see http://www.gnupg.org iD8DBQE7+YcUZG3em5NXM14RAhWrAJ9j5j2np92XwjQD/lOlHM9Fr/FOXACfYnhH p+uTvvpAvH6HoAI390qY0oU= =Nlm1 -----END PGP SIGNATURE-----
Received on Monday, 19 November 2001 17:26:31 UTC