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 3826 - Static typing of K-SeqOneOrMoreFunc-3
Summary: Static typing of K-SeqOneOrMoreFunc-3
Status: CLOSED FIXED
Alias: None
Product: XML Query Test Suite
Classification: Unclassified
Component: XML Query Test Suite (show other bugs)
Version: 1.0.1
Hardware: PC Windows XP
: P2 normal
Target Milestone: ---
Assignee: Frans Englich
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-10-13 13:41 UTC by Nick Jones
Modified: 2007-01-15 10:58 UTC (History)
0 users

See Also:

Attachments

Description Nick Jones 2006-10-13 13:41:25 UTC 
This test:

one-or-more("one") eq "one"

does not static type check as the types are

LHS: string+
RHS: anyAtomicType?

As has happened with similar cases, could "one" be set as the expected result
for the test harness to check, rather than doing such a test in the query.


(As a side note, is it preferable to submit lots of reports describing why each group of tests doesn't check. Or would a big list of tests which don't type check be prefered?)
Comment 1 Frans Englich 2006-10-13 13:48:16 UTC 
I think a significant factor is how much work it is for you to split the test cases into reports. I'd say:

Report K-* and K-2* tests in reports separately from tests that does not start with "K". Other than that feel free to do it pretty much at your convenience. For example, perhaps group tests that have the same problem in each report(probably leading to one big list of tests that use 'eq' to check the result).
Comment 2 Frans Englich 2007-01-12 18:52:34 UTC 
An attempted fix has been committed to CVS, and should be part of XQTS_current.zip. Feel free to verify that the fix is acceptable, and if so, change status to CLOSED. If the attempted fix is not acceptable, reopen this report.

If no opinion about this resolution is expressed within two weeks, it will be closed.

Along with the fix for this report, was committed fixes for other reports as well. Also, a significant amount of new tests were added to cover missing areas and changes in the specifications.