Recently, PR#463 has been merged with the OPTIMADE Specification.
I have therefore created this issue to keep track of the adoption of this PR in the optimade python tools.
One question I still have is whether we should return the meta field in case the optimade version is less than 1.2. A client that would specifically request version 1.2 would not understand the fields under meta. So I am wondering if we could break older clients. On the other hand, the JSON API specification does mention that there could be fields under meta so in that sense an older client could expect that there are values there.
ToDo
Recently, PR#463 has been merged with the OPTIMADE Specification.
I have therefore created this issue to keep track of the adoption of this PR in the optimade python tools.
One question I still have is whether we should return the meta field in case the optimade version is less than 1.2. A client that would specifically request version 1.2 would not understand the fields under meta. So I am wondering if we could break older clients. On the other hand, the JSON API specification does mention that there could be fields under meta so in that sense an older client could expect that there are values there.
ToDo