https://en.m.wikipedia.org/wiki/Tz_database
Even this is not enough for some edge cases like “I shall take my supper every day at 6pm, Jeeves” but one can always find exceptions to anything.
The suggestion above is to have the zone in the timestamp. ISO-8601 and RFC-3339 put the offset in the timestamp.
Zone and offset are different concepts: the up-thread comment's poster's example of Europe/London is one zone, that currently has two offsets, depending on time of year.
The up-thread comment includes a very practical example that any app dealing with something like an "appointment" would have to reckon with.
Including fixed UTC offsets was a massive mistake and it should have never happened. Anything except named timezones is useless.
Otherwise, I'm also always left wondering whether they really meant CET or actually CEST, calculating what the current offset of CET is, double-checking whether there's some other CET that I might be confusing things with (China Eastern Standard Time?) etc.
It is only scheduling future events where they fall down. Calendars and scheduling are demanding applications.
But I do love the `date` utility, which allows alphanumeric time zone abbreviations pretty well.