Hi again,

I don't *really* want to bring this up but I think it's important to
at least acknowledge that the RFCs are officially deprecated in favor of
the WHATWG "living standard" document.

This document emphatically has no formal grammar, which makes it
unnecessarily difficult for implementors to follow and verify that the
implementation matches the spec.  I've written about this before:
https://www.more-magic.net/posts/an-appeal-to-whatwg-uri-spec.html

I stand by this, and on top of that the WHATWG is unversioned.  They
euphemistically refer to this as a "living standard", but it basically
means you're building on quicksand - IIUC, there are no guarantees that
the language described by the document today will be the same as that
described by the same document a year from now.

Sure, you can look at the git repo, but there's no clear "anchor" for
anyone to rely on like static RFC numbers.

Anyway, enough about my personal grievances with WHATWG.  My point is
that this is the spec the browsers use and some modern URI parser libs
follow (at least partly), so the SRFI should probably mention how it
relates to that spec, even if just repeating the problems I see with it.

Cheers,
Peter