💾 Archived View for gemi.dev › gemini-mailing-list › 000763.gmi captured on 2024-06-16 at 14:28:33. Gemini links have been rewritten to link to archived content

View Raw

More Information

⬅️ Previous capture (2023-12-28)

-=-=-=-=-=-=-

[spec] List of proposed clarifications

1. Adnan Maolood (me (a) adnano.co)

I'd like to keep track of proposed clarifications to the Gemini
specification, since they seem to get buried in the mailing list. So
I've made a list and published them on my capsule:

=> gemini://adnano.co/gemini-spec-proposals/

Note that this is meant to keep track of proposed clarifications only,
not new features.

Let me know if I've missed anything.

Link to individual message.

2. Stephane Bortzmeyer (stephane (a) sources.org)

On Sun, Feb 28, 2021 at 10:23:12AM -0500,
 Adnan Maolood <me at adnano.co> wrote 
 a message of 10 lines which said:

> Let me know if I've missed anything.

=> gemini://gemini.bortzmeyer.org/gemini/missing.gmi My own list

And it's not complete, there is also:

Is there a difference between an empty path and a path of / ?

And certainly others.

Link to individual message.

3. colecmac (a) protonmail.com (colecmac (a) protonmail.com)

Hello,

Please look at the 2020 thread called "[spec] Oustanding issues". Here[1] is the
first message from that thread, and if you Ctrl-F for that heading on this[2]
page you'll find all the messages. For example, these fixes I proposed are still
needed:

gemini://gemi.dev/gemini-mailing-list/messages/003827.gmi
gemini://gemi.dev/gemini-mailing-list/messages/003911.gmi

1: gemini://gemi.dev/gemini-mailing-list/messages/004447.gmi
2: https://lists.orbitalfox.eu/archives/gemini/2020/thread.html

Hopefully your page and this thread will be helpful for our new BDFL, who will
need to make these changes.


makeworld

Link to individual message.

4. Stephane Bortzmeyer (stephane (a) sources.org)

On Sun, Feb 28, 2021 at 10:23:12AM -0500,
 Adnan Maolood <me at adnano.co> wrote 
 a message of 10 lines which said:

> I'd like to keep track of proposed clarifications to the Gemini
> specification, since they seem to get buried in the mailing list. So
> I've made a list and published them on my capsule:
> 
> => gemini://adnano.co/gemini-spec-proposals/

Now that we have an issue tracker to follow the work on the final
specification <https://gitlab.com/gemini-specification>, you may want
to turn this page into tickets at this issue tracker and/or to add
ticket numbers and links in your page.

>From your list:

=> https://gitlab.com/gemini-specification/protocol/-/issues/3 Clarify 
that META cannot be empty
=> https://gitlab.com/gemini-specification/protocol/-/issues/3 Clarify 
that META cannot contain LF before the final CRLF
=> TODO Clarify that Gemini URL queries MUST (not SHOULD) use %20 instead of +
=> https://gitlab.com/gemini-specification/protocol/-/issues/2 Clarify 
that servers MUST send TLS close notify before closing the connection
=> TODO Clarify that clients MUST NOT send fragments to the server [IMHO, 
RFC 3986, section 3.5 is clear enough]
=> TODO Clarify the purpose of alt text

Link to individual message.

---

Previous Thread: [spec] Clarify purpose of alt-text

Next Thread: [spec] mercury highlights ☿️