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 2357 - XQueryX: op-gYearMonth-equal-2 results are wrong
Summary: XQueryX: op-gYearMonth-equal-2 results are wrong
Status: CLOSED FIXED
Alias: None
Product: XML Query Test Suite
Classification: Unclassified
Component: XML Query Test Suite (show other bugs)
Version: 0.8.6
Hardware: PC Windows XP
: P2 normal
Target Milestone: ---
Assignee: Ravindranath (Ravi) Chennoju
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-18 15:43 UTC by Michael Kay
Modified: 2007-12-19 23:18 UTC (History)
2 users (show)

See Also:

Attachments

Description Michael Kay 2005-10-18 15:43:47 UTC 
Test op-gYearMonth-equal-2 is taken from the f+O spec section 10.4.17.1.

The spec correctly gives the result as "false" but the test suite gives the
expected results as "true".

Michael Kay
Comment 1 Michael Kay 2005-10-18 16:13:46 UTC 
The same problem affects:

op-gMonth-equal-2
Comment 2 Michael Kay 2005-10-18 16:16:31 UTC 
This also affects

op-gDay-equal-2
Comment 3 Andrew Eisenberg 2005-10-19 17:19:59 UTC 
Actual test case is op-gYearMonth-equalNew-1.

The spec gives the result of false because the implicit timezone is -05:00. I
believe that we are returning true because we assume timezone of Z.
Comment 4 Carmelo Montanez 2005-10-28 14:32:22 UTC 
Fixed tests.  USed an explicit timezone of "-05:00" as in the example
in the F& O specs.  Submitted new tests and results.  Please close
the bug if you agree with resolution.

Thanks,
Carmelo
Comment 5 Jerome Simeon 2006-01-11 15:17:50 UTC 
op-gYearMonth-equal-2 and op-gMonth-equal-2
still seem to use the implicit time zone in version 0.8.4 of
the test suite.
- Jerome
Comment 6 Carmelo Montanez 2006-01-11 16:10:04 UTC 
Jerome:

All tests should use an explicit timezone now.  Please close bug when able to 
verify.

Thanks,
Carmelo
Comment 7 Alberto Massari 2006-02-23 10:30:23 UTC 
In the 0.8.6 version of the suite op-gYearMonth-equalNew-2 doesn't rely any more
on the current timezone, but it still expects a "true" result, while the F&O
specs mandate a "false" one
Comment 8 Carmelo Montanez 2006-03-06 16:36:40 UTC 
Alberto et all:

Sorry I overlook that small detail.  Resubmitted test results.  Please close the bug if in agreement and able to verify.

Thanks,
Carmelo
Comment 9 Jerome Simeon 2006-09-30 01:51:16 UTC 
op-gYear-equal-2
should also return true
I think this one has been overlooked.
- Jerome
Comment 10 Carmelo Montanez 2006-10-04 13:27:45 UTC 
Jerome:

Thanks for the comment.  I updated the results to reflect a "true" value.

Thanks,
Carmelo
Comment 11 Michael Kay 2007-01-26 00:24:12 UTC 
It seems the XQueryX version of the test op-gYear-equal-2 is now out of line with the XQuery version.
Comment 12 Andrew Eisenberg 2007-12-19 23:07:06 UTC 
I believe that the XQuery and XQueryX versions of this test case are now in sync. This was probably fixed quite a while ago, and certainly was fixed when we added the XQueryX queries to our CVS repository.

http://dev.w3.org/2006/xquery-test-suite/TestSuiteStagingArea/Queries/XQuery/Expressions/Operators/CompExpr/ValComp/DurationDateTimeOp/gYearEQ/op-gYear-equal-2.xq
http://dev.w3.org/2006/xquery-test-suite/TestSuiteStagingArea/Queries/XQueryX/Expressions/Operators/CompExpr/ValComp/DurationDateTimeOp/gYearEQ/op-gYear-equal-2.xqx

Please close this bug if you agree with this resolution.
Comment 13 Michael Kay 2007-12-19 23:18:47 UTC 
I'll take it on trust. Closing.