[LEAPSECS] Leap second relationship to ISO 8601

Poul-Henning Kamp phk at phk.freebsd.dk
Wed Aug 27 13:38:12 EDT 2014


--------
In message <alpine.LSU.2.00.1408271650570.23119 at hermes-1.csi.cam.ac.uk>, Tony F
inch writes:
>Brooks Harris <brooks at edlmax.com> wrote:

>> > > For example, a date and time in New York City might be represented
>> > > as 2014-07-04T00:00:00-05:00 [...]
>> >
>> > The former is incorrect.
>>
>> Incorrect where?
>
>The UTC offset in New York at that time was not -05:00 so that cannot be a
>time in New York.

You're missing the quiet genius of 8601 here:

Who said the date and time of the event which happened in New York
were represented on local timescale there at the time ?

It would have been if you had written some ...EST or ...DST, and
that would take you into the murky swamp of the olsen timezone
database.

By explicitly stating the UTC offset numerically, 8601 decouples
it from any cultural basis it might have had and becomes a standalone
representation of a moment in time.

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk at FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.


More information about the LEAPSECS mailing list