Add rules regarding the anchor text for BIPs, W3C, IETF, WHATWG

[SamWilsn]

          Would still like the rules regarding the anchor text.

Originally posted by @Pandapip1 in:

• Update EIP-1: Add W3C as a permissible origin #7111 (review)
• Update EIP-1: Update EIP-1 to allow link to BIPs #6907 (comment)
• Update EIP-1: Add IETF as a permissible origin #7113 (review)
• Update EIP-1: Add WHATWG as a permissible origin #7117 (review)

[Pandapip1]

As is evidenced by the fact that I was the one suggesting this, +1. We have rules for referencing EIPs, so it only makes sense to do the same with other references.

[SamWilsn]

I thinking we re-use the same logic (for the most part) that we do for EIPs themselves:

• RFCs must be referenced with the form RFC N (not RFCN or RFC-N)

• BIPs must be referenced with the form BIP N (not BIPN or BIP-N)

Not sure how we want to handle WHATWG though.

[Pandapip1]

Not sure how we want to handle WHATWG though.

Require that it use the spec's title?

[github-actions]

There has been no activity on this issue for 1 week. It will be closed after 3 months of inactivity.

[github-actions]

There has been no activity on this issue for 1 week. It will be closed after 3 months of inactivity.

[github-actions]

There has been no activity on this issue for 1 week. It will be closed after 3 months of inactivity.

[github-actions]

This issue was closed due to inactivity. If you are still pursuing it, feel free to reopen it and respond to any feedback.