- From: Jonathan Robie <jonathan.robie@datadirect.com>
- Date: Mon, 11 Oct 2004 17:16:34 -0400
- To: XML Query Comments <public-qt-comments@w3.org>, Martin Duerst <duerst@w3.org>, w3c-i18n-ig@w3.org
Hi Martin, On behalf of the XQuery Working Group, I would like to respond to following issue, which is called qt-2004Feb0362-06 in our issues list: > [9] Section 3, 'encoding': "If this parameter is not specified, and > the output method does not specify any additional requirements, > the encoding used is implementation defined." > This should be more specific. In the absence of an 'encoding' > parameter, information e.g. given to an implementation via an > option, and specific information for a particular 'host language' > (e.g. other than XQuery or XSLT), there should be a default of > UTF-8. It appeared in this email: http://lists.w3.org/Archives/Public/public-qt-comments/2004Feb/0362.html The Serialization specification leaves much of this up to the host language, as Henry indicated here: http://lists.w3.org/Archives/Public/public-qt-comments/2004Sep/0082.html As Henry says, this is no longer in the optional, and each host language must specify how it is handled. XQuery has decided the following: 1. An XQuery implementation is not required to support serialization. For instance, it might deliver all results using StAX, SAX, or DOM. 2. If serialization is supported, XQuery uses the XML method only for serialization. The default encoding may be either UTF8 or UTF16 - the choice is implementation-defined. 3. The choice of normalization is also implementation-defined. Please let us know if you feel this resolution is not acceptable. Thanks! Jonathan On behalf of the XQuery Working Group
Received on Monday, 11 October 2004 21:17:06 UTC