On 29/01/2023 11:09, Jean Louis wrote:
* Tim Cross [2023-01-28 00:15]:
• Offset (fixed)
• This captures the idea of "when did it happen for the person who
------------------------------------^^^^^^^^^^^^^^^^^^^
Jean, you missed it.
made the observation"
• e.g., 2007-02-03T04:00:00.000+01:00
Offset is not that fixed, maybe from viewpoint of storage as maybe it
...
I think your misinterpreting the intent here. If you specify a timestamp
with offset, it is fixed.
That is what you say. And I am pointing out to international standard
references.
You reference and verbose message are hardly relevant. Since something
has already happened, time offset is known. DST can not change it,
either it is effective or not at this moment.
2007-02-03T04:00:00.000+01:00
can not be unambiguously attributed to an IANA timezone ID, however it
precisely specifies UTC time (time in seconds since epoch, etc.).
Usually (but not necessary) it means 04:00 local time in a timezone 1
hour ahead of UTC that moment (you may use it to specify 05:00 in
timezone having +02:00 offset). It is enough for a lot of applications.
There are important enough reasons to consider (and maybe discard to
still use offset) IANA timezone ID for scheduling an event in future.
Both options should be possible.
