Am Sa., 26. Juni 2021 um 13:15 Uhr schrieb Lassi Kortela <xxxxxx@lassi.io>:

- The name of the organization comes from `#! /usr/bin/env
scheme-script`. This convention has existed for a long time, but we
haven't figured out a scheme-script implementation that is useful for
writing complex, portable scripts. If the scheme-script organization
amasses a big collection of non-trivial scripts, we will have a good
body of work that shows what features are needed in a useful
`scheme-script`. A SRFI could then be written from that basis.

`scheme-script' is part of R6RS and is assumed to point to an implementation of R6RS. I wouldn't reuse the name for interpreters of other Scheme dialects as this can cause confusion or can clash with existing R6RS implementations in the search path.

Of course, R6RS and R7RS are similar enough so that one can write a script using their common syntax and semantics as long as the `scheme-script' implementation has access to enough libraries (including the base libraries `(rnrs base (6))' and `(scheme base)').

SRFI 22 suggests `scheme-XXX' where XXX corresponds to the version of Scheme.