A question regarding section 1.2 of the spec

[Ali Fardan]

On Sun, 15 Nov 2020 09:13:54 +0000
cbabcock at asciiking.com wrote:
> Your use of "reserved" here probably reflects a misunderstanding. You
> can have a URI with a query indicator without getting a 1x response
> code first.

To clarify, I was referring to being reserved for the use in a
standardized protocol specific function.

> The word "reserved" in the spec only ever refers to characters that
> must be escaped.

The word "reserved" refers to characters that must be escaped in RFC
3986, not in the Gemini spec, I was specifically referring to the case
where the query portion of the URI in 1X requests is reserved
specifically for user input therefore it can't be used for other
purpose in that specific case.

I was pointing out the fact that the Gemini spec referred to the query
portion of URI as "allowed and have no special meanings beyond those
defined by the generic syntax", this is confusing because A) the query
portion does have meaning in the context of user input responses, and in
that case it is actually reserved and can not be used for other purpose
B) "the generic syntax" is vague term.

What were you referring to by "the spec", did you mean RFC 3986 or the
Gemini spec?