This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
From http://www.w3.org/TR/xpath-functions-30/#func-normalize-unicode: "Conforming implementations must support normalization form "NFC" and may support normalization forms "NFD", "NFKC", "NFKD", and "FULLY-NORMALIZED". They may also support other normalization forms with ·implementation-defined· semantics." Yet test-cases 'cbcl-fn-normalize-unicode-001' and 'cbcl-fn-normalize-unicode-006' from 'fn-normalize-unicode' test-set do have an alternate result for the case where an implementation does not support "FULLY-NORMALIZED" normalization. http://www.w3.org/TR/xpath-functions-30/#ERRFOCH0003 error should be added as an alternate expected result.
The mentioned test-cases actually have a dependency on "FULLY-NORMALIZED" normalization form.