Message-Id: <9408230831.AA22092=guido@voorn.cwi.nl>
To: "Roy T. Fielding" <fielding@simplon.ICS.UCI.EDU>
Subject: Re: Using "scheme:" with relative URLs
In-Reply-To: Your message of "Mon, 22 Aug 1994 17:11:18 MDT."
<9408221711.aa20012@paris.ics.uci.edu>
From: Guido.van.Rossum@cwi.nl
Date: Tue, 23 Aug 1994 10:31:16 +0200
> Not really. A relative URL should not normally include the scheme name.
> The only case in which it is needed is when the URL path contains a
> colon character before any other non-scheme characters,
[example omitted]
> For the first draft, I wanted to stick as close as possible to proven
> implementations (aside from introducing the specific requirements of
> Internet URLs). For the next draft, should the use of scheme: in front
> of relative URLs be removed? Or, should they be allowed but with a note
> added to the spec which describes the pitfalls?
Yuck! Using the "scheme:" prefix to prevent parsing ambiguities! Of
course the standard %xx quoting mechianism should be used. I'd say,
if the "scheme:" prefix is present, the URL can't be partial...
(BTW, in general your draft is a wonder of clarity. I'll start
implementing right away...)
(To the gentleman who wondered why relative URLs were useful apart
from saving some space: -- the short answer is, you can now move a
tree of inconnected pages to a different root without having to edit
their hyperlinks.)
--Guido van Rossum, CWI, Amsterdam <Guido.van.Rossum@cwi.nl>
<URL:http://www.cwi.nl/cwi/people/Guido.van.Rossum.html>