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

View Raw

More Information

⬅️ Previous capture (2021-11-30)

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

<-- back to the mailing list

[SPEC] Backwards-compatible metadata in Gemini

Oliver Simmons oliversimmo at gmail.com

Mon Feb 22 11:04:41 GMT 2021

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

On Mon, 22 Feb 2021 at 10:48, Stephane Bortzmeyer <stephane at sources.org> wrote:

My question still holds. Should values be unstructured or should we
have structured types (dates, datetimes, numbers, URIs, etc)?

Unstructured data wouldn't be much more useful than people juststicking these in the file as plain text. :P

All the usual standards for dates/numbers/URIs should be followed.

As I said before, a list of common keys/values should be a thing.Anyone could write any freeform keys/values, but a list of commonlyused & supported key/values should be maintained, this should includewhatever format the values follow.

It should be freeform such that I could come along and decide I wantto use a new key and nothing should break, clients will ignore it ifthey don't recognise it.Metadata is not just for the machines, e.g an `author` key would bemainly for people interested in who wrote something.