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

commit b829541d7f6583d40306dbf885ecf6e8024de6ba
Author: Solderpunk 
Date:   Sun Jun 23 14:41:54 2019 +0000

    Describe gemini map format.

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.1, June 21st 2018
+v0.0.2, June 23st 2018
 -----------------------------

 This is a very rough sketch of how I imagine the actual spec for
@@ -134,7 +134,14 @@ non-text responses to the disk and that's it.  Clients for unix
 systems may consult /etc/mailcap to find installed programs for
 handling non-text types.

-Response bodies of type text/gemini are...
+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:

-...some kind of very lightweight hypertext *thing*.  Maybe kinda like
-gophermaps?  Very under development...
+
+
+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.

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