[SPEC] Backwards-compatible metadata in Gemini

• 🗣️ From: Stephane Bortzmeyer (stephane (a) sources.org)
• 📅 Sent: 2021-02-22 10:15
• 📧 Message 4 of 99

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, not
the '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 your
proposal fine. I tend to prefer yours since it degrades better for
people who don't have metadata support in their clients. (On the other
end, easrng's is probably better for programs, while yours is better
for 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 therefore

unparsable? Your own example for "last-edited" is useless for programs
since 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"?

---

Previous in thread (3 of 99): 🗣️ Louis Brauer (louis (a) brauer.family)

Next in thread (5 of 99): 🗣️ Petite Abeille (petite.abeille (a) gmail.com)

View entire thread.