> With library support in r6rs and r7rs we could even have the best of
> both worlds: have core procedures in (srfi N) and convenient/utility
> stuff in (srfi N extra) or something. Scheme implementors could choose
> to support just (srfi N) if they prefer minimalism.

Arthur and John know best about this topic, but I got the impression
that SRFIs are not intended to have optional parts. If optional features
are desired, the custom is to put them in a separate SRFI which has a
dependency on the other SRFI containing the core procedures. Cross-SRFI
dependencies are fine when they serve a purpose, and there are many
existing examples of them.

There is no particular need to have as few SRFIs as possible, so making
another SRFI for optional JSON stuff is probably no problem at all. We'd
just have to think of a good feature set for it.

I've had a few ideas for a SRFI that would have one or two procedures,
but haven't dared submit them :) It seems too trivial. But if the
procedures are really important for some job, maybe it's not.