Skip to content

Pagination on temporal instances is incomplete / needs fixing

The current version of temporal pagination in the specification is not clear. It needs to be clarified and possibly extended.

From Benjamin Hebgen: "range-start" and "range-end" shall be of type DateTime. They depend on the requested time relationship timerel (as defined by clause 4.11), as follows: If the lastN parameter is present, pagination shall happen "backwards":

  • "range-start" shall be equal to "timeAt" for requests with timerel=before, "endTimeAt" for requests with timerel=between, or the most recent timestamp in the range of the response, for requests with timerel=after;
  • "range-end" shall be equal to the least recent timestamp in the range of the response;
  • "size" shall be equal to the requested lastN it basically the same as using timeAt endTimeAt and lastN only? right?

######################second question ################################### If the lastN parameter is not present, pagination shall happen "forwards":

  • "range-start" shall be equal to timeAt for requests with timerel=after or timerel=between, or the least recent timestamp in the range of the response, for requests with timerel=before;
  • "range-end" shall be equal to the most recent timestamp in the range of the response;
  • "size" shall be equal to "*". this part is what makes the difference it terms of order and allowing size *? but if we would allow lastN to be * it would be kind of the same as well ?

######################third question ################################### in case size or lastN is set we still have no way of getting the "next" part of the attribute pagination?