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 1421 - [FO] codepoint-equal needed?
Summary: [FO] codepoint-equal needed?
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: Functions and Operators 1.0 (show other bugs)
Version: Last Call drafts
Hardware: PC Windows XP
: P2 normal
Target Milestone: ---
Assignee: Ashok Malhotra
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-05-13 21:23 UTC by Michael Rys
Modified: 2005-09-29 11:09 UTC (History)
0 users

See Also:


Attachments

Description Michael Rys 2005-05-13 21:23:49 UTC
Since users can use compare() with the UCC collation to perform codepoint 
equality checks: Why is the codepoint-equal function needed?
Comment 1 Ashok Malhotra 2005-05-20 22:21:59 UTC
The QT WGs agreed on 5/19/2005 to add a note saying that this function was added
to allows anyURIs to be compared without having to specify the long URI for the
Unicode code point collation.

Ashok Malhotra