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 4764 - delete words appropriate for leap-seconds
Summary: delete words appropriate for leap-seconds
Status: CLOSED FIXED
Alias: None
Product: XML Schema
Classification: Unclassified
Component: Datatypes: XSD Part 2 (show other bugs)
Version: 1.1 only
Hardware: All All
: P4 minor
Target Milestone: ---
Assignee: C. M. Sperberg-McQueen
QA Contact: XML Schema comments list
URL:
Whiteboard: cluster: clarification
Keywords: resolved
Depends on:
Blocks:
 
Reported: 2007-06-26 14:14 UTC by Dave Peterson
Modified: 2008-03-01 00:59 UTC (History)
0 users

See Also:


Attachments

Description Dave Peterson 2007-06-26 14:14:03 UTC
Near the end of D.2.1 the spec asserts "1972-12-31T00:00:00 happens to permit both the maximum number of days and the maximum number of seconds."  The sentence should end after "days" since we the datatype longer accounts for leap-seconds.
Comment 1 C. M. Sperberg-McQueen 2008-02-27 02:30:28 UTC
The sentence mentioned should have been deleted as part of the 
change adopted when we specified that leap seconds are not supported.
Owing to an editorial error, it survived.  I propose to resolve this
issue by deleting the sentence "1972-12-31T00:00:00 happens to permit 
both the maximum number of days and the maximum number of seconds."
Comment 2 C. M. Sperberg-McQueen 2008-02-27 15:26:16 UTC
A wording proposal intended to resolve this issue among others was sent to
the WG 27 February 2008:
http://www.w3.org/XML/Group/2004/06/xmlschema-2/datatypes.omni200802.xml
(member-only link).
Comment 3 C. M. Sperberg-McQueen 2008-02-29 19:40:20 UTC
At its telcon today, the XML Schema WG adopted the wording proposal at 
http://www.w3.org/XML/Group/2004/06/xmlschema-2/datatypes.omni200802.xml
(member-only link), and believes this issue now to be resolved.  

Since the originator is a WG member and was present on the call, it seems
likely that you agree that the issue is successfully resolved.  Still, 
please so indicate by changing the status of the bug report to CLOSED.
Or reopen it if you discover a snag.  Silence will be taken to mean consent.