Re: [LEAPSECS] Leap second relationship to ISO 8601

2014-08-27 Thread Tony Finch
Brooks Harris bro...@edlmax.com wrote: Its important to note 8601 is silent on how Daylight Savings Time is handled and provides no recommendation of how it might be indicated or represented. ISO 8601 does not represent daylight saving nor time zones. Looking closely you'll find there is no

Re: [LEAPSECS] Leap second relationship to ISO 8601

2014-08-27 Thread Poul-Henning Kamp
In message alpine.lsu.2.00.1408271011340.23...@hermes-1.csi.cam.ac.uk, Tony F inch writes: Brooks Harris bro...@edlmax.com wrote: Its important to note 8601 is silent on how Daylight Savings Time is handled and provides no recommendation of how it might be indicated or represented.

Re: [LEAPSECS] Leap second relationship to ISO 8601

2014-08-27 Thread Brooks Harris
Hi Tony, On 2014-08-27 05:22 AM, Tony Finch wrote: Brooks Harris bro...@edlmax.com wrote: Its important to note 8601 is silent on how Daylight Savings Time is handled and provides no recommendation of how it might be indicated or represented. ISO 8601 does not represent daylight saving nor

Re: [LEAPSECS] Leap second relationship to ISO 8601

2014-08-27 Thread Poul-Henning Kamp
In message alpine.lsu.2.00.1408271650570.23...@hermes-1.csi.cam.ac.uk, Tony F inch writes: Brooks Harris bro...@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?

Re: [LEAPSECS] Leap second relationship to ISO 8601

2014-08-27 Thread Brooks Harris
Hi Tony, On 2014-08-27 12:08 PM, Tony Finch wrote: Brooks Harrisbro...@edlmax.com wrote: On 2014-08-27 05:22 AM, Tony Finch wrote: ISO 8601 does not represent daylight saving nor time zones. It can represent both, but incompletely, or ambiguously. The time element called zone designator