News for hackers. Stuff that matters.
Re:RFC 3339 vs. ISO 8601 by tadfisher on Thursday August 31, 2023 @01:41PM (#37340934)
What if London doesn't exist by the event time?
Re:RFC 3339 vs. ISO 8601 by klysm on Thursday August 31, 2023 @01:43PM (#37340972)
Then the scheduled time is probably irrelevant so who cares
Re:RFC 3339 vs. ISO 8601 by MichaelZuo on Thursday August 31, 2023 @01:49PM (#37341084)
Not necessarily the scheduled event may be in some other city in a different time zone that wants this timezone for the convenience of scheduling attendees from across the world.
Re:RFC 3339 vs. ISO 8601 by gumby on Thursday August 31, 2023 @02:28PM (#37341706)
In which case a new calendar appointment will be circulated to the survivors with location and details. This mechanism already exists and is surely adequate.
Re:RFC 3339 vs. ISO 8601 by MichaelZuo on Thursday August 31, 2023 @05:31PM (#37343945)
The point is to have some means, some facility, to schedule things 100% correctly in advance. If there literally is no possible method then that's a pretty surprising aspect of computer systems circa 2023.
Re:RFC 3339 vs. ISO 8601 by gumby on Thursday August 31, 2023 @07:40PM (#37344980)
The real world is messy. We can't even predict when the sun will be overhead at any given location a decade or so in advance.

This is why I left computer science research. I realized I was working on things that only made sense inside the machine.

Re:RFC 3339 vs. ISO 8601 by klysm on Friday September 01, 2023 @12:38AM (#37346854)
Such an absolute perspective on the utility of computer science isn’t very pragmatic. Computers have the power to interact with the real world, and play a major part in billions of lives every day.
Re:RFC 3339 vs. ISO 8601 by throw0101a on Thursday August 31, 2023 @02:09PM (#37341397)
> What if London doesn't exist by the event time?

Europe/London will be either be left alone for historical purposes, or aliased to its successor for backwards compatibility.

See Type: Link and Source file: backward:

* https://en.wikipedia.org/wiki/List_of_tz_database_time_zones

Re:RFC 3339 vs. ISO 8601 by gumby on Thursday August 31, 2023 @02:27PM (#37341689)
Might be hard to meet there without radiation protection.
Re:RFC 3339 vs. ISO 8601 by rini17 on Thursday August 31, 2023 @02:31PM (#37341741)
You are either joking or you really think a RFC to cover such changes is possible? If so, do you have any examples in mind? Cities that stop existing is not a new problem.
Re:RFC 3339 vs. ISO 8601 by kzrdude on Thursday August 31, 2023 @02:47PM (#37341954)
I have never thought about it before, but are timezone names like 'Europe/London' designed to not be sensitive to political changes and not have to change?

It could have been Country/City or Region/Country but it's Continent/City instead.

Continents or regions of the world don't change fast or due to politics (not often) and cities aren't renamed or disapear that often, so this scheme is probably a lot more stable than any that uses political entities. (Think about countries that split or rename or become occupied, the locations of cities like Sevastopol (occupation), or Juba (Sudan/South Sudan split) or Jerusalem (every controversy).)

Re:RFC 3339 vs. ISO 8601 by fanf2 on Thursday August 31, 2023 @03:48PM (#37342752)
Yes, the city is chosen to be the most populous in the time zone. There’s a long discussion of the policy in https://www.ietf.org/timezones/theory.html
Re:RFC 3339 vs. ISO 8601 by Karellen on Thursday August 31, 2023 @03:17PM (#37342348)
I'm content for that to be a failure mode of the format. :-)
Re:RFC 3339 vs. ISO 8601 by cesarb on Thursday August 31, 2023 @03:46PM (#37342732)
> What if London doesn't exist by the event time?

Or what if it's split into two cities, which half were you talking about? This has famously happened with Berlin.