https://srfi.schemers.org/srfi-275/srfi-275.html#utf-8-interpretation

> If the information is available, then invalid sequences of UTF-8
octets should raise an assertion violation with the offending octet and
its position within the bytevector as irritants. This information may
not be available, in which case the irritants consist of the irritants
are the offending octet alone.

Is signalling an error required (with the irritants depending on the
information available), or is signalling optional? If signalling is
optional, what are the allowed behaviors on invalid UTF-8 bytes?

Also, is an assertion violation raised even when the text specified "an
error" is raised?

____________________

https://srfi.schemers.org/srfi-275/srfi-275.html#notation-and-convention

SRFI 97 libraries have a library name that precedes the sublibraries. So
the SRFi 97 convention would be:

* (srfi :275 uris-and-iris iri)
* (srfi :275 uris-and-iris uri)
* (srfi :275 uris-and-iris normalize)
* (srfi :275 uris-and-iris path)
* (srfi :275 uris-and-iris utils)

I would also note the R7RS-Small convention, which is similar to what is
currently in the SRFI:

* (srfi 275 iri)
* (srfi 275 uri)
* (srfi 275 normalize)
* (srfi 275 path)
* (srfi 275 utils)

_____________________

https://srfi.schemers.org/srfi-275/srfi-275.html#iri-authority

Procedures should generally return the same number of values for each
invocation. If not, it is difficult to use the procedure in a let binding:

     (let-values (((user host port) (iri-authority iri)))
       ;; Unspecified what happens when the procedure returns a single #f
       ...)

-- Peter McGoron