jiebi/ids-paragraph-commentary-corpus huggingface dataset:
Draft: draft-ietf-core-senml

Commentary: Fixes 
 Updated to add in Air and  sugestions 
 Looks good to me
A SenML Record is referred to as "expanded" if it does not contain
any base values and has no relative times, but the the base values of
the SenML Pack (if any) are applied to the Record.  That is, name and
base name are concatenated, base time is added to the time of the
Record, if Record did not contain Unit the Base Unit is applied to
the record, etc.
Sometimes it is useful to be able to refer to a defined normalized
format for SenML records.  This normalized format tends to get used
for big data applications and intermediate forms when converting to
other formats.
A SenML Record is referred to as "resolved" if it does not contain
any base values and has no relative times, but the the base values of
the SenML Pack (if any) are applied to the Record.  That is, name and
base name are concatenated, base time is added to the time of the
Record, if Record did not contain Unit the Base Unit is applied to
the record, etc.  In addition the records need to be in chronological
order.
Draft: draft-ietf-core-senml

Commentary: Pointed out in review this was missing 
 Works for me
A base sum is added to the sum found in an entry, similar to Base
Time.
Draft: draft-ietf-core-senml

Commentary: Fixes 
 This makes some of the examples very long . I preferred the presentation where all attributes of a Record are on a single line , when feasible . Especially for the " multiple data points " examples . Anyway ,  's comment was about indentation , which I agree should be ( and is now ) fixed . 
 See email from       examples in SenML "
Value of the entry.  Optional if a Sum value is present, otherwise
required.  Values are represented using basic data types.  This
specification defines floating point numbers ("v" field for
"Value"), booleans ("vb" for "Boolean Value"), strings ("vs" for
"String Value") and binary data ("vd" for "Data Value").  Exactly
one value field MUST appear unless there is Sum field in which
case it is allowed to have no Value field.
A SenML Record is referred to as "resolved" if it does not contain
any base values and has no relative times, but the the base values of
the SenML Pack (if any) are applied to the Record.  That is, name and
base name are concatenated, base time is added to the time of the
Record, if Record did not contain Unit the Base Unit is applied to
the record, etc.  In addition the records need to be in chronological
order.  An example of this is show in resolved-ex.
The following shows the example from the previos section show in
resolved format.
The following example shows a sensor that returns different data
types.
Draft: draft-ietf-core-senml

Commentary: The link was missing from schema . After this is merged , all the example need to be regenerated . 
 Given we want the l to have a defined integer value in the CBOR table , I think a good approach is define the l attribute as a string here then say what goes in it in the other draft that defines link . This is also good for EXI .
Value of the entry.  Optional if a Sum value is present, otherwise
required.  Values are represented using basic data types.  This
specification defines floating point numbers ("v" field for
"Value"), booleans ("vb" for "Boolean Value"), strings ("vs" for
"String Value") and binary data ("vd" for "Data Value").  Exactly
one value field MUST appear unless there is Sum field in which
case it is allowed to have no Value field.
A SenML Record is referred to as "resolved" if it does not contain
any base values and has no relative times, but the the base values of
the SenML Pack (if any) are applied to the Record.  That is, name and
base name are concatenated, base time is added to the time of the
Record, if Record did not contain Unit the Base Unit is applied to
the record, etc.  In addition the records need to be in chronological
order.
Draft: draft-ietf-core-senml

Commentary: Fix to issue
A SenML object is referred to as "expanded" if it does not contain
any base values and has no relative times.
A SenML Record is referred to as "expanded" if it does not contain
any base values and has no relative times, but the the base values of
the SenML Pack (if any) are applied to the Record.  That is, name and
base name are concatenated, base time is added to the time of the
Record, if Record did not contain Unit the Base Unit is applied to
the record, etc.