jiebi/ids-paragraph-commentary-corpus huggingface dataset:
Draft: draft-ietf-sacm-coswid

Commentary: Added back IANA registrations ( as provisional ) for swid and swidpath URI schemes . Slight re - wording of the intro paragraph to section 5 ( discussing the schemes ) to reflect this modification .
Paragraph (version A):
This specification defines the following expressions for use in
CoSWID and to provide interoperability with schemes used in SWID.
Because both the "swid" and "swidpath" schemes are to be interpreted
within a local, rather than a global, context, neither of these
scheme are URIs as defined in RFC3986 and the swid and swidpath
scheme names are not registered as permanent schemes with IANA.  That
noted, swid and swidpath expressions conform to all rules for URI
syntax.  All uses of these expressions encountered within a CoSWID
are to be interpreted as described in this section.
Paragraph (version B):
This specification defines the following scheme names for use in
CoSWID and to provide interoperability with scheme names used in
SWID.  Because both the "swid" and "swidpath" scheme names are to be
interpreted within a local (rather than a global) context, neither of
these are technically URI scheme names as defined in RFC3986.  For
this reason, the swid and swidpath scheme names are registered with
IANA as provisional, rather than permanent, scheme names.  However,
registering these scheme names as provisional ensures that the scheme
names are reserved and that they are properly defined going forward.
Paragraph (version B):
The swid and swidpath expressions conform to all rules for URI
syntax.  All uses of these expressions encountered within a CoSWID
are to be interpreted as described in this section.
Paragraph (version B):
The ISO 19770-2:2015 SWID specification describes use of the "swid"
and "swidpath" URI schemes, which are currently in use in
implementations.  This document continues this use for CoSWID.  The
following subsections provide registrations for these schemes in to
ensure that a registration exists for these schemes that is suitable
for use in the SWID and CoSWID specifications.  URI schemes are
registered within the "Uniform Resource Identifier (URI) Schemes"
registry maintained at IANA.uri-schemes.
Paragraph (version B):
IANA is requested to register the URI scheme "swid".  This
registration request complies with RFC7595.
Paragraph (version B):
IANA is requested to register the URI scheme "swidpath".  This
registration request complies with RFC7595.
Draft: draft-ietf-sacm-coswid

Commentary: Signed - off - by :
Paragraph (version A):
rel (index 40): An integer or textual value that (integer label
with text escape, see data-def, for the "Software Tag Link
Relationship Values" registry indexed-link-ownership) identifies
the relationship between this CoSWID and the target resource
identified by the "href" item.  If an integer value is used it
MUST be an index value in the range -256 to 65535.  Integer values
in the range -256 to -1 are reserved for testing and use in closed
environments (see iana-private-use).  Integer values in the range
0 to 65535 correspond to registered entries in the IANA "Software
Tag Link Relationship Values" registry (see iana-link-rel.  If a
string value is used it MUST be either a private use name as
defined in iana-private-use or a "Relation Name" from the IANA
"Link Relation Types" registry: https://www.iana.org/assignments/
link-relations/link-relations.xhtml as defined by RFC8288.  When a
string value defined in the IANA "Software Tag Link Relationship
Values" registry matches a Relation Name defined in the IANA "Link
Relation Types" registry, the index value in the IANA "Software
Tag Link Relationship Values" registry MUST be used instead, as
this relationship has a specialized meaning in the context of a
CoSWID tag.  String values correspond to registered entries in the
"Software Tag Link Relationship Values" registry.
Paragraph (version B):
rel (index 40): An integer or textual value that (integer label
with text escape, see data-def, for the "Software ID Link
Relationship Values" registry indexed-link-ownership) identifies
the relationship between this CoSWID and the target resource
identified by the "href" item.  If an integer value is used it
MUST be an index value in the range -256 to 65535.  Integer values
in the range -256 to -1 are reserved for testing and use in closed
environments (see iana-private-use).  Integer values in the range
0 to 65535 correspond to registered entries in the IANA "Software
ID Link Relationship Values" registry (see iana-link-rel.  If a
string value is used it MUST be either a private use name as
defined in iana-private-use or a "Relation Name" from the IANA
"Link Relation Types" registry: https://www.iana.org/assignments/
link-relations/link-relations.xhtml as defined by RFC8288.  When a
string value defined in the IANA "Software ID Link Relationship
Values" registry matches a Relation Name defined in the IANA "Link
Relation Types" registry, the index value in the IANA "Software ID
Link Relationship Values" registry MUST be used instead, as this
relationship has a specialized meaning in the context of a CoSWID
tag.  String values correspond to registered entries in the
"Software ID Link Relationship Values" registry.
Paragraph (version A):
entries in the "Software Tag Link Use Values" registry.
Paragraph (version B):
entries in the "Software ID Link Use Values" registry.
Draft: draft-ietf-sacm-coswid

Commentary: ( might not be literally covered by RFC 8126 ) 
 Approved by AD
Paragraph (version A):
The following registries allow for the registration of index values
and names.  New registrations will be permitted through either the
Standards Action policy or the Specification Required policy BCP26.
New index values will be provided on a First Come First Served as
defined by BCP26.
Paragraph (version B):
The following registries allow for the registration of index values
and names.  New registrations will be permitted through either a
Standards Action with Expert Review policy or a Specification
Required policy BCP26.  New index values will be provided on a First
Come First Served as defined by BCP26.
Draft: draft-ietf-sacm-coswid

Commentary: Additional clarification on registry name 
 Merging due to  's go - ahead .
Paragraph (version A):
The following IANA registries provide a mechanism for new values to
be added over time to common enumerations used by SWID and CoSWID.
Paragraph (version B):
The following IANA registries provide a mechanism for new values to
be added over time to common enumerations used by SWID and CoSWID.
While neither the CoSWID nor SWID specification is subordinate to the
other and will evolve as their respective standards group chooses,
there is value in supporting alignment between the two standards.
Shared use of common code points, as spelled out in these registries,
will facilitate this alignment, hence the intent for shared use of
these registries and the decision to use "swid" (rather than
"coswid") in registry names.
Draft: draft-ietf-sacm-coswid

Commentary: Fixed typo identified by   . Also removed some extra working text that was accidentally left in an IANA section . This PR will be kept open until the WGLC concludes .
Paragraph (version A):
To ensure that UTF-8 character strings are able to be encodes/decoded
and exchanged interoperably, text strings in CoSWID MUST be encoded
consistent with the Net-Unicode definition defined in RFC5198.
Paragraph (version B):
To ensure that UTF-8 character strings are able to be encoded/decoded
and exchanged interoperably, text strings in CoSWID MUST be encoded
consistent with the Net-Unicode definition defined in RFC5198.
Paragraph (version A):
If the supplemental item is set to "true", the tag SHOULD contain
at least one link item with both the rel(ation) item value of
"supplements" and an href item specifying an association with the
software that is supplemented.
Paragraph (version B):
If the supplemental item is set to "true", the tag SHOULD contain
at least one link item with both the rel(ation) item value of
"supplemental" and an href item specifying an association with the
software that is supplemented.
Paragraph (version A):
SWID or CoSWID by the referenced tag's tag-id.  This URI needs to be
resolved in the context of the endpoint by software that can lookup
other SWID or CoSWID tags.  For example, "swid:2df9de35-0aff-
4a86-ace6-f7dddd1ade4c" references the tag with the tag-id value
"2df9de35-0aff-4a86-ace6-f7dddd1ade4c".
Paragraph (version B):
Addressed a bunch of minor editorial issues based on WGLC
feedback.
Paragraph (version B):
Added text about the use of UTF-8 in CoSWID.
Paragraph (version B):
Adjusted tag-id to allow for a UUID to be provided as a bstr.
Paragraph (version B):
Cleaned up descriptions of index ranges throughout the document,
removing discussion of 8 biut, 16 bit, etc.
Paragraph (version B):
Adjusted discussion of private use ranges to use negative integer
values and to be more clear throughout the document.
Paragraph (version B):
Added discussion around resolving overlapping value spaces for
version schemes.
Paragraph (version B):
Added a set of expert review guidelines for new IANA registries
created by this document.
Paragraph (version B):
Added new registrations for the "swid" and "swidpath" URI schemes,
and for using CoSWID with SWIMA.
Draft: draft-ietf-sacm-coswid

Commentary: … and the IANA registry . Also fixed a wierd character encoding issue .
Paragraph (version A):
process-name (index 27): The process name as it will be found in
the endpoints's process table.
Paragraph (version B):
process-name (index 27): The process name as it will be found in
the endpoint's process table.