Re: [apps-discuss] +exi

Peter Saint-Andre <stpeter@stpeter.im> Fri, 16 December 2011 16:29 UTC

Return-Path: <stpeter@stpeter.im>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC64621F8B8A for <apps-discuss@ietfa.amsl.com>; Fri, 16 Dec 2011 08:29:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.693
X-Spam-Level:
X-Spam-Status: No, score=-102.693 tagged_above=-999 required=5 tests=[AWL=-0.694, BAYES_00=-2.599, J_CHICKENPOX_33=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e+ViGKdaj0+F for <apps-discuss@ietfa.amsl.com>; Fri, 16 Dec 2011 08:29:36 -0800 (PST)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 32D8C21F8B10 for <apps-discuss@ietf.org>; Fri, 16 Dec 2011 08:29:36 -0800 (PST)
Received: from dhcp-64-101-72-220.cisco.com (unknown [64.101.72.220]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id EA180423AD; Fri, 16 Dec 2011 09:37:18 -0700 (MST)
Message-ID: <4EEB6EB2.30807@stpeter.im>
Date: Fri, 16 Dec 2011 09:15:46 -0700
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Zach Shelby <zach@sensinode.com>
References: <01O8GE5O3B5K00RCTX@mauve.mrochek.com> <C68CB012D9182D408CED7B884F441D4D0611DAC31D@nambxv01a.corp.adobe.com> <4EC31F1E.6070304@stpeter.im> <8p86c7d6chvadsku6k5dhct20qkl7uk73l@hive.bjoern.hoehrmann.de> <4EC326FE.1010809@stpeter.im> <lu96c7hsl37325nn3184ub4vr88qjgja50@hive.bjoern.hoehrmann.de> <EDB50792-348B-4693-9FDF-04BA091F8BE9@sensinode.com> <4EE78F2F.2070601@stpeter.im> <20111213215816.GI5525@jay.w3.org> <5EFF390A-3D29-4F15-95BE-C81EFCF6D3D5@mnot.net> <20111214092327.GK5525@jay.w3.org> <7472087B-86F9-4683-BA74-F70EC98D483C@sensinode.com>
In-Reply-To: <7472087B-86F9-4683-BA74-F70EC98D483C@sensinode.com>
X-Enigmail-Version: 1.3.4
OpenPGP: url=https://stpeter.im/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: paduffy@cisco.com, Mark Nottingham <mnot@mnot.net>, Thomas Herbst <therbst@silverspringnet.com>, "apps-discuss@ietf.org" <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] +exi
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Dec 2011 16:29:36 -0000

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/