- From: <bugzilla@jessica.w3.org>
- Date: Tue, 05 Jul 2011 17:56:05 +0000
- To: public-qt-comments@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13141 --- Comment #1 from Michael Kay <mike@saxonica.com> 2011-07-05 17:56:05 UTC --- I don't believe that this discrepancy has any observable effects. I suspect that historically, XSD fills in the template with components from the date 1972-12-31T00:00:00 because that year was a leap year and that day contained leap seconds; this date could therefore be combined with any xs:time value to produce a legal xs:dateTime. Now that leap seconds are no longer supported in XSD, the rationale for this choice has disappeared. The only reason for using this machinery in XPath functions and operators is so that we can define xs:gYear operations in terms of xs:date operations. For that purpose, I think any month and day (other than 29 Feb) would work equally well. The reason for choosing 1 January is that the spec says that gYear values are compared by comparing their starting instants, and it's therefore logical to use the first day of the year in the actual algorithm. The same approach would still work if we chose to support ordering of gYear values. -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Tuesday, 5 July 2011 17:56:07 UTC