Then, if a state decides to stop doing DST, or any other funkiness like that, you can still get the time right.
Then, if a state decides to stop doing DST, or any other funkiness like that, you can still get the time right.
I should note that it is not possible to make a database of geolocation->UTC offset that is legal in all countries, since there are countries with disputed borders, some of which care very much that no software imply the "wrong" border.
> If you're worried about the future timestamp being at a specific local time (say 10 AM on a future date), it's actually better to store a naive time and a location than the IANA timezone name.
Europe/Oslo would be the IANA name for mainland Norway (Svalbard and Jan Mayen are in different IANA regions).
If you're meeting somewhere at a specific time, you might as well specify that place really precisely (Maybe: Nidaros Cathedral, Trondheim, Norway) and then use that place to infer the proper UTC offset when the date approaches.
There's no perfect solution as landmarks, names, &c. can all change.
Sorry yeah, this is the one I was thinking of when I said Oslo/Norway.
Agree with your other points as well.
I guess to increase the long term robustness one could record some additional data:
GPS coordinates for the intended event
GNSS coordinates using another system such as BDS or GLONASS for the intended event
The current time with time zone at the time when the record was created
The IANA name of the location where the record was created