This would be nice to have. We can probably auto-extract it from <a
href="..."> tags or by searching the plain text of the document for
the regexp "SRFI\s+(\d+)".
It's a bit more curated than that. There would probably be far too many connections if we did that search.
Also, your srfi-data.scm categorizes each SRFI. That sounds useful.
Yes, thanks, I forgot about that. My categorization isn't great, and I would be grateful for help with that.
Just remembered: if the metadata files are in the same repo as each
SRFI's HTML, then it's easier to inspect changes to the metadata
whenever the HTML is updated (simply by using `git diff`). If the new
metadata looks OK then it can be committed, and people can use the git
log to see metadata changes in addition to HTML changes. I have a
feeling this might be a big help if/when debugging metadata problems.
Yes, that's a good point. Proximity is helpful for catching errors.