Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify usage of create/update on object instances with R-only resources #30

Closed
boaks opened this issue Feb 20, 2015 · 3 comments
Closed

Comments

@boaks
Copy link

boaks commented Feb 20, 2015

When resources are R-only, what must then be obeyed using the operation create or replace on object instances?

Example:
An object (id 50000) defines to have a mandatory R-only resource (ID 1, water level, R, S, M, …).
To create a new instance of 50000, must the resource with ID 1 be provided?
To replace a instance of 50000, must/could the resource with ID 1 be provided?

@msangoi
Copy link

msangoi commented Mar 4, 2015

A typical example is the Software Management object.
When a new instance is created, how do we provide the mandatory R-only resources 'PkgName' and 'PkgVersion'?

@boaks
Copy link
Author

boaks commented Jun 8, 2015

"OMA-DM-LightweightM2M-2015-0033R01-CR_R_Only_Resource_Clarification.doc" will clarify it.

But why does it introduce a different processing of mandatory (use new value) and otional (ignore new value)?

• For the “Delete”, “Observe”, “Write Attributes”, and “Discover” operations, the LWM2M Client
MUST perform the operation since those operations have no effect on the Resource.

"Observe" should be moved to the "Read" above, though it includes a initial read.

@boaks
Copy link
Author

boaks commented Jun 17, 2015

Fixed with OMA-TS-LightweightM2M-V1_0-20150615-D.

@boaks boaks closed this as completed Jun 17, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants