💾 Archived View for gemi.dev › gemini-mailing-list › 001074.gmi captured on 2024-06-16 at 15:37:02. Gemini links have been rewritten to link to archived content

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

In Body URI references from non Gemini content

1. (indieterminacy (a) libre.brussels)

📅 Sent: 2021-11-11 14:33
📧 Message 1 of 1

Hello all,

I have been thinking further about how to represent in body references
from non Gemini content within Gemini - building upon this thread I initiated:
=> gemini://gemi.dev/gemini-mailing-list/messages/006684.gmi 2021-06-13 In 
Body URI references

Id like to propose the use of a non actionable '=>' to reference that
there is an inline uri and that (all things being in order) an
actionable uri is below (either directly below or in a collection at the
bottom of the document).

# Example
When 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>

# Justifications
An advantage of this would be that the Gemini reader will not have the
visual 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's
specifications.

However, given the amount of non-Gemtext content with inlink uri content
and comments there may be an advantage for making use of semiotics of
'=>' for Gemini centric browsers and parsers.

WDYT?


Jonathan

Link to individual message.

---

Previous Thread: Geminispace Statistics Visualized

Next Thread: gmipay v1.2 released, with subscription support