Don't give so much weight to nips. They are there for those who need them. If you don't like a nip, leave it be. Not every client has to implement every nip and some are conflicting but those who want to support one way of doing things can use a nip to explain themselves. That's all these nips are. A formal definition instead of having software as a standard. Take away the nips and the first client that succeeds using some new feature will be the reference for others. With a nip, others are more protected against the first client to just change things all the time or make things unnecessarily complicated.