ols4
ols4 copied to clipboard
Should api/v2 to be api/v4 to match OLS version?
I think it probably should be, but it will be a lot of find/replace across the backend and frontend so we should make sure we've all committed everything we are working on (particularly @serjoshua) and freeze for a couple of hours while I do it. Maybe a good activity for a Thursday in the office!
I actually now think api/v4 should be api/raw, because it returns the raw owl2json objects without any abstraction. We can then plan a new api/v4 based on what we think the new API should look like, but because the frontend is in the same repo as the backend it's fine if it uses the "raw" API.
Or maybe this is just the v4 api and we have toggles to turn on and off levels of detail (e.g. reification), where everything on = the raw DB objects and everything off looks more like the v3 api.