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

[Julian Reschke <[e-mail]>]

On 2012-04-13 22:28, Henry S. Thompson wrote:
> Julian Reschke writes:
>
>> On 2012-04-13 22:02, Carine Bournez wrote:
>>> ...
>>> I suppose that the registration for application/senml+xml could
>>> mandate use of a particular schema when encoded with EXI and exclude
>>> any additional schema (i.e. no schemaId allowed).
>>> ...
>>
>> Nope. Content-Encoding and media type are orthogonal things.
>
> But she said "when encoded with EXI".  Why can't a media type
> registration say that, literally?  That is "When encoding with EXI,
> use this schema: [ref] and schemaID: http://...".

Back to our confusion :-)

Yes, you can use EXI, but you can't use EXI-as-a-HTTP-Content-Encoding 
in this case. The HTTP Content Encoding must be fully defined in absence 
of any out-of-band information.

For instance, a recipient (say browser) needs to be able to remove the 
encoding without having to know *anything* about the media type.

Best regards, Julian