Re: [Tzdist] example json snips for systems that count leap seconds

[Steve Allen <[e-mail]>]

On Tue 2015-01-13T20:43:55 +0100, Martin Burnicki hath writ:
> However, if it's made clear that the
> times are TAI, not UTC (is 'Z' correct, then?) this should be no
> problem. The most important thing is that list of leap second events
> can be extracted properly.

Martin is right, the 'Z' is an abuse of the notation.  The
interpretation that UTC might be counted without counting the leap
seconds is a different kind of abuse, but thinking of things in that
way is continuing a long-term non-constructive temporal flame war.
I am aiming to follow the lead of the "right" TimeZone database with
practical examples helping people to use tzdist in order to work
around deficiencies in the existing standards.

So as Martin cautioned, in the text (before the json examples that I
posted) it was necessary that I very clearly defined the assumptions
of each underlying system time scale including the way in which it
differs from various standards and the motivation for each difference.
With that documentation clearly explaining the appropriate context for
the use of each, the json examples that I posted should work with the
math of the code in existing calendar APIs.

--
Steve Allen                 <[e-mail]>                WGS-84 (GPS)
UCO/Lick Observatory--ISB   Natural Sciences II, Room 165    Lat  +36.99855
1156 High Street            Voice: [phone]           Lng -122.06015
Santa Cruz, CA 95064        http://www.ucolick.org/~sla/     Hgt +250 m