This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
The function currently maps '24:00:00' to a value whose hour coordinate is 24, which is currently illegal. If 24:00:00 (the time value) intended to always map to a value whose hour coordinate is zero, then the fix is to normalize (via ·normalizeSecond·, or at least ·normalizeMinute·--there is no "·normalizeHour·") before emitting the value. See bug 2497
On 30 Mar the WG decided to insert "normalizeSecond" with appropriate arguments as the first line of the Algorithm of newDateTime. It also quietly fixed a typo by changing 'Year' to 'Yr'.
The change proposed above was approved by the WG on 30 March 2007 at its face to face meeting in Cambridge. It is now reflected in the status quo version of the Datatypes spec. Accordingly, I am setting the disposition of this issue to RESOLVED / FIXED. If the originator of the issue would examine the change and let us know whether it satisfactorily resolves the problem or not, we'd be grateful. To signal that the resolution is acceptable, change the status of the issue to CLOSED. Otherwise, to signal that it's NOT acceptable, change the status to REOPENED (and tell us what's wrong). If we don't hear from you in the next three weeks, we'll assume that silence betokens consent, and close the issue ourselves.