Looking for some guidance around the usage of configurable attribute in 633 servicespecification.
As per the definition , If value for specCharacteristic .configurable is true, it indicates that the target Characteristic is configurable.
Does it mean that when configurable is true , consumer can perform Create, Update and Delete on that characteristic ?
We have a use case where consumer A can do a create /update and consumer B is allowed to do only an update . Hence characteristic needs to be represented with allowed operation Create and Update as in example 3.Is there an option to explicitly represent the allowed operations on a particular characteristic to provides a clear demarcation ?
characteristics1 : Allowed operation : Read
characteristics 2 : Allowed operation : Update
characteristics 3 : Allowed operation : Create and Update@Rati Mehrotra