I came across a fairly recent RFC on “URI Fragment Identifiers for the text/plain Media Type”. I ran a few tests on the URL itself in Chrome and IE to no avail. For example:
https://stackoverflow.com/robots.txt#line=50
Should work similar to:
https://stackoverflow.com/about#footer
How do I write a Greasemonkey script to do the following:
- Map the table of contents to the line it references and add a hyperlink to each table of contents listing which maps to the respective line number?
The closest thing is the addrable project. It is targeting the
text/csvMIME type, and has jQuery and NodeJS implementations. Outside of the browser landscape, Canonical Fragment Identifiers for ePub would be a bridge between plain text and markup.References
addrable-core.js
readium-cfi.js
Chromium Issue 77024: RFC 5147 plain text position fragments
Microsoft Connect Issue 652715: RFC 5147 Plain Text Positions Given as URI Fragment
W3C Existing Technologies Survey: Existing URI Fragment Schemes
Aggregating Media Fragments in Collaborative Mashups(pdf)
RFC Repository of programming RFC's with ability to direct-link sections or even lines?