On Thu 2015-02-05T18:51:20 -0500, Brooks Harris hath writ: > Many aspects of "local time" or "civil time" are left to "common > practice" which is not good enough to expect uniform inter-operable > implementations.
> doesn't address the elephant in the > room - local time. As a horror story example from today, see the IANA tz mail list discussion trying to decipher the various announcments (official and un) about how Quintana Roo in Mexico will be setting its clocks in April. http://mm.icann.org/pipermail/tz/2015-February/022005.html It is all too common to find situations where it is difficult to ascertain who has authority, over what geographic region, and what exactly they are trying to say. Often the change only becomes clear scant days in advance. That is not enough time for the tz community to publish the change, for operating system vendors to incorporate the change, and for users of computers and cell phones to apply the patch. By comparison, leap second announcements are crystal clear. -- Steve Allen <[email protected]> WGS-84 (GPS) UCO/Lick Observatory--ISB Natural Sciences II, Room 165 Lat +36.99855 1156 High Street Voice: +1 831 459 3046 Lng -122.06015 Santa Cruz, CA 95064 http://www.ucolick.org/~sla/ Hgt +250 m _______________________________________________ LEAPSECS mailing list [email protected] https://pairlist6.pair.net/mailman/listinfo/leapsecs
