By Ether DataRequest data sample
Interactive publication
Back to the catalogue
ClocksCase 09 of 10

Timestamp provenance (which time became canonical)

Sensor time, API time, database time, and client time are different instants. Which one became the canonical event time (and therefore the slot) is a modeling decision that must travel with the value, exactly like geometry provenance in the geo KB.

Class
Case to account for
Affects
2 conversions
01

Detection

A record carries several time columns and the canonical stage is not declared.

02

Mitigation

01
Carry the full lifecycle (observed/captured/received/ingested/stored/reported) and name the canonical stage.
03

Affected conversions

Timestamp + zonehour-of-week slot
OPEN
Instant(ISO week × slot) key
OPEN