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 6341 - [FO] Specification of op:dateTime-equal, etc
Summary: [FO] Specification of op:dateTime-equal, etc
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: Functions and Operators 3.0 (show other bugs)
Version: Recommendation
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Michael Kay
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-02 17:50 UTC by Michael Kay
Modified: 2010-02-09 10:32 UTC (History)
1 user (show)

See Also:


Attachments

Description Michael Kay 2009-01-02 17:50:22 UTC
The "Summary" of op:dateTime-equal states:

<quote>
Returns true if and only if the value of $arg1 is equal to the value of $arg2 according to the algorithm defined in section 3.2.7.4 of [XML Schema Part 2: Datatypes Second Edition] "Order relation on dateTime" for xs:dateTime values with timezones.
</quote>

There is no mention here, or anywhere else except the examples, of the role of the implicit timezone. The information in the summary seems at best misleading and at worst plain incorrect: the only way it can be made consistent with the examples is by assuming that the implicit timezone is treated implicitly as part of the values used as input to the algorithm from the XML Schema specification.

The same problem applies to all the other comparison functions for dates/times.

The introductory paragraphs to section 10.4 describe the general approach to comparing dates and times by filling in missing components from the 7-field model; but the specific functions do not refer to that material directly (instead it refers directly to the schema specification). Indeed the introductory material only says that the implicit timezone is used "in some cases", but it does not say which.
Comment 1 Michael Kay 2009-01-27 16:46:31 UTC
Mixed views on this one; but editor encouraged to see what he can do without excess duplication of text across the function. A "See also" would do no harm.
Comment 2 Michael Kay 2009-02-24 18:27:40 UTC
Editor encouraged to add a "See also" section where appropriate.
Comment 3 Michael Kay 2009-10-13 10:27:25 UTC
Rather than adding a "see also", I decided to add the following text to the relevant function specifications:

<p>If either $arg1 or $arg2 has no timezone component, the effective value of the argument is obtained by substituting the implicit timezone from the dynamic evaluation context.</p>