(proposal) on metadata in documents

[text at sdfeu.org]

Reading about favicon in Gemini by way of an extra request to the host 
serving a requested document, I searched for "metadata" in old threads.

It seems to me the quoted message from 2020-11-14 below could serve as a 
solution to the debate.

Note that the favicon RFC basically uses this approach itself, stating 
some `key: value` pairs within the document.

=> gemini://mozz.us/files/rfc_gemini_favicon.gmi RFC: Adding Emoji 
Favicons to Gemini

Why not use this kind of structured metadata lines for an (as per RFC 
still unmotivated) favicon convention?

Favicon: #


On Sat, 14 Nov 2020 17:07:30 +0000, smlckz wrote:

> I am proposing a convention of putting human and machine readable
> metadata in documents (in ''geminisphere''). This is completely optional
> for document writers.
> 
> The metadata should be placed at the end of the document so that the
> viewers can view the content first.
> 
> For now, I am proposing the following metadata for inclusion in
> documents (all of which is optional):
> 
> *  the date (and maybe time) when the document was published
> 
> *  the date (and maybe time) when the document was last modified
> 
> *  copyright information and/or license of the document
> 
> IMO, we should use ISO 8601 for the date/time in metadata.
> 
> The clients may use the information, but may not hide the metadata.
> The spiders/bots can also use the information (when indexing/archiving
> documents) as well.
> 
> Now the question for you is how the metadata is formatted?
> Please share your thoughts on it.
> 
> 
> ~smlckz