<-- back to the mailing list

[SPEC] Backwards-compatible metadata in Gemini

Stephane Bortzmeyer stephane at sources.org

Wed Feb 24 12:24:26 GMT 2021

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

On Tue, Feb 23, 2021 at 05:49:19PM -0500, Sean Conner <sean at conman.org> wrote a message of 112 lines which said:

Years ago, there was an extention for Firefox (back when I think it
was just known as Mozilla) that would use metadata in the <HEAD>
section of a web page to construct a navigation bar for the site.
The metadata included:

Actually, it is a concrete form ("serialization") of links, which arean abstract concept, and can be in HTTP headers ('Link:'), in HTMLtext, in Atom feeds, etc.

The standard for links is RFC 8288<gemini://gemini.bortzmeyer.org/rfc-mirror/rfc8288.txt>.

next next "page" in the collection
previous previous page in the collection
first first page in the collection

All these are official standardized types of links, in the IANAregistry<https://www.iana.org/assignments/link-relations/link-relations.xml#link-relations-1>. Forinstance, "canonical" was registered in RFC 6596<gemini://gemini.bortzmeyer.org/rfc-mirror/rfc6596.txt> to link to thecanonical URI of this resource.