To: uri@bunyip.com
Subject: various
From: Larry Masinter <masinter@parc.xerox.com>
Message-Id: <93Jun4.151503pdt.2741@golden.parc.xerox.com>
Date: Fri, 4 Jun 1993 15:15:02 PDT
>> Tim B-L sez:
> This is the crux: Where do 99.9% of FTP URLs actually come from? FTP directory listings.
Oh. Most of *my* FTP URLs come from mail messages where people say
'this is available for anonymous FTP at this place', and I hand
translate it to a URL. Usually, if the file isn't a 'standard' format,
they'll say what it is.
>> Mitra sez:
> John , It seems the first thing we need is a format to combine them, then
> we can experiment with URformats etc knowing that systems that dont recognize
> your descriptor will ignore it gracefully.
> I'm not sure what this should look like, my gut feeling goes for
> something like.
> gopher:path.net//aaa/bbb/ccc:type=image/gif:size=100k
> or
> <gopher:path.net//aaa/bbb/ccc><type=image/gif><size=100k>
> or
> urn:isoc::12345:::ABCDE:gopher:path.net//aaa/bbb/ccc:type=image
> The tricky thing is handling all the special characters so that this can
> be passed unambiguously?
I kind of like the first one:
gopher:path.net//aaa/bbb/ccc:type=image/gif:size=100k
I think we probably need MIME types for things that don't have types
now, like naming a list of items:
directory/ftp directory/gopher
has this already been proposed? I don't see it in the MIME docs:
text/html
and probably things that don't really fit as types of 'data' but
should be registered, like:
telnet/vt100 telnet/mud