💾 Archived View for rawtext.club › ~sloum › geminilist › 005806.gmi captured on 2024-03-21 at 16:37:27. Gemini links have been rewritten to link to archived content

View Raw

More Information

⬅️ Previous capture (2021-11-30)

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

<-- back to the mailing list

Split Gemini spec into two specs?

Katarina Eriksson gmym at coopdot.com

Mon Mar 1 12:02:13 GMT 2021

- - - - - - - - - - - - - - - - - - - 

Apparently, I sent this only to Oliver Simmons and not to the list.

On Tuesday, February 23, 2021 7:07 PM, Katarina Eriksson <gmym at coopdot.com> wrote:

Oliver Simmons <oliversimmo at gmail.com> wrote:
At current the Gemini spec is dual-purpose, it describes the protocol,
and the text/gemini format.
Whilst gemtext is the "native" format for Gemini (as HTML is to HTTP),
one isn't required for the other to work, they are two distinct
things.
I think that they should be split into two specs, one for the protocol
and one for gemtext.
What would people think of this?
- Oliver Simmons (GoodClover)
Here's a thread about it from May last year:
https://lists.orbitalfox.eu/archives/gemini/2020/001037.html
It resulted in some rearranging of the order it appeared in the specification.
Solderpunk's thoughts about it:
https://lists.orbitalfox.eu/archives/gemini/2020/001070.html
Personally, I don't have strong opinion one way or the other.
-- 
Katarina