[REQ] Element IDs in the web specification

[Brian Evans]

> From: Sean Conner <sean at conman.org>
>   On the plus side, there are two RFCs (RFC-5147 and RFC-7111) that define
> URI fragment semantics to particular resource types.  Downside, they don't
> directly apply to text/gemini.
> 
>   One method would be to use verbatim text as the ID, starting from the
> start of the line.  So for your use case:
> 
> gemini://gemini.circumlunar.space/docs/specification.gmi#%235%20The
> 
> the fragment portion, decoded, would be "# 5 The" (note:  the '#' here is
> encoded as %23).  The client would then scan through the document in
> question looking for a line that starts with "# The" and position the
> document accordingly in the window/viewport/terminal.
> 
>   The second method would be to adapt the one for text/plain (RFC-5147).
> 
>   The two methods have the advantage of not modifying text/gemini and could
> be a convention of clients util some method clearly beomces the winner.
> 
>   -spc
> 

I'm sorry I wasnt more clear: I had meant for the web version adding ID
attributes would be useful.

That said, I like the idea of using the fragment portion on gemini in the way you
describe. If I get some time I may try to mock this up and see if I can get it to
work. :)

-- 
Sent with https://mailfence.com
Secure and private email