<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><br>
</p>
<p>This is basically what I was about when asking for the "scope" of
tzdb, and might end up in a similar discussion concerning timezone
ids just like the Wikipedia's inclusionism/exclusionism debate.</p>
<p>Standpoints:</p>
<p>a) (Exclusionist) Timezone ids should be kept at a minimum level
required to model tz rules appropriately<br>
b) (Inclusionist) There should be at least one timezone id for
each ISO 3166-1 TLC<br>
...and as the "Hanoi" case would not be covered by (b) the even
extended inclusionist approach would rather be something like: <br>
c) (Inclusionist+) There should be at least one timezone id for
each "timezone" (in the sense of tzdb's consistent-since-1970
definition) for each ISO 3166-1 TLC</p>
I see the point of simply sticking to (a). However, not all all
users of tzdb will grasp this, and so there will always be
considerable "misuse" of timezone ids and discussions such as the
recent "Hanoi" thread.
<p>However it looks like there is no real solution to this, as
either choice has its subtleties. So sticking to the status quo
might be the best to do for now.</p>
<p>While I think I understand the perspective of people who are
arguing to focus on core tzdb maintenance, I'd however encourage
tzdb "users" (which I guess are also represented on this list) to
speak up regarding challenges they observe.</p>
<p>I think such discussion might be worthwhile 1) to raise
sensitivity for tzdb usage challenges in this community and 2) to
better understand pain points in the usage of time zones / time
zone identifiers in general.<br>
</p>
<p>For instance, has anybody ever seen an approach such as advised
in the note suggested by Paul [1], or are we actually all sticking
to just storing tzdb identifiers?</p>
<p>Thanks and best,<br>
Hans-Joerg</p>
[1] <br>
<pre class="moz-quote-pre" wrap="">Timezone boundaries are not part of the stable interface.
For example, even though the <samp>Asia/Bangkok</samp> timezone
currently includes Chang Mai, Hanoi, and Phnom Penh, this is not part
of the stable interface and the timezone can split at any time.
If a calendar application records a future event in some location other
than Bangkok by putting "<samp>Asia/Bangkok</samp>" in the event's record,
the application should be robust in the presence of timezone splits
between now and the future time.</pre>
<div class="moz-cite-prefix">On 20.02.19 13:37, Stephen Colebourne
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CACzrW9AoK4EeTbG1CqT49Y3KZ4NFKuo53FRi-Og2OV+4XN2XWw@mail.gmail.com">
<pre class="moz-quote-pre" wrap="">I strongly oppose this patch. At least one zone per ISO 3166-1 is a
vital part of this project and an entirely sensible rule. It is what
users expect the project to provide.
TZDB identifiers are used incredibly widely, and are seen on many
public-facing systems. I understand that is not seen as desirable by
some here, but it is the truth. When a country splits, it is usually
for painful reasons. The idea that the half of the country should be
forced to use the old identifier simply isn't tenable.
Stephen
On Tue, 19 Feb 2019 at 23:17, Paul Eggert <a class="moz-txt-link-rfc2396E" href="mailto:eggert@cs.ucla.edu"><eggert@cs.ucla.edu></a> wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">
On 2/19/19 2:31 PM, Tim Parenti wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">So, since it's pretty clear that the "There should typically be at
least one name for each ISO 3166-1 officially assigned two-letter code
for an inhabited country or territory" guideline has been, if not
abandoned entirely, at least significantly de-prioritized, perhaps
theory.html needs an update indicating that, yes, this /used/ to be
considered more important, but is not any longer (perhaps going a bit
into the rationale), and that we don't intend to create new zones
anymore if that's the only justification.
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
Sounds good to me; proposed patch attached.
</pre>
</blockquote>
</blockquote>
<br>
<pre class="">--
audriga GmbH
Durlacher Allee 47
76131 Karlsruhe, Germany
Tel: +49 (0) 721 17029 316
Fax: +49 (0) 721 17029 3179
<a class="m_-745030944823917949m_-7737262847214818316moz-txt-link-abbreviated" href="http://www.twitter.com/audriga" rel="noreferrer" target="_blank">www.twitter.com/audriga</a>
<a class="m_-745030944823917949m_-7737262847214818316moz-txt-link-abbreviated" href="http://www.audriga.com/" rel="noreferrer" target="_blank">www.audriga.com</a>
Handelsregister: Amtsgericht Mannheim - HRB 713034
Sitz der Gesellschaft: Karlsruhe
Geschäftsführer: Dr. Frank Dengler, Dr. Hans-Jörg Happel
USt-ID: DE 279724142</pre>
</body>
</html>