- From: Ted Hardie <ted.ietf@gmail.com>
- Date: Mon, 15 Oct 2012 13:00:14 -0700
- To: Larry Masinter <masinter@adobe.com>
- Cc: Robin Berjon <robin@w3.org>, Anne van Kesteren <annevk@annevk.nl>, "plh@w3.org" <plh@w3.org>, "Peter Saint-Andre (stpeter@stpeter.im)" <stpeter@stpeter.im>, "Pete Resnick (presnick@qualcomm.com)" <presnick@qualcomm.com>, "Martin Dürst (duerst@it.aoyama.ac.jp)" <duerst@it.aoyama.ac.jp>, "www-archive@w3.org" <www-archive@w3.org>
On Mon, Oct 15, 2012 at 11:37 AM, Larry Masinter <masinter@adobe.com> wrote: > I think that's the bigger implication -- the vision that the web supplants all other (network) apps; for some systems, "URLs to non-Web things" is an empty set. > > My understanding of Peter's survey of other specs that make reference to RFC 3987 was that there weren't any whose implementations relied on anything other than the browser to do URL/IRI resolution and processing. > First, can you provide a pointer to the survey? Second, while there may be systems for which the only handle for URIs is the the browser, there are certainly systems for which that is not true. To pick one produced close to when URIs became a full standard, look at RFC 4088 (http://tools.ietf.org/html/rfc4088). I doubt there are many browsers which dereference URIs like snmp://example.com/bridge1;800002b804616263 with their own handlers. URIs used internally to systems outside the web may not be easily seen in a web-based corpus, but that does not mean that they are not there, nor that shifting the parsing rules won't effect them. regards, Ted Hardie
Received on Monday, 15 October 2012 20:00:42 UTC