@Kevin_Mcgahey - I’m getting to something similar. I want to have my API evolve as the data structure changes, while still retaining compatibility. I’ve thought of using views of concept clusters with the version number in them to maintain compatibility as the underlying tables evolve (eg, Users-3.2.4), but I’m unconvinced that’s a good idea because it would proliferate views.
Now that we’re looking at V3 on the horizon, Sven’s question still seems important - are we going to /api/v3? Is that vX available for me to use? And are there any good best practices for applying, eg. SEMVER to data apis? Bonus points for mapping to Google’s best practices on the topic.
Thanks,
Josiah