I have gone through and updated all existing EIPs to match this rule, including EIP-1.
In some cases, people were using markdown citations, I suspect because the long-form was a bit verbose to inline. Since the relative path is quite short, I moved these to inline but I wouldn't be opposed to putting them back to citation format if that is desired by the authors.
In doing the migration/cleanup, I found some EIP references to EIPs that don't actually exist. In these cases I tried to excise the reference from the EIP as best I could.
It is worth noting that the Readme actually already had this rule, it just wasn't expressed properly in EIP-1 and the "Citation Format" section of the readme I think caused people a bit of confusion (when citing externally, you should use the citation format).
* EIP-????: Add OpenRPC Service Discovery To JSON-RPC Services
* fix:
* fix(openrpc): add openrpc.json to eip assets
* fix(openrpc): reference eip asset
* Update EIPS/eip-1901.md - document link
* Delete openrpc.json
* Update eip-1901: move link to spec to top
* fix(1901): preamble + author github usernames
* fix(1901): add copyright info
* fix(1901): add link to eth json rpc spec
* fix(1901): type and category in preamble + spelling
* fix(1901): motivation section and use vendored assets
* fix(1901): add link to multi-geth OpenRPC discovery
* fix(1901): change ordering + small fixes
* fix(1901): typo
