Sorry, I may be wrong, but community processes (such as SRFI) are
sometimes seen as a sign of "endorsement" for something by the said
community, and I just don't see the case for endorsing INI files by Scheme
(broadly understood).
SRFIs in particular are just requests for implementation. So John is just asking implementers to include INI parsing and generation, and providing a simple sample implementation. SRFIs only really turn into endorsements once the implementers adopt them.
As a legacy-supporting interface, obviously, such a library is very
useful, but wouldn't a snow2 package be more appropriate in such a
case?
I'm happy to have both!