On Mon, 16 Nov 2020 21:07:54 -0500 Sean Conner <sean at conman.org> wrote: > This has come up before [1][2], and as I have stated [3][4], the '//' is > considered part of the host (or at least, a marker for the host portion of a > URL) and thus, I think the wording of section 2 should be changed to read > > <URL> is a UTF-8 encoded absolute URL, of maximum length 1024 bytes. > If the scheme of the URL is not specified, a scheme of gemini: is > implied. > "gemini:" is not a valid scheme. ":" is part of the URI and absolute-URI syntaxes defined in RFC 3986, not the scheme. The spec should be able to express any sensible acceptable URI syntax in terms of the syntaxes and terminology defined in RFC 3986. There's no need to add weird exceptions outside RFC 3986 that aren't already covered in it. For example, the spec can read: "<URL> is an UTF-8 encoded URI or network-path reference as defined in RFC 3986" (requests) and "<URL> is an UTF-8 encoded URI-reference as defined in RFC 3986" (links). If we want requests like "gemini.circumlunar.space/" to be valid, it can additionally read that <URL> allows suffix references. To call it an "absolute URL" is especially concerning since Gemini apparently allows fragments, but RFC 3986 defines an "absolute-URI" syntax which does not. -- Philip -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 488 bytes Desc: not available URL: <https://lists.orbitalfox.eu/archives/gemini/attachments/20201117/53a8 277c/attachment.sig>
---
Previous in thread (8 of 31): 🗣️ Philip Linde (linde.philip (a) gmail.com)
Next in thread (10 of 31): 🗣️ Ali Fardan (raiz (a) stellarbound.space)