authorship tag

[Sean Conner]

It was thus said that the Great Petite Abeille once stated:
> 
> 
> For one, as both an author & a reader, I like to have text anchored in
> time. Nothing happen in a vacuum.
> 
> gemini and text/gemini have no notion of time at all.
> 
> Instead people tend to compensate by haphazardly leaving contextual
> breadcrumbs here and there about such basic information:
> 
> ⇲ gemini://gemini.conman.org/gRFC/
> => 0001 0001 2019-08-01 PROPOSED MIME type and parameters for Gemini Index Files
> => 0002 0002 2019-08-01 ACCEPTED Resource request format for Gemini
> => 0003 0003 2019-08-01 PROPOSED Response header to include optional file size in reply
> => 0004 0004 2019-09-06 PROPOSED Gemini index format

  If you check those links, you'll see I already include such metadata in
the document itself, not just on the link line.  So the above links are not
a good example for you here.

> The authorship tag gives a simple and consistent way to embed such date in
> the text/gemini document itself.

  In a machine readable way.  And the "authorship" is not authorship per se,
but the authority.  The tag: URI includes either a domain *or* an email
address.  It's meant to be used for identification of a resource, not
authorship of a document.

> Furthermore, the tag provides, well,  authorship information: who did it?
> 
> E.g. gemini.circumlunar.space/~solderpunk points to solderpunk actual home
> at circumlunar.
> 
> This could be used creatively, by, say, uniquely styling ~solderpunk
> documents with sigil, color scheme, whatnot:
> 
> ⌂ gemini.circumlunar.space/~solderpunk → f01c0885 → 4028369029 → ~lapryt-fidseg → sigil
> 
> This provides a more stable and granular alternative to the host IP
> address or certificate.
> 
> Finally, the tag itself is rather readable on its own:
> 
> tag:gemini.conman.org <http://gemini.conman.org/>,2019-08-01:gRFC/0002 <gemini://gemini.conman.org/gRFC/0002>#20:46:12

  It would help your case if you generated valid tag: URIs, like:

	tag:gemini.conman.org,2019-08-01:gRFC0001:PROPOSED:Sean%20Conner

But that's not easy for humans to parse (they can) because of the encoding
and the lack of actual whitespace.

  -spc