Date: Sun, 13 Mar 94 12:35:25 CST
Message-Id: <9403131835.AA01329@boombox.micro.umn.edu>
From: "Mark P. McCahill" <mpm@boombox.micro.umn.edu>
To: uri@bunyip.com
Subject: Mark acting as Tim's proxy:gopher section of the URL document
Below is what Tim has in the Gopher section. I very strongly suggest that this
be replaced with the Gopher section I proposed, but I have good reasons for
this :-).
According to Steven Foster (one of the guys who builds the Veronica indexes
of gopherspace) by December 1993, 1/3 of the Gopher servers accessible on the
net were Gopher+ servers. We find that 85 - 90% of the new server registrations
we do are Gopher+. I NEED a URL that encompasses Gopher+ items so I can point
to Gopher+ forms, abstracts, and all the other cool stuff in Gopher+.
Anyway, here is Tim's revision of the draft:
-----------------------------------------------------------------
Gopher
The first character of the URL path (after the initial single slash) is a
single-character "type" field which is that used by the Gopher protocol. The
rest of the path is the "selector string", with disallowed characters encoded.
Note that some selector strings begin with a copy of the gopher type character,
in which case that character will occur twice consecutively in the URL. If the
type character and selector are omitted, the type defaults to "1". Gopher links
which refer to non-Gopher protocols are represented directly as URLs of the
underlying access method and are not represented as Gopher URLs.
[Whether extensions are required, and if so what, for Gopher+ is under
discussion, and a new draft exists.. - tbl 3/93]
-----------------------------------------------------------------
Mark P. McCahill
gopherspace engineer/University of Minnesota
mpm@boombox.micro.umn.edu
612 625 1300 (voice) 612 625 6817 (fax)