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 19579 - cbcl-subsequence-008, 010
Summary: cbcl-subsequence-008, 010
Status: RESOLVED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XQuery 3 & XPath 3 Test Suite (show other bugs)
Version: Working drafts
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: O'Neil Delpratt
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on: 21413
Blocks:
  Show dependency treegraph
 
Reported: 2012-10-17 15:37 UTC by O'Neil Delpratt
Modified: 2013-06-07 11:38 UTC (History)
0 users

See Also:


Attachments

Description O'Neil Delpratt 2012-10-17 15:37:13 UTC
The test-case cbcl-subsequence-010 (i.e: 'count(subsequence(1 to 3000000000, -2147483648, 2147483647))') goes beyond the limits of representation for a integer value in Java and therefore we are not able to produce the expected result in our implementation. Hence, we suggest that any-error be allowed as an additional expected result for us to pass this test.

In addition, for the test cbcl-subsequence-008 there is spurious error code (i.e. <error code="ANDY0001"/>) given as one of the expected results.
Comment 1 Tim Mills 2012-11-06 11:56:51 UTC
This is interesting.

In the XSLT 3.0 specification at:

https://www.w3.org/XML/Group/qtspecs/specifications/xslt-30/html/Overview.html#limits

lists 7 implementation defined limits.

1.  For the xs:decimal type, the maximum number of decimal digits (the totalDigits facet). This must be at least 18 digits. (Note, however, that support for the full value range of xs:unsignedLong requires 20 digits.)

2.  For the types xs:date, xs:time, xs:dateTime, xs:gYear, and xs:gYearMonth: the range of values of the year component, which must be at least +0001 to +9999; and the maximum number of fractional second digits, which must be at least 3.

3.  For the xs:duration type: the maximum absolute values of the years, months, days, hours, minutes, and seconds components.

4.  For the xs:yearMonthDuration type: the maximum absolute value, expressed as an integer number of months.

5.  For the xs:dayTimeDuration type: the maximum absolute value, expressed as a decimal number of seconds.

6.  For the types xs:string, xs:hexBinary, xs:base64Binary, xs:QName, xs:anyURI, xs:NOTATION, and types derived from them: the maximum length of the value.

7.  For sequences, the maximum number of items in a sequence.

Not all of these are represented in the XQuery 3.0 specifiaction in

https://www.w3.org/XML/Group/qtspecs/specifications/xquery-30/html/xquery-30.html#id-data-model-conformance

Of the above, 1 to 5 are represented in the F&O specification by error codes FOAR0002, FOCA0001, FOCA0003, FOCA0006, FODT0001 and FODT0002.

There aren't any codes for 6 or 7.  Perhaps there should be?

The code ANDY0001 is XmlPrime's error for "Argument out of implementation defined range."  Perhaps a code for this could be added to F&O 3.0 so that the condition can be handled uniformly across processors.
Comment 2 O'Neil Delpratt 2013-03-20 10:59:29 UTC
To add a new error code I think we would need a WG decision.
Comment 3 O'Neil Delpratt 2013-03-27 12:59:04 UTC
The WG decided add an error code for "implementation-defined limit exceeded". Therefore this bug depends on the resolution of bug #21413,
Comment 4 O'Neil Delpratt 2013-03-27 16:37:12 UTC
In addition to comment #3 the spurious error code described in comment #0 has been removed from the test case.
Comment 5 O'Neil Delpratt 2013-06-07 11:38:16 UTC
Test cases fixed by using the new error codes