Re: [apps-discuss] +exi

[Peter Saint-Andre <[e-mail]>]

On 12/16/11 12:24 AM, Zach Shelby wrote:
> On Dec 14, 2011, at 11:23 AM, Carine Bournez wrote:
> 
>> In the schema-informed mode the encoder and the decoder use a
>> schema, the EXI 1.0 version specifies XML schema informed grammars.
>> The reference to that schema is carried in the EXI header. The
>> format of that "schemaId" is not specified for 1.0 processors, it
>> can be whatever is practical for the application. It is *optional*
>> in the EXI header, even when a schema is in use: applications can
>> also "share" this information out of band. EXI 1.0 is intentionally
>> liberal on a number of details and defers them to the application
>> level, so that it can support a large range of use cases.
> 
> 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.

Zach, thanks for clarifying the matter. Perhaps it would make sense for
someone to write a brief I-D describing the rationale for media types
with the +exi suffix and the information required to register such types.

Peter

-- 
Peter Saint-Andre
https://stpeter.im/