repo: gemini-site
action: commit
revision: 
path_from: 
revision_from: e40677edba03533543e708dc09e86ea503454823:
path_to: 
revision_to: 

commit e40677edba03533543e708dc09e86ea503454823
Author: Solderpunk 
Date:   Sun Jul 21 20:48:26 2019 +0000

    Finalise link syntax.

diff --git a/spec-spec.txt b/spec-spec.txt

--- a/spec-spec.txt
+++ b/spec-spec.txt
@@ -1,7 +1,7 @@
 -----------------------------
 Project Gemini
 "Speculative specification"
-v0.0.3, June 24th 2018
+v0.0.4, July 21st 2018
 -----------------------------

 This is a very rough sketch of how I imagine the actual spec for
@@ -136,12 +136,22 @@ handling non-text types.

 Response bodies of type text/gemini are a kind of ultralight hypertext
 format inspired by gophermaps.  The format is line-based.  Any line
-which can be parsed as having the following structure:
+which begins with the two character prefix "=>" is a link, analogous
+to a gopher menu item with an item type other than "i" (full syntax
+below).  All other lines are just text and should be presented as-is,
+analogous to a gopher menu item with item type "i", but without the
+overhead of the dummy item type, selector, host and port.

-[|]
+Link lines have the following format:

-should be treated as a link, analogous to a gopher menu item with an
-item type other than "i".  All other lines are just text and should be
-presented as-is, analogous to a gopher menu item with item type "i",
-but without the overhead of the dummy item type, selector, host and
-port.
+=> []
+
+where  is any non-zero number of consecutive spaces or
+tabs and the square brackets indicate that the user-friendly name is
+optional.  The whitespace between the => and the URL is optional.  All
+the following examples are valid links:
+
+=> gemini://example.org/
+=> gemini://example.org/ An example link
+=> gemini://example.org/foo	Another example link at the same host
+=>gemini://example.org/bar Yet another example link at the same host

-----END OF PAGE-----