> 1. “Should native-endianness be a procedure or a value? The R7RS Large
usually does not have procedures like this …”  But R7RS Small does
(e.g. ‘jiffies-per-second’, which is another system-information
accessor like ‘native-endianness’).  I think it’s fine for this to be
a procedure.

OK.

 >  2. I would be happy to see more procedures from SRFI 207 added and
brought into line with SRFI 152.  I’m not sure why so many procedures
from the bytestrings SRFI are missing start & end arguments.

I'm thinking of pushing that off to a different SRFI, because this one
is pretty full as-is.

 > 4. Apparently (srfi 281 u8) exports ‘bytevector-s8-ref’ and
‘-s8-set!’ but not the ‘u8’ forms.  Typos?

Yes.

 > 5. “If this library is voted into R7RS Large, then all features are
supported, (scheme bytevector) must be the composite library, and
(scheme bytevector) not have any sublibraries.”  I’m not sure I
understand this sentence.

If this SRFI is voted in as (scheme bytevector), then (scheme
bytevector) exports all identifiers defined in this SRFI and does not
have the sublibrary structure of the SRFI.

The sublibrary structure is meant to facilitate the optional components,
such as certain sizes of allowed numbers. The R7RS-Large will not have
any difficulty implementing anything in here, so the division is not as
necessary.

 >  6. “The R6RS only has the static endianness macro, which cannot be
portably implemented in syntax-rules.”  How is it any easier to
implement ‘endianness?’ portably, if it accepts implementation-defined
symbols?

That is true, "portably" should be removed from that sentence.

 > 7. “[The serialization procedures] are no longer required to signal
errors.”  Why the change?  In another context, SRFI 281 says that
“error-raising behavior is more natural” than pushing on through
invalid elements.  Is there some rationale for signaling errors when
decoding Unicode but not when decoding hex- or base64-encoded data?
(I’d prefer signaling in these cases, too.)

After thinking about it, I've decided to restore signaling behavior to
the serialization procedures.

-- Peter McGoron