Has there been any thought to future proofing the API? I noticed there are several forward-looking comments about things like pagers which, if/when implemented, might cause some compatibility issues. Let's say, for instance, that a future version of the spec implements a paging option: it doesn't look like there's any provision for a client to know what version(s) the API server supports. This could be addressed in several ways, for instance requiring "/v1/" in the endpoint, or via content negotiation, each with its set of advantages and drawbacks. Just wondering if this was discussed at all.
Has there been any thought to future proofing the API? I noticed there are several forward-looking comments about things like pagers which, if/when implemented, might cause some compatibility issues. Let's say, for instance, that a future version of the spec implements a paging option: it doesn't look like there's any provision for a client to know what version(s) the API server supports. This could be addressed in several ways, for instance requiring "/v1/" in the endpoint, or via content negotiation, each with its set of advantages and drawbacks. Just wondering if this was discussed at all.