Deprecating a standard before retirement

[mattyfirth]

Is there a concept of deprecating a standard prior to retirement, to give the community time to make any necessary changes at their end before the standard is retired?

I'm familiar with the sunsetting process for deprecating an API before it can be retired, and we are now looking to align how we sunset our standards - we have initially gone down a deprecation then retirement route, but this guidance may suggest that it's unnecessary?