Re: [apps-discuss] +exi

[Carine Bournez <[e-mail]>]

On Fri, Dec 16, 2011 at 09:24:05AM +0200, Zach Shelby wrote:
> Right. It is exactly these kinds of applications that are using schema informed mode natively (without intermediate XML), where the application/foo+exi media type helps to determine this information out of band. When registering foo+exi, the schema information should be included in the registration.  In addition to SE2 mentioned so far, also our specification on SenML [http://tools.ietf.org/html/draft-jennings-senml-07] is requesting an application/senml+exi media type. Both of these media types are aimed at constrained embedded devices.


It seems that you could use application/foo and the content-encoding: exi
instead of registering a different media type. Is your application using a
protocol that has no content-encoding? or do you mean that you use a 
different schema for the exchange of a foo serialized in EXI than a 
text foo? A quick look at http://tools.ietf.org/html/draft-jennings-senml-07 
makes me think it is the latter, for SenML. It does not seem a very nice
way to convey the schema information, SchemaId is meant to serve this 
purpose, not the media type. Since you need to carry other EXI options,
out-of-band or in the EXI header, why not using SchemaId?.


-- 
Carine Bournez -+- W3C Europe