💾 Archived View for rawtext.club › ~sloum › geminilist › 005590.gmi captured on 2023-11-14 at 09:59:46. 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

Lars Noodén lars.nooden at gmx.com

Wed Feb 24 20:11:07 GMT 2021

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

On 2/24/21 9:34 PM, Oliver Simmons wrote:[snip]

Whilst it's true anyone could use any key/values, I would hope that we
are civilised enough to be able to agree on what keys and values we
use.[snip]

I agree, if that is about settling on the way of writing arbitrarykey-value pairs within Gemini documents. That would be somethinganalogous to what would be the meta element in XHTML:'

<meta name="..." content="..." />

The spec there provides the element. The people using the spec fill inthe data themselves through their own choice. It is then up to them touse or write software on their site which takes advantage of it to offerone or more ways to navigate the accrued metadata. Or not.

The actual contents of the key-value pairs, the actual metadata itself,would not be part of the spec, not even the keys. It would not beappropriate to try to impose a custom vocabulary or even any existingschemes like the Library of Congress Subject Headings (LCSH), MedicalSubject Headings (MeSH), Universal Decimal Classification (UDC), Lööv,or any other vocabulary.

/Lars