On Fri 2016-12-30T17:59:14 -0700, Warner Losh hath writ: > if you were to transition to a TAI world, then you'd not be able to > implement the latter for a TAI time of the UTC time at some > Y/M/D/H/M/S past the end of the next six month boundary, since it is > impossible to have that knowledge.
This is a well-known problem in the arena of calendaring applications when an event is to be attended by parties in many timezones. The calendaring applications must be able to recognize that the timezone rules for one or more of those attending can change (sometimes with much less notice than the 6 months for leap seconds) between the scheduling and the event. This requires that the event be stored with a home time zone (in addition to the time in that zone) in which its time is fixed, and that everyone else can be alerted if the local authorities announce that home time zone or their own time zone is being changed. -- Steve Allen <[email protected]> WGS-84 (GPS) UCO/Lick Observatory--ISB 260 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
