Legacy Issue Number: 16680
Source: Object Management Group ( Andrew Watson)
(This comment came from the Architecture Board's review of the final submission.)
This comment on page 16 [now Annex A.3 jarred somewhat:
"These variations are accounted for by incorporating intercalary leap days and leap seconds into some calendar and timekeeping schemes. This specification chooses to support leap days, but not leap seconds, because leap days are significant to business while leap seconds are insignificant."
It seems a bit arrogant to assert that "leap seconds are insignificant to
business". If (for instance) your company's Telephone PABX were to crash at
midnight on New Year's Eve because its software couldn't cope with
leap-seconds, I suggest that would be "significant to business".
Reported: DTV 1.0b1 — Wed, 16 Nov 2011 05:00 GMT
Disposition: Resolved — DTV 1.0
Currently, the Date-Time Vocabulary describes the Gregorian Calendar in terms of the UTC time scale. To support leap seconds, add definitions of the TAI time scale and leap seconds, and add text saying that leap seconds add discontinuities in the UTC time scale. These discontinuities affect use cases that are sensitive to leap seconds.
Per ISO 80000-3, the definition of the 'day' time unit remains as a fixed 86 400 seconds.
Updated: Sun, 8 Mar 2015 17:51 GMT
DTV_ — Date-Time Issue - leap seconds
- Key: DTV_-16
- OMG Task Force: Date-Time (DTV) 1.0 FTF 2