- From: David Woolley <david@djwhome.demon.co.uk>
- Date: Sat, 10 Jan 2004 10:54:29 +0000 (GMT)
- To: www-style@w3.org
> If both http://example.com/foo/ and urn:xmp:foo result in the same > response to be rendered/handled, why does it matter? > (I'll admit that at the moment I have no idea what urn:xmp:foo means but > give me an hour and a google search) It matters because the browser has to go partway to fetching the URN before it can know that it resolves to the same URL. It might also resolve to a mirror URL which would require reverse resolution of the URN, a facility that I wouldn't expect to be implemented in many URN resolution schemes, and which would therefore require fetching the complete resource and comparing.
Received on Saturday, 10 January 2004 06:13:00 UTC