This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
See description from Bug 2116. 1.1 needs to answer the question of whether "00:00:00" and "24:00:00" give rise to different values.
After discussion the F&O adopted the following wording "For xs:time, "00:00:00" and "24:00:00" are alternate lexical forms for the same value. For xs:dateTime, a time component "24:00:00" translates to "00:00:00" of the following day." As pointed out in bug 2116, the problem is in the order relation on these time values. If 24:00:00 is, indeed, 00:00:00 of the following day then it is later than 00:00:00.
(In reply to comment #1) > After discussion the F&O adopted the following wording "For xs:time, "00:00:00" > and "24:00:00" are alternate lexical forms for the same value. For xs:dateTime, > a time component "24:00:00" translates to "00:00:00" of the following day." > > As pointed out in bug 2116, the problem is in the order relation on these time > values. If 24:00:00 is, indeed, 00:00:00 of the following day then it is later > than 00:00:00. My recollection is that the WG discussed this and decided it wasn't worth making a special case for time. However, the best I can find is that Ashok and I were given an action by the WG 18 Nov 05 to "investigate, bring back proposed fix(es) or reason why none required [recorded in http://www.w3.org/2005/11/18-xmlschema-minutes.html#action01]". Ashok responded with Comment #1 herein, stating the F&O position. OTOH, In researching this I find that there is an error in the function ·newDateTime· in that it doesn't normailze the hour, mapping a '24' hourFrag to the hour coordinate value 24, which is illegal. I am therefore entering a new bug (3851) to insure this is fixed.
On 30 Mar the WG asserted its intent that 00:00:00 and 24:00:00 be identical, and corrected the bug in 3851 to insure that this was the case. They also chose to add a note to the end of 3.3.9.4 saying "NOTE: The lexical mapping maps '00:00:00' and '24:00:00' to the same value, namely midnight (hour = 0, minute = 0, second = 0)." ['hour', 'minute', and 'second' marked up to indicate they are the coordinates of a time value so named.] [This bug should now carry the keyword 'decided'. Bugzilla will not permit me to make that change at this time.]
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.