> On the other hand, it has one extra bit of information:
 > cross-reference information, so that I can generate "see also" links
 > from one SRFI to another, e.g. for when one SRFI is intended to
 > obsolete another, or is an alternative proposal to another.

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+)".

Also, your srfi-data.scm categorizes each SRFI. That sounds useful.

 > I'm flexible.  I just want to maintain editorial control over what
 > appears on the SRFI web site, so I would want copies of the data to
 > appear in the SRFI Git repos so that I could review changes before they
 > were pushed to the site.

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.