Re:RFC 3339 vs. ISO 8601
by wahern on Thursday August 31, 2023 @03:43PM
(#37342696)
In the OP's example, 2023-11-05 01:30:00 America/New_York, 1:30AM occurs twice as at 2:00AM the clock rolls back to 1:00AM. Normally this is resolved by including a disambiguating timezone, EDT (first 1:30AM) or EST (second 1:30AM). But if there's no timezone indication to accompany a geographical location, there's no way to disambiguate the time.
[ Parent
| on HN ]
Re:RFC 3339 vs. ISO 8601
by deathanatos on Thursday August 31, 2023 @04:03PM
(#37342957)
If there's no flag indicating DST. America/New_York is the timezone designation.
Part of what makes TZ discussions incredibly difficult is that people play fast and loose with the terminology.
I think the person you're responding to is simply saying that if you made the meeting in a non-DST observing zone, the meeting time would still wobble in a DST-observing zone. (I'm not sure why they're noting it, because my comment also clearly spells that out, too, albeit in reverse. But yes, it works both ways.)
Right, to pick an actual time stamp for a particular local time in a particular location, you need to first choose at what time stamp to resolve the time offset for the location. Then in that time offset you can unambiguously map the localtime to a unique time stamp.