[tz] EU Public Consultation on summertime arrangements
eggert at cs.ucla.edu
Tue Jul 10 22:31:36 UTC 2018
I tried to adjust the draft according to recent comments, as follows:
* Mention EEA and EFTA and Shengen, with the proposed terminology change, the
point being to be as inclusive as possible.
* Suggest that EU specify time zone names in the EU languages, not just English.
Mention CLDR as something that could use this.
* Change "many people" to "many English-language systems" would likely say
"Eastern European Time (EET)" for French time. Mention CLDR as one such.
Please see attached.
-------------- next part --------------
I am commenting as coordinator of the Time Zone Database (TZDB) hosted by the Internet Assigned Numbers Authority. This database is used by most of the world’s cell phones and many of its computers to track time zones and summertime arrangements. The comments below have been circulated on the TZDB mailing list and attempt to reflect consensus there.
Although the simplest thing for computing applications would to keep the EU rules unchanged, it would not be much of a problem to accommodate the abolition of twice-yearly clock changes in the EU, as has already been done in Russia and other countries. However, if such a change is done, the following technical points should be considered.
1. If timekeeping rules are changed, there should be at least a year’s notice before the changes take effect. Otherwise there is a good chance that some computer-based clocks will operate incorrectly after the change, due to delays in propagating updates to software and data. The shorter the notice, the more likely clock problems will arise. For more about this, please see “Changes to the tz database” and “On the Timing of Time Zone Changes”.
2. If the EU rules are changed, the EU should record in a public document its member states’ related changes to civil time, so that interested parties can easily track European timekeeping changes. For best results, the document should also keep track of changes to civil time in EEA/EFTA countries, candidate countries, potential candidates, the Schengen area, and other countries not in the EU that decide to make a related change. This document would be purely informative, with no authority behind it.
3. If the EU abolishes twice-yearly clock changes, the resulting time zones should be considered standard time, not permanent summertime, to avoid conflicts with existing computer standards in widespread use. The notion of permanent summertime is not supported by the POSIX.1-2017 standard, which covers most of the computing servers in the European Union.
4. If the EU abolishes twice-yearly clock changes, time zone names should be specified in the EU languages to help avoid confusion in applications like the Unicode Common Locale Data Repository, which is related to TZDB and which records time zone abbreviations and names in many languages. For example, if France decides to stay on UTC +02 all year, many English-language systems would likely call France’s new time zone “Eastern European Time (EET)”, due to the long association between EET and UTC +02. The EU should suggest this terminology (or some other terminology, if it prefers) to help interested parties discuss and understand the new timekeeping clearly.
 Time Zone Database, Internet Assigned Numbers Authority. 2018-05-01. <https://www.iana.org/time-zones>
 Changes to the tz database. 2018-05-01. <https://data.iana.org/time-zones/tz-link.html#changes>
 Johnson M. On the Timing of Time Zone Changes. 2016-04-23. <https://codeofmatt.com/2016/04/23/on-the-timing-of-time-zone-changes/>
 The Open Group Base Specifications Issue 7, 2018 edition, IEEE Std 1003.1-2017 (Revision of IEEE Std 1003.1-2008). See the variable “TZ” in section 8.3, “Other Environment Variables” <http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap08.html#tag_08_03>.
 By-Type Chart: Timezones:Europe. CLDR version 33. Unicode Consortium. 2018-03-09. <https://www.unicode.org/cldr/charts/33/by_type/timezones.europe.html>.
More information about the tz