Re: [core] Designs to resolve streaming issues in SenML

[Christian Amsüss <[e-mail]>]

Hello Cullen,

On Wed, Jan 13, 2016 at 01:57:02PM +0000, Cullen Jennings (fluffy) wrote:
> The objects can also have the base values right in the object and the
> base values apply to all the things in the object and any future
> objects in the array. 
>
> Appreciate any thoughts people have on pro / cons of the -03 design vs -04 design.

The -03 draft is parsable with minimum RAM: I've assembled a crude
demo[1] that shows that given a list of known integer-valued resources
on a device, it is possible to parse incoming SenML-03 with less than 30
bytes of state, with support for arbitrary SenML extensions, all legal
JSON number representations and full URL concatenation semantics.

With the -04 draft, one would have to allocate a buffer for the "n"
value, because before the object finishes, the "bn" might change later
in the same object, and change the context in which it needs to be
interpreted. This could be remedied by making base and entry updates
mutually exclusive (arguably a less straight-forward design), but as
things are, I'd prefer -03.

Best regards
Christian

[1] https://gitlab.com/c.amsuess-energyharvesting/senml-03-streaming-parser-demo/tree/master

-- 
Christian Amsüss                      | Energy Harvesting Solutions GmbH
founder, system architect             | headquarter:
mailto:[e-mail]  | Arbeitergasse 15, A-4400 Steyr
tel:[phone]                | http://www.energyharvesting.at/
                                      | ATU68476614