[LEAPSECS] A new use for Pre-1972 UTC
dot at dotat.at
Tue Feb 17 15:23:11 EST 2009
On Tue, 17 Feb 2009, Gerard Ashton wrote:
> Concatenate the "epoch" time at the time this ID value is being
> generated ; the "epoch" time is the number of seconds elapsed since
> 00:00:00 Coordinated Universal Time (UTC) January 01,
> 1970 (not counting leap seconds)
> 2. It has all the problems of what UTC means before 1972 that have been
> discussed in this mailing list, as well as what kind of seconds are
You can avoid that by specifying that the timescale can be any variant of
UT (UT1 or UTC or POSIX time, etc.) and is accurate to no better than a
A better solution than a seconds count would be to use an ISO 8601 string.
> a. Rigorously defined epoch, rigorous definition of whether SI or UT1 second
> is used.
Don't bother worrying about what kind of seconds you have, because no
commodity computing environments do.
> c. Contains a minimal number of non-alphanumeric characters to facilitate
Punctuation is optional in ISO 8601.
> d. The same time will be represented identically,
> character-for-character, in all implementations.
Use ISO 8601 zulu time. You probably need to specify a strict profile, in
the manner of RFC 3339.
f.anthony.n.finch <dot at dotat.at> http://dotat.at/
GERMAN BIGHT HUMBER: SOUTHWEST 5 TO 7. MODERATE OR ROUGH. SQUALLY SHOWERS.
MODERATE OR GOOD.
More information about the LEAPSECS