This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 10658 - Lexical mapping for midnight is missing
Summary: Lexical mapping for midnight is missing
Status: CLOSED FIXED
Alias: None
Product: XML Schema
Classification: Unclassified
Component: Datatypes: XSD Part 2 (show other bugs)
Version: 1.1 only
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: David Ezell
QA Contact: XML Schema comments list
URL:
Whiteboard:
Keywords: decided
Depends on:
Blocks:
 
Reported: 2010-09-20 13:03 UTC by Michael Kay
Modified: 2010-11-25 08:01 UTC (History)
2 users (show)

See Also:


Attachments

Description Michael Kay 2010-09-20 13:03:21 UTC
In part 2, Section 3.3.9.2 (xs:time) asserts: "The ·lexical mapping· maps '00:00:00' and '24:00:00' to the same value, namely midnight (·hour· = 0 , ·minute· = 0 , ·second· = 0)."

However, the lexical mapping given in function timeLexicalMap() does not appear to do this; it gives no mapping to a value when endOfDayFrag is used.

Similarly for xs:dateTime.
Comment 1 Dave Peterson 2010-09-20 17:50:15 UTC
(In reply to comment #0)

> However, the lexical mapping given in function timeLexicalMap() does not appear
> to do this; it gives no mapping to a value when endOfDayFrag is used.
> 
> Similarly for xs:dateTime.

It appears I screwed up--amazing no one caught it before.  Will try to have a fix by next week's WG phone meeting.  :-(
Comment 2 David Ezell 2010-10-01 14:21:11 UTC
At the telcon on 2010-09-24 the WG decided:
1) to adopt an ammendment proposed in this email
http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2010Sep/0007.html,
i.e.  "D+1), 0, 0, 0," to "D), 24, 0, 0,"

2) to recast the notes in Appendices E.3.5 and D.2.2, since special handling for EOD frag no longer forces values to zero (MSM).  

3) remove the parentheses from these same notes and mark them in the usual way for notes.

4) adopt the following rewording of the text:
LEX necessarily includes substrings that are instances of yearFrag,
monthFrag, and dayFrags (below referred to as Y, MO, and D
respectively); it also contains either instances of hourFrag,
minuteFrag, and secondFrag (Y, MI, and S), or else an instance
of endOfDayFrag; finally, it may optionally contain an instance of
timezoneFrag (T).
Comment 3 C. M. Sperberg-McQueen 2010-11-25 00:41:24 UTC
The changes described in comment 2 have been made in the (member-accessible) 
status-quo version of the document; to reflect that fact, I'm marking this issue as 
resolved.

[To the originator of the comment:]  If you are content with the disposition of the 
comment, you can as originator close the issue to signal your contentment.  If 
for some reason you are unhappy, please re-open the issue and explain what's 
wrong.  If we don't hear from you in the next two weeks or so, we'll assume that 
you are happy with the outcome.