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 14873 - [QT3TS] format-integer-020
Summary: [QT3TS] format-integer-020
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XQuery 3 & XPath 3 Test Suite (show other bugs)
Version: Member-only Editors Drafts
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: 17099
Blocks:
  Show dependency treegraph
 
Reported: 2011-11-18 10:32 UTC by Tim Mills
Modified: 2012-09-25 08:50 UTC (History)
3 users (show)

See Also:


Attachments

Description Tim Mills 2011-11-18 10:32:11 UTC
This test expects an XSLT error code, but doesn't state a dependency on XSLT.

A variant of this test is required for XP30+/XQ30+.
Comment 1 Tim Mills 2011-11-18 12:43:57 UTC
A similar problem afflicts the following tests.

format-integer-023 to 028
format-integer-034
format-integer-037 to 040
format-integer-054
format-integer-056
format-integer-057
Comment 2 Tim Mills 2011-11-18 14:26:47 UTC
A similar problem afflicts the following tests.

format-date-801err to 808err

format-time-809err to 817err

format-time-809err to 817err

format-dateTime-801err
Comment 3 Michael Kay 2011-11-23 21:59:00 UTC
These tests should work with XPath 3.0 as well as XSLT. In the current draft of F+O, the original XSLT error codes have been replaced by FO error codes; these new error codes have yet to be reflected in the test cases.
Comment 4 Tim Mills 2011-11-24 16:11:43 UTC
But format-integer in

http://www.w3.org/XML/Group/qtspecs/specifications/xpath-functions-30/html/Overview.html#func-format-integer

doesn't raise any errors.

The text

"Any other format token indicates a numbering sequence in which that token represents the number 1 (one) (but see the note below). It is 
Comment 5 Michael Kay 2012-05-18 11:12:10 UTC
Marked as dependent on the resolution of spec bug 17099
Comment 6 O'Neil Delpratt 2012-08-08 12:50:06 UTC
Resolved. The error codes for the test cases in question have been changed.
Comment 7 Tim Mills 2012-09-25 08:50:45 UTC
Marking as CLOSED, but see Bug 19004.