💾 Archived View for rawtext.club › ~sloum › geminilist › 005427.gmi captured on 2024-02-05 at 11:10:59. Gemini links have been rewritten to link to archived content

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

[SPEC] Backwards-compatible metadata in Gemini

Stephane Bortzmeyer stephane at sources.org

Mon Feb 22 10:15:37 GMT 2021

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

On Mon, Feb 22, 2021 at 12:46:22AM +0000, Oliver Simmons <oliversimmo at gmail.com> wrote a message of 69 lines which said:

Also for people that don't have nice link parsing it would look a

mess.

Why? These people would only see the text at the end of the line, notthe 'data:' link itself.

^^^

favicon: 🤗

author: Bob McBobface

last-edited: 22nd Feb 2021

The delimiter would work similar to the opening ``` toggle and there

would be no closing one, enforcing placing it at the end of the file.

I think that metadata are important, I find both easrng's and yourproposal fine. I tend to prefer yours since it degrades better forpeople who don't have metadata support in their clients. (On the otherend, easrng's is probably better for programs, while yours is betterfor humans, but both work for programs and humans, which I like.)

Now, some details:

What set of characters in the key (except the colon, of course)?LDH? ASCII letters or Unicode?

What about the value? Completely unstructured and thereforeunparsable? Your own example for "last-edited" is useless for programssince it does not fit any known standard for dates.

Will we need a list of standard keys, to avoid some people using"last-modified", others "last-edited" and others "last-change"?