How about using this rubric to decide when to invest in updating legacy APIs to meet new governance models? Ive been working with an organisation on a two-track API governance model where new APIs are built to meet recently-introduced standards/style guides/best practices whereas existing/legacy APIs are updated by being defined using a specification file and added to the internal catalogue but otherwise left alone to avoid breaking changes, etc. any further thoughts on whether this rubric could be used to help decide when to invest in updating legacy APIs to the new standards and when to just leave them as they are?
How about using this rubric to decide when to invest in updating legacy APIs to meet new governance models? Ive been working with an organisation on a two-track API governance model where new APIs are built to meet recently-introduced standards/style guides/best practices whereas existing/legacy APIs are updated by being defined using a specification file and added to the internal catalogue but otherwise left alone to avoid breaking changes, etc. any further thoughts on whether this rubric could be used to help decide when to invest in updating legacy APIs to the new standards and when to just leave them as they are?