Updated/improved semantics of .../latest/... path in openEHR specifications

Specifications
1

There has been a clarifying change in the URL semantics of …/latest/… when it has been changed/improved to mean “latest released specification” rather than “latest development stuff we are working on”, the development stuff is now …/development/… instead of …/latest/…

The problem of changing URLs (Hypertext Style: Cool URIs don't change.) is that it may breaks links from other resources pointing to the thing that changed address or meaning. I have so far found these remaining issues when reading about new features that are in development but not yet officially released:

  • Some links in Jira issues predating the meaning change of …/latest/… (This likely needs a search followed by human judgment+editing to fix)
  • Some links in …/development/… that should likely have been relative in the source or conversion script seem to be absolute and point to …/latest/… instead of to …/development/…, see image below for example. (This likely needs an update of a documentation conversion/publish script to fix. Perhaps @sebastian.iancu or @thomas.beale know wich one?)

image
image1171×319 35.9 KB

2

Indeed, there is an issues around it. It happens when we have refs to specs that were not released yet, like in this case for TAGS, thus there is no ‘latest’ available.
I was more thinking of a general fallback on the routes, a sort of lucky-guess, where all http requests to inexistent ‘latest’ will be internally retried to ‘development’.

3

Using relative URIs (starting with e.g. ../ or /) in the specs instead of absolute URIs (starting with e.g. https://) would likely solve this automatically (browsing links within “development” would then link to “development” versions of the documents)