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 1317 - Inconsistency in normalize-unicode() $normalizationForm 'FULLY-NORMALIZED'
Summary: Inconsistency in normalize-unicode() $normalizationForm 'FULLY-NORMALIZED'
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 minor
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-10 10:17 UTC by Jeni Tennison
Modified: 2007-02-25 23:38 UTC (History)
0 users

See Also:

Attachments

Description Jeni Tennison 2005-05-10 10:17:50 UTC 
The description of normalize-unicode() is inconsistent. In the bulleted list it
says:

   If the effective value of $normalizationForm is "FULLY_NORMALIZED"...

(Note underscore in FULLY_NORMALIZED.)

In the following paragraph it says:

   Conforming implementations ... ·may· support normalization forms ...   
   "FULLY-NORMALIZED"

(Note hyphen in FULLY-NORMALIZED.)

In the Serialization spec, the value of the normalization-form parameter can be
'fully-normalized', with a hyphen, so I think that for consistency a hyphen
should be used here as well.
Comment 1 Jim Melton 2007-02-25 23:38:45 UTC 
Closing bug because commenter has not objected to the resolution posted and more than two weeks have passed.