Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Zach Shelby <zach@sensinode.com>
In-Reply-To: <4F4F40D3.3040401@toshiba.co.jp>
Date: Thu, 1 Mar 2012 15:32:51 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <2355688C-D382-48EB-A2B7-7251C57AD6F0@sensinode.com>
References: <4F464C15.6010006@piuha.net> <4F4F40D3.3040401@toshiba.co.jp>
To: Yusuke DOI <yusuke.doi@toshiba.co.jp>
Cc: Cullen Jennings <fluffy@cisco.com>,
 General discussion of application-layer protocols <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] SenML
Precedence: list

Hi Yusuke,

Our main use case for the senml+exi representation is for strict mode. =
We believe the vast majority of implementations will be configured in =
this mode as it makes the most sense for M2M applications as you point =
out. The only reason we included a MAY for non-strict was to allow such =
use. However if as you point out that might cause interoperability =
problems, I would be in favor of making strict mode a MUST.

Thanks!
Zach

On Mar 1, 2012, at 11:26 AM, Yusuke DOI wrote:

> Hi,
>=20
> I have a question on EXI use.
>=20
> Is it practical to allow both strict (SHOULD) and non-strict (MAY) ?
>=20
> In this case, some nodes may not have non-strict grammar. So, =
nonstrict-capable-and-extended-sender and strict-no-extension-receiver =
must make some agreement to make a communication in strict mode.
>=20
> IMHO, I like strict schema-informed (because it can reduce or =
eliminate dynamic memory allocation).
>=20
> Regards,
>=20
> Yusuke
>=20
>=20
>=20
> (2012/02/23 23:24), Jari Arkko wrote:
>> Hello again,
>>=20
>> This is another draft that we'd like to get feedback on. It is yet =
another component that the authors have used in their work around small =
and smart devices. The goal is to define a base data format that sensors =
and other Internet of Things devices can easily use, preferably without =
having to define entirely new schemes and different structures just to =
measure a slightly different thing.
>>=20
>> http://tools.ietf.org/html/draft-jennings-senml-08
>>=20
>> The abstract says:
>>=20
>> This specification defines media types for representing simple sensor
>> measurements and device parameters in the Sensor Markup Language
>> (SenML). Representations are defined in JavaScript Object Notation
>> (JSON), eXtensible Markup Language (XML) and Efficient XML
>> Interchange (EXI), which share the common SenML data model. A simple
>> sensor, such as a temperature sensor, could use this media type in
>> protocols such as HTTP or CoAP to transport the measurements of the
>> sensor or to be configured.
>>=20
>> Comments appreciated. Necessary? Correctly defined? Improvement =
suggestions?
>>=20
>> Jari
>>=20
>> _______________________________________________
>> apps-discuss mailing list
>> apps-discuss@ietf.org
>> https://www.ietf.org/mailman/listinfo/apps-discuss
>=20
> _______________________________________________
> apps-discuss mailing list
> apps-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-discuss

--=20
Zach Shelby, Chief Nerd, Sensinode Ltd.
http://www.sensinode.com
http://zachshelby.org  - My blog "On the Internet of Things"
http://6lowpan.net - My book "6LoWPAN: The Wireless Embedded Internet"
Mobile: +358 40 7796297