News for hackers. Stuff that matters.
Re:Maya – Python Datetimes for Humans by masklinn on Monday December 19, 2016 @04:59AM (#13210498)
> You also mix up the various timescales:

No, but I think we're interpreting the word "skipping" differently which leads to confusion. To me, in TAI, a "leap second" is nothing special and included in the normal time stream, in UTC the leap second is removed from the normal time stream and tacked on as a special case on some specific days, hence skipping it, hence UTC running late compared to TAI: UTC has "removed" 36 seconds from the timestream compared to UTC.

> Unix/POSIX time might not skip leap seconds

UNIX/POSIX can only ignore leap seconds, how it does so doesn't matter, because it's defined as constant-length days, the timestamp is 86400days since epoch + seconds since midnight. The day after a leap second, that leap second has "disappeared" from the timestamp sequence.

> However, Unix/POSIX time is not UTC.

Unix time is specifically defined as UTC (at least after January 1st 1972 since that's when UTC was defined, pre-72 it's ambiguous), though not true since it can't represent* leap seconds. Outside of the extent of leap seconds, UNIX time tracks UTC exactly.

> as leap seconds are an inherent property of UTC.

They're an inherent property of UTC in that it removes them from normal time treatment.

> TAI does not include leap seconds[1]:

It includes them in the sense that it treats them as perfectly normal seconds without anything special about them.

> With the above, it should be obvious that this is a property of UTC, not TAI.

The paragraph you're quoting here (and my entire comment really) is talking about how these systems map to human time aka year/month/day/hour/minutes/seconds. Leap seconds were introduced specifically for that purpose, and UTC (and unix timestamps) are thus trivially mappable by definition.

Because it does not, TAI can't be mapped to human time without leap seconds definition AKA May 7th, 2078 at 17:54:33 is known in UTC, but not known in TAI, because we don't know how many leap seconds will be introduced in the next 61 years and that's necessary to map TAI to and from human time.

There are no comments on this comment yet.