> Let's focus on getting the client API and the subprocess protocol right.
> Then a Scheme library that talks to a subprocess (hopefully using
> S-expressions or ASN.1 rather than a bespoke serialization)

Can you write a one-page femto-ASN.1 spec that has unsigned integers,
UTF-8 strings, booleans, null, and either lists/conses or vectors?
Similar to your Bottom Scheme proposal for a really minimal Scheme. That
would give me a concrete set of building blocks on which to base my
understanding.

I'm not opposed to a bespoke protocol if it's completely generic and
really simple. Things like that are in short supply. May be best if
ASN.1 can be subsetted as is.

> that speaks the
> SQLite API will be both portable and usable, and will get the SRFI
> finalized.  A second implementation will be a Good Thing for
> standardization, and of course many more can follow.

I'd strongly suggest having both SQLite and PostgreSQL implementations
before finalizing anything. But then, a Postgres C driver has already
been started :)