- From: Larry Masinter <masinter@parc.xerox.com>
- Date: Wed, 14 May 1997 08:48:35 PDT
- To: Foteos Macrides <MACRIDES@sci.wfbr.edu>
- CC: kweide@tezcat.com, uri@bunyip.com
The way I think of it myself is that when you interact with a resource on the network ("http://whatever.com/blah") or even a local file ("file:///c|/downloaded/blah") and recieve some content from that resource and are viewing it, the viewer has another implicit resource: "the copy of the content that is being viewed now" Let's give it its own URL scheme "this:" where the scheme-specific part of "this:" is empty. Then what we want to assert is that URL references of the form "#xxxx" are *not* relative to the BASE at all, they're always relative to to "this:". That is, <A HREF="#blarg">...</A> is equivalent to <A HREF="this:#blarg">...</A> and different from <A HREF="file://localhost/download/blah#blarg">...</A> even when the buffer was read from "file://localhost/download/blah" in that following a "file:" link might well re-fetch the data in the case where the file has actually changed. I know many browsers have built-in URLs for some operations ("about:", "globalhistory:") and vaguely remember some reference to "back:" and "forward:" somewhere; but what we need to explain "#blarg" is "this:". Regards, Larry
Received on Wednesday, 14 May 1997 11:50:03 UTC