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

Commentary:     we might as well remove any reference to codepoints ...
Paragraph (version A):
Optionally, an application might use the general format defined here,
but also register a new media type and an associated Content-Format
identifier -- typically one in the range 10000-64999 -- instead of
using application/multipart-core.
Paragraph (version B):
Optionally, an application might use the general format defined here,
but also register a new media type and an associated Content-Format
identifier instead of using application/multipart-core.
Draft: draft-ietf-core-multipart-ct

Commentary: … different ways 
 There is little a reader of the document could actually do with this information .
Paragraph (version B):
The collection is encoded as a CBOR RFC7049 array with an even number
of elements.  The second, fourth, sixth, etc. element is a byte
string containing a representation, or the value "null" if an
optional part is indicated as not given.  The first, third, fifth,
etc. element is an unsigned integer specifying the content format ID
of the representation following it.
Draft: draft-ietf-core-multipart-ct

Commentary: … oundaries defined by the CDDL 
 We should add something like : " within the syntactical boundaries defined by the CDDL in Figure 1 . "
Paragraph (version A):
Applications using the application/multipart-core Content-Format
define the internal structure of the application/multipart-core
representation.
Paragraph (version B):
Applications using the application/multipart-core Content-Format
define the semantics as well as the internal structure of the
application/multipart-core representation according to the syntax
described by the CDDL in mct-cddl.
Draft: draft-ietf-core-multipart-ct

Commentary: Sure . Apologies , I had completely misunderstood the gist of your comment ( and  's reply ) . 
  / message - body / request or response body/ 
 I still do n't understand why the only permissible use of this representation format is inside a CoAP payload . Ca n't I transfer the CBOR structure over HTTP or store it in a file ?
Paragraph (version A):
This memo defines application/multipart-core, an application-
independent media-type that can be used to combine representations of
several different media types into a single CoAP message-body with
minimal framing overhead, each along with a CoAP Content-Format
identifier.
Paragraph (version A):
This memo defines application/multipart-core, an application-
independent media-type that can be used to combine representations of
several different media types into a single CoAP RFC7252 message-body
with minimal framing overhead, each along with a CoAP Content-Format
identifier.
Paragraph (version B):
This memo defines application/multipart-core, an application-
independent media-type that can be used to combine representations of
several different media types into a single message, such as a CoAP
request or response body, with minimal framing overhead, each along
with a CoAP Content-Format identifier.
Paragraph (version B):
This memo defines application/multipart-core, an application-
independent media-type that can be used to combine representations of
several different media types into a single message, such as a CoAP
RFC7252 request or response body, with minimal framing overhead, each
along with a CoAP Content-Format identifier.
Draft: draft-ietf-core-multipart-ct

Commentary: WFM 
 Oops , I 'd missed that . I will change that instance as well . 
 It should not preclude 0 , 1 or 2 , therefore : s / several / zero or more/ 
 Maybe just " representations of different media types " ?
Paragraph (version A):
This memo defines application/multipart-core, an application-
independent media-type that can be used to combine representations of
several different media types into a single message, such as a CoAP
request or response body, with minimal framing overhead, each along
with a CoAP Content-Format identifier.
Paragraph (version A):
This memo defines application/multipart-core, an application-
independent media-type that can be used to combine representations of
several different media types into a single message, such as a CoAP
RFC7252 request or response body, with minimal framing overhead, each
along with a CoAP Content-Format identifier.
Paragraph (version B):
This memo defines application/multipart-core, an application-
independent media-type that can be used to combine representations of
zero or more different media types into a single message, such as a
CoAP request or response body, with minimal framing overhead, each
along with a CoAP Content-Format identifier.
Paragraph (version B):
This memo defines application/multipart-core, an application-
independent media-type that can be used to combine representations of
zero or more different media types into a single message, such as a
CoAP RFC7252 request or response body, with minimal framing overhead,
each along with a CoAP Content-Format identifier.