W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2009

Re: Review of Content-Encoding: value token

From: Mark Nottingham <mnot@mnot.net>
Date: Fri, 23 Jan 2009 11:22:43 +1100
Cc: Carine Bournez <carine@w3.org>, ietf-http-wg@w3.org
Message-Id: <7187413D-4013-48F9-91AB-E58CE8FFBB3A@mnot.net>
To: Roy T. Fielding <fielding@gbiv.com>

Yes. If it doesn't preserve characters, all sorts of mess can result,  
e.g., with ETag comparison, range retrieval, etc.


On 22/01/2009, at 7:01 AM, Roy T. Fielding wrote:

>
> On Jan 21, 2009, at 11:13 AM, Carine Bournez wrote:
>
>> Dear HTTPbis Working Group,
>>
>> The Efficient XML Interchange (EXI) Working Group is seeking advice  
>> and
>> review of a proposal for a new registered HTTP content coding token
>> called "exi".
>>
>> The EXI Working Group has discussed the content type management  
>> issue and
>> is suggesting to use a Content-Encoding, whenever possible, in order
>> to retain the original XML or XML-based media type (e.g. xhtml, rdf,
>> svg...). We also register a fallback "application/exi" media type,  
>> for
>> the protocols that have no Content-Encoding capability.
>
> No, it doesn't qualify as a content encoding or transfer encoding.
> It is not decoded to the original type.  It is just another media  
> type.
> If you want to retain the original type (I have no idea why), then
> put it in a parameter.  E.g., application/exi;orig="svg"
>
> ....Roy
>
>


--
Mark Nottingham     http://www.mnot.net/
Received on Friday, 23 January 2009 00:23:22 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:51:00 GMT