Right, the implementation is in the srfi text.
I just made a PR to fix links to SLIB and its document.

On Fri, Oct 23, 2026 at 8:18 AM Arthur A. Gleckler <xxxxxx@speechcode.com> wrote:
>
> On 2026-10-23, Peter Bex <xxxxxx@more-magic.net> wrote:
>
> I was looking into older SRFIs (in particular, 33 and 60) for which the texts both mention reference implementations, but contain no links. The "main page" for both points to a GitHub repo with only the HTML text. I see that for other old SRFIs like 1, 13 and 14, there's a .scm file in the GitHub repo that sits beside the HTML files.
>
> The reference implementation for SRFIs 33 and 60 are in the documents themselves. We avoid doing that in more recent SRFIs because it makes it harder to fix the implementation after the SRFI is published. (The document is supposed to remain unchanged after finalization.)
>
> Also, note that we call them "sample implementations" now. John Cowan says that there's a widely used distinction between term "sample implementation," which has no normative value, and "reference implementation," which implies that the implementation itself is normative, i.e. defines the specification. In SRFIs, the non-normative meaning has always held.
>
> Finally, I'm a bit unclear what the files srfi-60-1.[1245].html are for. There's some lines like "Revised:" in some, so I presume they're draft revisions, but not all of them have this, so it's a bit unclear. And there's no srfi-60-1.3.html. Apologies if this has been discussed before, but I couldn't find anything using the search of these archives.
>
> At the time, the editors sometimes maintained old drafts with version numbers in their filenames. I've preserved such files for older SRFIs, but we now rely only on version control, including git tags, to track drafts (and errata and finalization).