Closed panekk closed 4 years ago
We will discuss this topic next week at our face-to-face meeting.
We discussed the topic and concluded that it does not make sense to offer three different encoding options for conveying execute arguments. Hence, we will change the text and remove the option for SenML JSON and SenML CBOR.
Thanks for spotting this issue.
Why not allow different encoding options? Wouldn't this depend on the resource? Some could allows just text, some, for example CBOR.
What should be the format of execute arguments sent as SenML JSON or SenML CBOR? It's a new feature introduced in 1.1.1, but it's not defined which labels should be used (existing, or LwM2M-specific, like "vlo"?).