Maybe we agree then?
If the proposal is clearly written, and some non-tiny group of people want to follow this standard, then it should be in this repo. If there are a couple of implementations, and all the technical objections have been addressed, then it should be merged
Merging doesn't mean that the maintainers of the repo think that the proposal is the right solution to the problem. i.e.. the same process as is used in BIPs, where the maintainers own judgement/preference/opinion is not relevant
