jiebi/ids-paragraph-commentary-corpus huggingface dataset:
Draft: draft-schaad-cose

Commentary: Add an example to the document for a multi - signature item .
payload contains the serialized content to be signed.
protected is optional and contains additional information to be
authenticated by the signature.  The field generally holds data
about the signture operation or inner content.
header is optional and contains additional information for
evaluation of the signature.
Concatenate the "protected" field and the "payload" field into a
single octet string.  If the "protected" field is absent, use a
zero length bstr object for it.
contains attributes about the payload which are to be protected by
the signature.  An example of such an attribute would be the
content type ('cty') attribute.  The content is a CBOR map of
attributes which is encoded to a byte stream.  This field MUST NOT
contain attributes about the signture, even if those attributes
are common across multiple signtures.
contains attributes about the payload which are not protected by
the signature.  An example of such an attribute would be the
content type ('cty') attribute.  This field MUST NOT contain
attributes about a signature, even if the attributes are common
across multiple signatures.
contains the serialized content to be signed.
is either a single signature or an array of signature values.
is optional and contains additional information to be
authenticated by the signature.  The field holds data about the
signture operation.  The field MUST NOT hold attributes about the
payload being signed.  The content is a CBOR map of attributes
which is encoded to a byte stream.
contains attributes about the signture which are not protected by
the signature.  This field MUST NOT contain attributes about the
payload being signed.
contains the computed signature value.
Create a Sig_structure object and populate it with the appropirate
fields.
Create the value to be hashed by encode the Sig_structure to a
byte string.
Place the signature value into the appropriate signature field.
Draft: draft-schaad-cose

Commentary: Correct descriptions of Direct and Key Agreement Direct Change examples in the back to have " real " examples - they are  rather than CBOR , but that makes them shorter and easier to read .
The 'protected', 'iv', 'aad', 'ciphertext' and 'recipients' fields
MUST be null.
The plain text to be encrypted is the key from next layer down
(usually the content layer).
At a minimum, the 'unprotected' field SHOULD contain the 'alg'
parameter as well as a parameter identifying the shared secret.
The 'protected', 'aad', 'iv', and 'tag' fields all use the 'null'
value.
At a minimum, the 'unprotected' field SHOULD contain the 'alg'
parameter as well as a parameter identifying the asymmetric key.
The 'unprotected' field MUST contain the 'epk' parameter.