Do not get me wrong, but is there really a need to make this an SRFI?
The format is simple, the implementation is straightforward

I mean, INI files are generally very varied, and frankly ill-defined.
Sometimes repeated sections are expected to override each other,
sometimes they are expected to be read as a list, and sometimes they
are forbidden. This is just a single example.

On Thu, 11 Aug 2022 at 03:21, Arthur A. Gleckler <xxxxxx@speechcode.com> wrote:
>
> Scheme Request for Implementation 233,
> "INI files,"
> by John Cowan (text), Arvydas Silanskas (code),
> is now available for discussion.
>
> Its draft and an archive of the ongoing discussion are available at https://srfi.schemers.org/srfi-233/.
>
> You can join the discussion of the draft by filling out the subscription form on that page.
>
> You can contribute a message to the discussion by sending it to xxxxxx@srfi.schemers.org.
>
> Here's the abstract:
>
> An INI file is a configuration file that consists of key-value pairs for properties, and sections that group the properties. The name of these configuration files comes from the filename extension INI, short for initialization. The format has become an informal standard in many contexts of configuration. This SRFI provides access to the contents of an INI file.
>
> Regards,
>
>
> SRFI Editor

--
Yours sincerely, Vladimir Nikishkin
(Sent from GMail web interface.)