Scheme Section 2 quibble

[Sean Conner]

It was thus said that the Great John Cowan once stated:
> 
> Requires a small breaking spec change to remove the sentence about
> defaulting to "gemini://" in 5.4.2 and preferably in 2 as well.  But 5.4.2
> is self-contradictory and has to be fixed.
> 
> My proposal is to rewrite section 2 to say this:
> 
> <URL> is an absolute URL according to RFC 3986, of maximum length 1024
> bytes.
> 
> And to rewrite section 5.4.2 to say this:
> 
> <URL> is a URI reference according to RFC 3986.

  I've gone over the path month of logs [1] on my Gemini server and pulled
some stats.

	Total number of requests:		103,422
	Total number of schemeless requests:	    275

And of the schemeless requests:

	client #1	  2 requests
	client #2	  3 requests
	client #3	270 requests

  Given the relative rarity of such requests (0.2% of all requests) and the
number of clients requesting schemeless requests (between 0.3% to 8% [2]) I
would agree with this proposal.  A Gemini request is an absolute URL (per
RFC-3986).

  -spc

[1]	It's all I keep

[2]	Okay, on the Gemini software page [3], I count 37 known clients. 
	There are some others not listed, like CAPCOM, Spacewalk and GUS,
	but even excluding those, 3 out of 37 is 8%.  And assuming that all
	1,187 unique IP addresses were using a unique client, then the
	percentage falls to 0.3%.  The truth is somewhere in between.

	Also, my server probably gets hit by *every* client, as it serves up
	the Gemini Client Torture test.

[3]	https://portal.mozz.us/gemini/gemini.circumlunar.space/software/