Re: [apps-discuss] SenML

I am in support of strict-only. IMO, you do it if you need to conserve space and code as much as possible. If you don't, pure JSON mode of SenML may actually be the right choice for you.

Jari

On 01.03.2012 15:32, Zach Shelby wrote:
> 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,
>>
>> I have a question on EXI use.
>>
>> Is it practical to allow both strict (SHOULD) and non-strict (MAY) ?
>>
>> 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.
>>
>> IMHO, I like strict schema-informed (because it can reduce or eliminate dynamic memory allocation).
>>
>> Regards,
>>
>> Yusuke
>>
>>
>>
>> (2012/02/23 23:24), Jari Arkko wrote:
>>> Hello again,
>>>
>>> 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.
>>>
>>> http://tools.ietf.org/html/draft-jennings-senml-08
>>>
>>> The abstract says:
>>>
>>> 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.
>>>
>>> Comments appreciated. Necessary? Correctly defined? Improvement suggestions?
>>>
>>> Jari
>>>
>>> _______________________________________________
>>> apps-discuss mailing list
>>> apps-discuss@ietf.org
>>> https://www.ietf.org/mailman/listinfo/apps-discuss
>> _______________________________________________
>> apps-discuss mailing list
>> apps-discuss@ietf.org
>> https://www.ietf.org/mailman/listinfo/apps-discuss