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 22418 - [QT3TS] format-date-en153, 154
Summary: [QT3TS] format-date-en153, 154
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XQuery 3 & XPath 3 Test Suite (show other bugs)
Version: Candidate Recommendation
Hardware: PC Windows NT
: 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:
Blocks:
 
Reported: 2013-06-20 14:12 UTC by Tim Mills
Modified: 2013-06-21 12:11 UTC (History)
1 user (show)

See Also:


Attachments

Description Tim Mills 2013-06-20 14:12:06 UTC
F&O3 stays of the $calendar argument:

"If the expanded QName is in a namespace then it identifies the calendar in an ·implementation-defined· way."

Tests format-date-en153 and 154 are testing implementation defined behaviour.
Comment 1 O'Neil Delpratt 2013-06-21 11:54:37 UTC
Yes you are right. I have applied a fix to the test cases in question. The fix was to change the assertion to assert-type= xs:string
Comment 2 Michael Kay 2013-06-21 12:08:22 UTC
Just an observation on this.

The spec says that the effect of a calendar in a namespace is implementation-defined, but it also says that the implementation must not raise an error unless the calendar name is invalid against the spec. So the only thing we can safely assert is that the result of the query must be a string (not an error). The revised tests reflect this decision.
Comment 3 Tim Mills 2013-06-21 12:11:51 UTC
Thanks.