(proposal) on metadata in documents

[Sean Conner]

It was thus said that the Great smlckz at tilde.pink once stated:
> On Sat, 14 Nov 2020, Sean Conner wrote:
> > Okay.
> >
> >Created 2020-11-14T17:34:19-0500
> >Modified 2020-11-14T17:50:03-0500
> >Copyright 2020 by Sean Conner.
> >
> > The timestamp was created with the following Unix command: "date +%FT%T%z"
> >so that's pretty easy.
> 
> That's one way of doing that. Can we do better than that?

  What's wrong with that format?  It's an ISO standard, it's locale neutral,
easy to parse, and it's easy for humans to read.  I don't think you really
can do better than that.  Unless you really want to parse dates like

	vuos, sk�b 16. b. 2020 02:27:32 CET

> >And you know, if you move the lines to the top of
> >the document, put the Modified: header first, a client would only have to
> >read the first 34 bytes of the document to see if it's modified, and if it
> >hasn't since the client last read it, the client can close the connection.
> >Caching solved!
> >
> > -spc (Add a Size header and you solve the size problem as well!)
> >
> 
> We don't want or need anything like that. That is a breaking change to the 
> spec so breaks all existing clients.

  Like adding headers isn't a breaking change?  And I'm not adding the size
to the MIME type, but to the other "fields", something like:

Created 2020-11-15T20:29:01-0500
Modifie 2020-11-15T20:29:01-0500
Copyright 2020 by Sean Conner
Size 806
Cache not-on-your-life
User-Agent myGeminiClient-1.13
MD5sum fd888c3218f34e71dc57221143d44ccb

> Let me change my wordings a little bit.
> 
> >>The metadata should be placed at the end of the document so that the
> >>viewers can view the content first.
> I should have said ''must'' instead of ''should''.

  Kill joy.

> >>The clients may use the information, but may not hide the metadata.
> ''must'' not hide.
> 
> mmmh..

  Mmmmmh indeed ...

  -spc