W3C home > Mailing lists > Public > public-ietf-w3c@w3.org > October 2009

Re: Requesting IESG Approval for the Media Type application/xslt+xml, application/xquery+xml, and application/xquery

From: Alexey Melnikov <alexey.melnikov@isode.com>
Date: Fri, 02 Oct 2009 11:42:18 +0100
Message-ID: <4AC5D90A.9030004@isode.com>
To: Liam Quin <liam@w3.org>
CC: Philippe Le Hegaret <plh@w3.org>, public-ietf-w3c@w3.org, Dan Connolly <connolly@w3.org>, iesg@ietf.org, Carine Bournez <carine@w3.org>
Liam Quin wrote:

>On Thu, Oct 01, 2009 at 10:14:57PM +0100, Alexey Melnikov wrote:
>  
>
 [...]

>>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 &#xddd;  
>>>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.
>  
>
If this is done for backward compatibility, this is Ok with me.

Please address Martin's concern about Latin-1 not being registered.
Received on Friday, 2 October 2009 10:42:54 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 2 October 2009 10:42:54 GMT