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 22284 - test-cases not considering that "FULLY-NORMALIZED" is not mandatory.
Summary: test-cases not considering that "FULLY-NORMALIZED" is not mandatory.
Status: RESOLVED INVALID
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XQuery 3 & XPath 3 Test Suite (show other bugs)
Version: Working drafts
Hardware: PC Linux
: 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-05 14:05 UTC by Sorin Nasoi
Modified: 2013-06-05 14:22 UTC (History)
0 users

See Also:

Attachments

Description Sorin Nasoi 2013-06-05 14:05:24 UTC 
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.
Comment 1 Sorin Nasoi 2013-06-05 14:22:03 UTC 
The mentioned test-cases actually have a dependency on "FULLY-NORMALIZED" normalization form.