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

[Ned Freed <[e-mail]>]

> Julian Reschke writes:

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

> Ah, I see the disconnect.  In my original message, I said:

>  "Why not call it application/senml+xml and encode it with EXI?
>   Doesn't that tell you everything you need?"

> I should have been more explicit -- what I meant the above to convey
> was

>  "Why not call it application/senml+xml and encode it with EXI?
>   That is, use Content-Type: application/senml+xml and
>                Content-Encoding: exi .
>   Doesn't that tell you everything you need?"

I'm a newcomer to all this myself, but I'm fairly sure the general answer to
that is "no".

This will work if the exi encoding isn't using schema-specific compression. But
what if it is? Then you need to see start of the actual content before you can
be sure you can decode it - it could contain a SchemaId pointing at a schema
you do not have available for whatever reason. Or it could contain no SchemaId
at all and you don't know what the default schema is for this type.

So this would mess up negotiation schemes.

				Ned