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 1494 - [XQuery] encoding names
Summary: [XQuery] encoding names
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XQuery 1.0 (show other bugs)
Version: Last Call drafts
Hardware: PC Windows XP
: P2 normal
Target Milestone: ---
Assignee: Don Chamberlin
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-06-14 10:43 UTC by Michael Kay
Modified: 2005-08-29 22:08 UTC (History)
0 users

See Also:


Attachments

Description Michael Kay 2005-06-14 10:43:55 UTC
Section 4.1 doesn't say what constitutes a valid encoding name. It also uses
lower-case for example encodings such as utf-8, whereas the IANA specification
of these names defines their preferred representation as upper case.

Proposal: 

(1) add

"The value of the string literal following the keyword "encoding" is an encoding
name, and follows the same rules as the EncName specified in an XML declaration
in [XML].

(2) change the examples to use IANA registered character set names as written:
UTF-8, UTF-16, US-ASCII in upper case

(3) (optionally) add a reference to the note (or a copy of the note) in the XML
spec that says processors "should" treat encoding names as case-insensitive (at
least in the case of IANA-registered names)
Comment 1 Paul Cotton 2005-07-28 15:18:56 UTC
The XML Query WG adopted the proposed solution at its Jul 13 meeting [1].

/paulc

[1] http://lists.w3.org/Archives/Member/w3c-xml-query-wg/2005Jul/0035.html 
(member only)