Terms for describing time-dependent data *This is a public review draft that may incompatibly change any time.* This collection supports temporal requests To address an entity in a resource path or path to related resources, a point in application time must be specified as described in [OData-Temporal, section 4.2.1]. The addressed entity is then a snapshot of the data at the given point in time. The temporal collection MUST NOT contain two entities with the same object key as defined by their `ObjectKey` properties and with overlapping application-time periods as defined by their `PeriodStart` and `PeriodEnd` properties. The temporal collection always contains all entities (with consecutive time periods) for a given object key. The properties `PeriodStart` and `PeriodEnd` MUST NOT be present if the entity type of the `Timeslice` already contains period start and end, that is, if the collection on which the action is invoked has visible timeline. If present, they MUST have the same type, either `Edm.Date` or `Edm.DateTimeOffset`, depending on the `ApplicationTimeSupport/UnitOfTime` of the collection. The update behavior for a given object key is known from the [SQL statement](https://www.ibm.com/docs/en/db2oc?topic=statements-update) `UPDATE ... FOR PORTION OF BUSINESS_TIME ... WHERE ...`. `deltaTimeslices` with non-matching object keys and non-overlapping sub-periods of `deltaTimeslices` are disregarded. The delta time slices need not contain all properties, but at least the boundary values of the period to change. An absent object key property matches any key property value. New time slices are processed in the order of the collection, which especially matters if some of the specified change periods overlap. The delta time slices must contain all properties that are needed for insertion. New time slices are processed in the order of the collection, which especially matters if some of the specified change periods overlap. The delta time slices need not contain all properties, but at least the lower boundary of the period to change. An absent object key property matches any key property value. New time slices are processed in the order of the collection, which especially matters if some of the specified change periods overlap. The deletion behavior for a given object key is known from the [SQL statement](https://www.ibm.com/docs/en/db2oc?topic=statements-delete) `DELETE ... FOR PORTION OF BUSINESS_TIME ... WHERE ...`. The sub-period of an existing time slice that lies outside a given instance of `deltaTimeslices` is kept, effectively shortening the time slice. The delta time slices contain only the boundary values of the period to delete and (parts of) the object key. An absent object key property matches any key property value. The delta time slices contain only the lower and optionally upper boundary values of the period to delete and (parts of) the object key. An absent object key property matches any key property value.