29573 2016-04-13 10:42:07 +0000 format-dateTime-en151, format-dateTime-en152, format-date-en151, format-date-en152 2016-04-26 20:32:49 +0000 1 1 1 Unclassified XPath / XQuery / XSLT XQuery 3 & XPath 3 Test Suite Candidate Recommendation PC Windows NT RESOLVED FIXED P2 normal --- 1 christian.gruen oneil mike public-qt-comments oldest_to_newest 125839 0 christian.gruen 2016-04-13 10:42:07 +0000 In 9.8.4.4. of the XQFO 3.1 spec, it is stated that "If the fallback representation uses a different calendar from that requested, the output string must identify the calendar actually used, for example by prefixing the string with [Calendar: X] (where X is the calendar actually used), localized as appropriate to the requested language." and "If the fallback representation uses a different language from that requested, the output string must identify the language actually used, for example by prefixing the string with [Language: Y] (where Y is the language actually used) localized in an implementation-dependent way." In the test suite, there are four tests which contain the proposed prefixes "[Calendar: ...]" and "[Language: ...]": <assert-string-value>[Language: en]March</assert-string-value> <assert-string-value>[Calendar: AD]03</assert-string-value> If the prefix representation is supposed to be examplary, it could make sense to replace the string assertions with something like: <not><assert-string-value>March</assert-string-value><not> <not><assert-string-value>03</assert-string-value></not> 126166 1 mike 2016-04-26 20:32:49 +0000 The WG agreed that the expected results needed to be more liberal. I have replaced the expected results with <all-of> <assert>matches($result, "en")</assert> <assert>matches($result, "March")</assert> </all-of> <all-of> <assert>matches($result, "AD")</assert> <assert>matches($result, "03")</assert> </all-of>