This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
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>
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>