W3C home > Mailing lists > Public > whatwg@whatwg.org > October 2008

[whatwg] Time element, typographical error, and UTC

From: Gerard Ashton <ashtongj@comcast.net>
Date: Sat, 25 Oct 2008 19:52:59 -0400
Message-ID: <3120A52EDD7D489E9D4F9E428063871F@grendel>
The part of the spec at
in the " Vaguer moments in time" section contains a typographical
error. In this phrase:

"If second is not a number in the range 0 ? minute < 60, then the string is
invalid, abort these steps. "

the word "minute" should be replaced by "second".

Also, it is quite confusing to have times constantly being refered to as UTC
times, and yet find the following phrase in " Specific moments in

"If second is not a number in the range 0 ? second < 60, then fail. (The
 60 and 61 are not allowed: leap seconds cannot be represented by datetime
values.) "

Where the time element is described, at
the description of the second used is unclear. I infer from the description
that the value
of the time element is the number of UT milliseconds since 1970-01-01 00:00
The distinction being that UTC only applies to the initial epoch, 1970-01-01
00:00 UTC.
After the epoch, time is counted in universal time (UT), with no leap
seconds allowed
(that is, a seconds value of 60.500 violates the spec).

Am I on the right track? Should the spec spell this out, or provide a
to a location where it is spelled out?

Received on Saturday, 25 October 2008 16:52:59 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:06 UTC