Small correction to my own reply: NIP-32 lists `e`, `p`, `a`, `r` and `t` as the targets and describes them as "events, people, relays, or topics respectively". So by the text, `r` means relays, not w...
Good correction. I would keep the page anchor in NIP-22 with I=<normalized URL> and K=web, then make the score a separate replaceable event with an explicit namespace and version. That cleanly separates a comment about a page from a rating claim, while a receipt can bind the fetched bytes or content hash and observation time without pretending the URL itself is immutable.
1
