Re: Action A-659-05 Completed

>> * Support for UCA Collations. We chose to make support for UCA collations mandatory in the interests of interoperability and I18N support, but implementation is technically challenging, and typically depends on third party libraries. We could make the feature optional, but we don't think this would be in the interests of the user community; rather we would prefer to accept that implementation of these features may lag a little behind.
> And this point is actually what has stopped me from implementing XQuery 3.1 so far.
> 

FNO allows you to use fallback behavior so you don't have to implement UCA.

https://www.w3.org/XML/Group/qtspecs/specifications/xpath-functions-31/html/ <https://www.w3.org/XML/Group/qtspecs/specifications/xpath-functions-31/html/>
"If the fallback parameter is present with the value no, then the implementation must either use a collation that conforms with the rules in the Unicode specifications for the requested tailoring, or fail with a static or dynamic error indicating that it does not provide the collation (the error code should be the same as if the collation URI were not recognized). If the fallback parameter is omitted or takes the value yes, and if the collation URI is well-formed according to the rules in this section, then the implementation must accept the collation URI, and should use the available collation that most closely reflects the user's intentions. For example, if the collation URI requested is http://www.w3.org/2013/collation/UCA?lang=se;fallback=yes and the implementation does not include a fully conformant version of the UCA tailored for Swedish, then it may choose to use a Swedish collation that is known to differ from the UCA definition, or one whose conformance has not been established. It might even, as a last resort, fall back to using codepoint collation."

XQST tests that depend on not using fallback and not raising an error are tagged such that you can avoid running them. 

Josh