It has the advantage of allowing nested data structures. So like in my example we can nicely model an array of signed_data and it would be quite obvious which parameters to include for signature checking for everyone.
With a flat key=>value structure it's not so obvious anymore and might lead to errors.
Also json knows basic datatypes (strings, numbers, ...) so there is less risk of misinterpretation/wrong conversion.
A json-parser is available in any language you can think of (see http://json.org/), and some/many popular languages have it already built-in.
With a flat key=>value structure it's not so obvious anymore and might lead to errors.
Also json knows basic datatypes (strings, numbers, ...) so there is less risk of misinterpretation/wrong conversion.
A json-parser is available in any language you can think of (see http://json.org/), and some/many popular languages have it already built-in.
Well, while there is a C parser avaliable, most seem aimed at full blown systems, a sensor platform may have as little as 8MHz, 16KByte flash space and 2KByte ram.
However even those devices can cope with simple json, so its not a "must not have"
