On 2009/10/02 10:30, Liam Quin wrote: > On Thu, Oct 01, 2009 at 10:14:57PM +0100, Alexey Melnikov wrote: >> <http://www.w3.org/TR/2009/PER-xquery-20090421/#id-registration-of-mime-type> >> 2). >>> The syntax of XQuery is expressed in Unicode but may be written with >>> any Unicode-compatible character encoding, including UTF-8 or UTF-16, >>> or transported as US-ASCII or Latin-1 with Unicode characters outside >>> the range of the given encoding represented using an XML-styleෝ >>> syntax. >> Is there any good reason for allowing Latin-1? IETF pretty much settled >> on only using US-ASCII, UTF-8 (and rarely UTF-16). > > To the best of my memory it was for in response to a comment regarding > HTTP cpmpatibility, but, there is also no good reason to forbid it at > this point, with over 50 XQuery implementations in the field. > > For XQuery 1.1 we could possibly disallow Latin-1, but I don't think > we'd gain anything now. If we were still in 2005, we'd be in a > position to change such things, and I think do a better job. > Removing it could only hurt interop now I think. I think http://www.w3.org/TR/2009/PER-xquery-20090421/#dt-encoding-declaration makes it clear that XQuery documents can be in very much any encoding. So the mention of Latin-1 in the Mime type registration is just an example. As such, it can stay in the registration template or be removed without any effect on interoperability. [charset expert reviewer hat on] However, there is no 'charset' "Latin-1" registered at http://www.iana.org/assignments/character-sets. So I strongly suggest to replace it with ISO-8859-1, or leave it out. [hat off] Regards, Martin. -- #-# Martin J. Dürst, Professor, Aoyama Gakuin University #-# http://www.sw.it.aoyama.ac.jp mailto:duerst@it.aoyama.ac.jpReceived on Friday, 2 October 2009 08:03:29 UTC
This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:09:51 UTC