For the current draft, you can copy the R6RS[1] or R7RS[2] argument
conventions. So you don't need to say that “an &assertion-violation
exception is raised if str is not a string,” etc. you can make that
implicit. Similarly, you can add "iri" and "uri" to the argument
convention list, etc.

The argument restrictions are usually in a separate paragraph so that it
is easier to scan for.

Each instance of "fixnum" can probably be replaced with "exact integer,"
for R7RS implementations that don't have the concept.

[1]: https://r6rs.org/final/html/r6rs/r6rs-Z-H-9.html#node_sec_6.2
[2]: https://standards.scheme.org/r7rs-html5/index.html#1.3.3

-- Peter McGoron

On 8/18/26 10:25, D Guthrie wrote:
> Anyway, I've tried my best to be really explicit about what is raised, and any irritants raised also.

 > For the function specification the signatures probably aren't that
important given the language describing error-rasiing behaviour on input
types now, so these can probably be deleted in a subsequent draft.