Rationale: -JSON Serialization is becoming more and more popular in RESTful implementations (comparing to XML) --Pros: better readability, concise (also support binary encoding - CBOR) --Cons: less schema validation capability -oneM2M native protocol bindings support JSON already
Suggestion: to add JSON Serialization in SDT4.0 FFS: JSON Schema limitations?
I'm struggling of choosing between JSON Schema vs plain JSON. Many developers think JSON Schema is too verbose and not easy to learn. Should we start with using plain JSON first?
Further more, does it really make sense to re-define the SDT schema itself (domain.xsd) using JSON (or JSON Schema)? Should we just focus on using JSON for concrete 'deviceClass' and 'moduleClass' definition?
It is my impression as well that JSON Schema is way to complicated. I am struggling understanding it myself. Therefore, I would suggest to start by implementing it by example, too. Hopefully, someone can do the format definition later ;)
domain.xsd is the schema, not an actual SDT definition.
In my opinion this depends whether we manage to define a formal description for JSON.
Assuming that we will define the JSON mapping by examples, I would have suggest to have a separate document/page, where we will provide mappings between the XML and JSON formats, and then link from the 'components' description to the appropriate sections in that page.