- From: <bugzilla@wiggum.w3.org>
- Date: Mon, 12 Sep 2005 15:10:37 +0000
- To: www-xml-schema-comments@w3.org
- Cc:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=2135
Summary: R-144: Adding durations to dateTime
Product: XML Schema
Version: 1.0
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
Component: XSD Part 2: Datatypes
AssignedTo: cmsmcq@w3.org
ReportedBy: sandygao@ca.ibm.com
QAContact: www-xml-schema-comments@w3.org
Section E.1 contains the sentence:
"If a field in S is not specified, it is treated in the calculation as if it
were the minimum allowed value in that field, however, after the calculation is
concluded, the corresponding field in E is removed (set to unspecified)."
I think this sentence is in error and should be deleted.
The ordering relation for eg gYear specifies: "the order relation on gYear
values is the order relation on their starting instants". In this case as in
others, we only need to compare fully-specified dateTime instants.
The value space of gYear must be considered as containing both the year number
and the time zone (if any). To compare two values in the gYear value space, you
convert them to values in the dateTime value space (by using their starting
instants). Then you compare those two dateTime values using the algorithm in
3.2.7.3.
That sentence in section E.1 only makes sense if you take the view that the
value space of the partially specified dateTimes (like gYear, gMonth) does
*not* include time zones; in this case, you would need to normalize out the
time-zone before converting to a time-instant for comparison, and so would be
applying addition to a partially-specified date time. But this leads to
nonsense results, as Kawaguchi-san pointed out:
http://lists.w3.org/Archives/Public/www-xml-schema-comments/2001JanMar/0065.html
See:
http://lists.w3.org/Archives/Public/www-xml-schema-comments/2002AprJun/0046.html
Received on Monday, 12 September 2005 15:10:43 UTC