#732: fix rt and ver attributes of Link format. #774
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR aims to fix #732.
About
ver
attributeThe lwm2m specification v1.0.x seems to not be clear about the use of quote
"
forver
value :</55>;ver=1.9,
</44>;ver=“2.2”
The version v1.1.x both examples seem to not use quote and the format is clearly defined in §5.1.2. Attributes Classification :
"ver" "=" 1*DIGIT "." 1*DIGIT
, so quote MUST NOT be used in v1.1.x.Regarding this, we choose to be able to read (server side) both quoted and unquoted value and we will write(client) it without using quote.
About
rt="oma.lwm2m"
attributeThere is nothing clear in the specification neither in v1.0.x nor v1.1.x, but all example use quote (
"oma.lwm2m"
).Following the rfc669 quote could be used or not for single rt value.
So we choose to be able to read (server side) both quoted and unquoted value and we will write(client) it with quote (like in lwm2m example).