> 1. In the section "Rationale"
>> The bytevector-copy! procedure has a different argument order than the procedure in the R7RS base library.
>
> Not just argument corder, as discussed in
> https://codeberg.org/scheme/r7rs/issues/58, The main conflict lies in
> the `bytevector-copy!` functions in versions R6 and R7 is they interpret
> their last argument differently.

I have added that information.

 > 2.
> I don't understand why it can't be implemented in `syntax-rules`, since
> this SRFI just require it to raise an error on invalid endianness during
> the evaluation, not a syntax violation (the R6RS way).

The form must signal an error during expansion. I have modified the
specification to make that clear.

> 3. The title of "Encoding procedures" and "Decoding procedures" two
> sections were accidentally swapped.

Fixed.

> 4. The signature of make-bytevector has an extraneous argument
> "bytevector", do you mean (make-bytevector k [b8]) ?

Yes. Fixed.

>
> 5. The procedure (bytevector b8 ...) seems to be missing in SRFI, This
> is strange since it already had another lower level API make-bytevector.

Added.

-- Peter McGoron