Ticket 183: "requested resource" in content-encoding definition

• From: Julian Reschke <julian.reschke@gmx.de>
• Date: Tue, 06 Apr 2010 16:15:23 +0200
• To: HTTP Working Group <ietf-http-wg@w3.org>
• Message-ID: <4BBB41FB.7000507@gmx.de>

Hi,

see <http://trac.tools.ietf.org/wg/httpbis/trac/ticket/183>:

> p3 3.2.1:
>
>     Content-Encoding may be used to indicate any additional content codings applied to the data, usually for the purpose of data compression, that are a property of the requested resource. There is no default encoding.
>
> Saying that compression is a property of the requested resource implies that 'requested resource' includes conneg, which may confuse particularly astute readers.
>
> Probably better to say that they're a property of the requested representation, or similar.

Or of the returned entity body.

That being said just removing that part seems to make it clear enough; 
proposal:

    Content-Encoding can be used to indicate any additional content
    codings applied to the data, usually for the purpose of data
    compression.  There is no default encoding.

(see 
<http://trac.tools.ietf.org/wg/httpbis/trac/attachment/ticket/183/i183.diff>)

Best regards, Julian

Received on Tuesday, 6 April 2010 14:15:58 UTC