Simon Bernard

(An OMA issue which seems about content format : https://github.com/OpenMobileAlliance/OMA_LwM2M_for_Developers/issues/514)

Thx for the feedback. The idea was to keep consistent with other write/create dialog at (instance/object level) By the way some description are sometime bigger and so the large is...

This is done for server in #518.

> For now Orange will focus mainly on verifying the already implemented LWM2M 1.1 functionality and on the Observe-Composite implementation. :+1: > After the holidays we also intend to start...

@Przem83, @Michal-Wadowski just a ping in case you missed this (as I didn't get any feedback) if there is nothing to add it's perfectly OK too :slightly_smiling_face:

> And we have to use stable release, so it's the reason why we waiting for 2.0.0 You are not allowed to use milestones release ?

> It's just that we are getting some pressure to move to a full release ASAP to avoid rewriting code (the one that uses Leshan) in case of any major...

I had planned to refer the TestObject here too. @hannestschofenig thx for doing this. :pray: > I am wondering whether it would make sense to have some of the interoperability...

> If we just focus on LwM2M-specific testing, then there is the question about how those tests should be done automatically. I have been working with the IETF OAuth community...

I prefer the second solution : a separate field in LwM2mModel, e.g. `Map reusableResources`.