Re: [apps-discuss] Fwd: New Version Notification for draft-shelby-exi-registration-01.txt

[Julian Reschke <[e-mail]>]

On 2012-04-13 19:04, Henry S. Thompson wrote:
> ...
>> You can use EXI to compress application/rdf+xml, but once you did that
>> it's not application/rdf+xml anymore. The same would be true for
>> application/rdf+xml compressed with gzip (which reminds me about an
>> epic debate we had last year about ".svgz").
>
> What?  Surely Content-Encoding is logically independent from, and
> processing-wise transparent wrt Content-Type.

Yes.

> Here's what 2616 says:
>
>    "The Content-Type entity-header field indicates the media type of
>     the entity-body"
>
> and
>
>    "The Content-Encoding entity-header field is used as a modifier to
>     the media-type. When present, its value indicates what additional
>     content codings have been applied to the entity-body, and thus what
>     decoding mechanisms must be applied in order to obtain the
>     media-type referenced by the Content-Type header field. "
>
> So I take an entity-body which is application/rdf+xml, I encode it
> with gzip, I send it marked
>
>   Content-Encoding: gzip
>   Content-Type: application/rdf+xml
>
> The gzip-aware UA decodes the entity body with gunzip and hands over
> the result as application/rdf+xml.
>
> Same for exi, modulo the fudge about infoset vs. character sequence
> which was thrashed through wrt the 'exi' content-code.
> ...

All true, but as far as I can tell, you didn't mention Content-Encoding 
in the message I replied to.

Best regards, Julian