This page defines the common superclass pattern used across Grunddatamodellen registries on Datafordeleren.
The goal is to avoid repeating the same temporal and status semantics in every dataset page.
Common Superclass Attributes
All core entities inherit the same temporal/status backbone:
| Name | Type | Multiplicity | Meaning |
|---|---|---|---|
id | Identifikation | 1 | Stable object identifier |
registreringFra | DateTime | 1 | Transaction-time start (when recorded) |
registreringTil | DateTime | 0..1 | Transaction-time end (null = still current in register timeline) |
registreringsaktør | CharacterString | 1 | Actor that recorded the change |
virkningFra | DateTime | 1 | Valid-time start (when true in real world) |
virkningTil | DateTime | 0..1 | Valid-time end (null = still valid) |
virkningsaktør | CharacterString | 1 | Actor responsible for validity assertion |
status | StatusType | 1 | Domain status (for example active/inactive) |
Why This Matters
These fields encode the dual-time model:
- Transaction time (
registrering*): what the register knew and when. - Valid time (
virkning*): what was true in reality and when.
This is the core bitemporal interpretation used in SemanticGIS workflows.
Query Modes
Current
Use latest active state only.
Temporal
Use valid-time history while keeping current registration perspective.
Bitemporal
Use both valid-time and registration-time history.
Interpretation Rule
Always state the temporal question explicitly:
- What was valid at time
T? - What was registered/known at time
R?
Do not mix these questions implicitly in one extraction.