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

Commentary: Update the ABNF to refer to httpbis - semantics ; include quoted - pair  from 7230/7231 to httpbis - semantics Address the question   did not ask :-)
Paragraph (version B):
when it needs to be updated to understand these field values and the
values controlled by them; registries are used to evolve these name
spaces in a controlled way.  SenML packs can be processed by a
consumer while not understanding all the information in them, and
information can generally be preserved in this processing such that
it is useful for further consumers.
Paragraph (version A):
This specification provides a formal definition of the syntax of
Content-Format-Spec strings using ABNF notation RFC5234, which
contains three new rules and a number of rules collected and adapted
from various RFCs RFC7231 RFC6838 RFC5234 RFC8866.
Paragraph (version B):
This specification provides a formal definition of the syntax of
Content-Format-Spec strings using ABNF notation RFC5234, which
contains three new rules and a number of rules collected and adapted
from various RFCs I-D.ietf-httpbis-semantics RFC6838 RFC5234 RFC8866.
Draft: draft-ietf-core-senml-data-ct

Commentary: Discuss and comments from
Paragraph (version A):
The receiver is expected to know how to interpret the data in the
"vd" field based on the context, e.g., name of the data source and
out-of-band knowledge of the application.  However, this context may
not always be easily available to entities processing the SenML pack.
To facilitate automatic interpretation it is useful to be able to
indicate an Internet media type and, optionally, content codings
right in the SenML Record.
Paragraph (version B):
The receiver is expected to know how to interpret the data in the
"vd" field based on the context, e.g., name of the data source and
out-of-band knowledge of the application.  However, this context may
not always be easily available to entities processing the SenML pack,
especially if the pack is propagated over time and via multiple
entities.  To facilitate automatic interpretation it is useful to be
able to indicate an Internet media type and, optionally, content
codings right in the SenML Record.
Paragraph (version A):
a CoAP Content-Format number in decimal form with no leading zeros
(except for the value "0" itself).  This value represents an
unsigned integer in the range of 0-65535, similar to the CoRE Link
Format RFC6690 "ct" attribute).
Paragraph (version B):
a CoAP Content-Format number in decimal form with no leading zeros
(except for the value "0" itself).  This value represents an
unsigned integer in the range of 0-65535, similar to the "ct"
attribute defined in RFC7252 for CoRE Link Format RFC6690).
Paragraph (version A):
The Base Content-Format Field, label "bct", provides a default value
for the Content-Format Field (label "ct") within its range.  The
range of the base field includes the Record containing it, up to (but
not including) the next Record containing a "bct" field, if any, or
up to the end of the pack otherwise.  Resolution (RFC8428) of this
base field is performed by adding its value with the label "ct" to
all Records in this range that carry a "vd" field but do not already
contain a Content-Format ("ct") field.
Paragraph (version B):
The Base Content-Format Field, label "bct", provides a default value
for the Content-Format Field (label "ct") within its range.  The
range of the base field includes the Record containing it, up to (but
not including) the next Record containing a "bct" field, if any, or
up to the end of the pack otherwise.  The process of resolving
(RFC8428) this base field is performed by adding its value with the
label "ct" to all Records in this range that carry a "vd" field but
do not already contain a Content-Format ("ct") field.
Draft: draft-ietf-core-senml-data-ct

Commentary: ... addressing    review .
Paragraph (version A):
The Sensor Measurement Lists (SenML) media type supports multiple
types of values, from numbers to text strings and arbitrary binary
data values.  In order to simplify processing of the data values,
this document proposes to specify a new SenML field for indicating
the Content-Format of the data.
Paragraph (version B):
The Sensor Measurement Lists (SenML) media type supports multiple
types of values, from numbers to text strings and arbitrary binary
data values.  In order to facilitate processing of binary data
values, this document specifies a pair of new SenML fields for
indicating the Content-Format of those binary data values, i.e.,
their Internet media type including parameters as well as any
Content-Coding applied.
Paragraph (version A):
The receiver is expected to know how to interpret the data in the
"vd" field based on the context, e.g., name of the data source and
out-of-band knowledge of the application.  However, this context may
not always be easily available to entities processing the SenML pack.
To facilitate automatic interpretation it is useful to be able to
indicate an Internet media type and content-coding right in the SenML
Record.  The CoAP Content-Format (RFC7252) provides just this
information; enclosing a Content-Format number (in this case number
60 as defined for content-type application/cbor in RFC8949) in the
Record is illustrated in ex-2.  All registered CoAP Content-Formats
are listed in the IANA.core-parameters IANA.core-parameters as
specified by RFC7252.
Paragraph (version B):
The receiver is expected to know how to interpret the data in the
"vd" field based on the context, e.g., name of the data source and
out-of-band knowledge of the application.  However, this context may
not always be easily available to entities processing the SenML pack.
To facilitate automatic interpretation it is useful to be able to
indicate an Internet media type and content-coding right in the SenML
Record.  The CoAP Content-Format (RFC7252) provides this information
in the form of a single unsigned integer; enclosing a Content-Format
number (in this case number 60 as defined for content-type
application/cbor in RFC8949) in the Record is illustrated in ex-2.
All registered CoAP Content-Format numbers are listed in the
IANA.core-parameters IANA.core-parameters as specified by RFC7252.