[Bug 1317] New: Inconsistency in normalize-unicode() $normalizationForm 'FULLY-NORMALIZED'

• From: <bugzilla@wiggum.w3.org>
• Date: Tue, 10 May 2005 10:17:50 +0000
• To: public-qt-comments@w3.org
• Cc:
• Message-Id: <E1DVRoE-0007Kt-I4@wiggum.w3.org>

http://www.w3.org/Bugs/Public/show_bug.cgi?id=1317

           Summary: Inconsistency in normalize-unicode() $normalizationForm
                    'FULLY-NORMALIZED'
           Product: XPath / XQuery / XSLT
           Version: Last Call drafts
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: minor
          Priority: P2
         Component: Functions and Operators
        AssignedTo: ashok.malhotra@oracle.com
        ReportedBy: jeni@jenitennison.com
         QAContact: public-qt-comments@w3.org


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.

Received on Tuesday, 10 May 2005 10:17:53 UTC