- From: Henri Sivonen <hsivonen@iki.fi>
- Date: Tue, 14 Oct 2008 10:56:24 +0300
- To: Mark Baker <distobj@acm.org>
- Cc: "Marcos Caceres" <marcosscaceres@gmail.com>, public-webapps <public-webapps@w3.org>
On Oct 13, 2008, at 17:59, Mark Baker wrote: > file:, despite the name, doesn't have to be mapped to the file system. > Its scope could be limited in exactly the same way you've limited > widget: there. Similarly, ftp or http - even part of the space - > *could* be mapped to the file system. So the issue you're worried > about has little to do with the URI scheme. In an agent that supports both normal file/ftp/http URIs and widgets, special casing things like that seems troublesome on surface. What problem is solved by avoiding minting a new scheme and instead violating the principle of least surprise with an old scheme? Aren't URIs extensible at the scheme point in order to avoid forcing implementors to give special contextual meaning to existing schemes? -- Henri Sivonen hsivonen@iki.fi http://hsivonen.iki.fi/
Received on Tuesday, 14 October 2008 07:57:06 UTC