Commit 10000036 authored by Martin Bauer's avatar Martin Bauer
Browse files

Added clause 7.4.2.5 Temporal pagination

parent eebe97d6
Loading
Loading
Loading
Loading
+15 −0
Original line number Diff line number Diff line
@@ -1729,6 +1729,21 @@ Entities no longer fulfilling the filter criteria of the query. As a result, the
first page when going backward, and the last page, when going forward, may have
less than the maximum number of Entities.

#### 7.4.2.5 Temporal pagination

Temporal representation of resources adds an additional dimension to the pagination.
Depending on the requested time range, the response will contain multiple instances
of the requested Attribute, and therefore an additional pagination mechanism for
those temporal representations is required, in order to limit the time range of the
response. If no limits are specified, a default limit is enforced, depending on
implementation specific configurations. 

Temporal pagination can be done in ascending order using the _`firstN`_ parameter
and in descending order using the _`lastN`_ parameter, whose respective value (N) 
indicates the **limit**, i.e. the maximum number of temporal instances of any
Attribute allowed on a page. _`offset`_ is used to select the respective page
in the chosen order.

## 7.5 Counting results

Given that NGSI-LD Query operations can potentially return a result set