💾 Archived View for rawtext.club › ~sloum › geminilist › 007587.gmi captured on 2023-11-04 at 12:18:01. Gemini links have been rewritten to link to archived content

View Raw

More Information

⬅️ Previous capture (2021-11-30)

-=-=-=-=-=-=-

<-- back to the mailing list

In Body URI references from non Gemini content

indieterminacy at libre.brussels indieterminacy at libre.brussels

Thu Nov 11 14:33:43 GMT 2021

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

Hello all,

I have been thinking further about how to represent in body referencesfrom non Gemini content within Gemini - building upon this thread I initiated:=

https://lists.orbitalfox.eu/archives/gemini/2021/006684.html 2021-06-13 In Body URI references

Id like to propose the use of a non actionable '=

' to reference thatthere is an inline uri and that (all things being in order) anactionable uri is below (either directly below or in a collection at thebottom of the document).

ExampleWhen presenting non Gemini text, could it be wise to adapt:<text><signifier-for-uri><uri><uri-comment><text>

Into:<text><opening-parenthesis><space><this-'=>'

<space><alphanumeric-reference><space><uri-comment><closing-parenthesis><text>

JustificationsAn advantage of this would be that the Gemini reader will not have thevisual clutter of the uri-reference but still the content

Norms could be to consider:* Line(s) immediately following with-regex /^=

<uri> <alphanumeric-reference> <optional-content>/ to-signify the LOCAL uri-reference* Lines preceeding end-of-document with-regex /^=
<uri> <alphanumeric-reference> <optional-content>/ to-signify the GLOBAL uri-reference

I accept it would be heresy for such an approach to be in Gemini'sspecifications.

However, given the amount of non-Gemtext content with inlink uri contentand comments there may be an advantage for making use of semiotics of'=

' for Gemini centric browsers and parsers.

WDYT?

Jonathan