Scheme Section 2 quibble

[Ali Fardan]

On Mon, 16 Nov 2020 21:19:16 -0500
Sean Conner <sean at conman.org> wrote:
>   It *is* allowed though---it's a schemeless URI and in a given
> context, it can be inferred.  Check out RFC-3986 section 5.2.2
> (Transforming Rreferences, aka, resolving a URL with a base URL) and
> section 5.3 (Component Recomposision) where ':' is appended to the
> scheme, and '//' is prefixed to the authority (host) section.
> 
>   So, given a URL like this:
> 
> 	//example.net/path/to/resource
> 
> in a resource, if the resource was served up via HTTP, then the
> scheme is 'http:'; if HTTPS, then 'https:' and if gemini, 'gemini:'.  
> 
>   A URL like this:
> 
> 	example.net/path/to/resource
> 
> is, again, per RFC-3986 parsing rules, to be interpreted as a path,
> not an authority section then path.  Need I create an example to show
> this?  I can.

You are correct.