Original text:
UTF-8 RFC3629" (see RFC7049 section 2.1).  Thus both SWID and CoSWID use UTF-8 for the encoding of characters in text strings. <del> To ensure that UTF-8 character strings are able to be encodes/decoded </del>  and exchanged interoperably, text strings in CoSWID MUST be encoded consistent with the Net-Unicode definition defined in RFC5198. 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 <del> "supplements" and an href item specifying an association with the </del>  software that is supplemented. If all of the corpus, patch, and supplemental items are "false", 5.6.1. <del> 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". </del> There is a need for a scheme name that can be used in URIs that point to a specific SWID/CoSWID tag by that tag's tag-id, such as the use of the link entry as described in section model-link) of this [THIS SECTION TO BE REMOVED BY THE RFC EDITOR.]  Changes from version 03 to version 11: Reduced representation complexity of the media-entry type and

Reviewer comments:
Fixed typo identified by Alex Nelson. Also removed some extra working text that was accidentally left in an IANA section. This PR will be kept open until the WGLC concludes.

Revised text:
UTF-8 RFC3629" (see RFC7049 section 2.1).  Thus both SWID and CoSWID use UTF-8 for the encoding of characters in text strings.  <ins> To ensure that UTF-8 character strings are able to be encoded/decoded </ins> and exchanged interoperably, text strings in CoSWID MUST be encoded consistent with the Net-Unicode definition defined in RFC5198. 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  <ins> "supplemental" and an href item specifying an association with the </ins> software that is supplemented. If all of the corpus, patch, and supplemental items are "false", 5.6.1.  There is a need for a scheme name that can be used in URIs that point to a specific SWID/CoSWID tag by that tag's tag-id, such as the use of the link entry as described in section model-link) of this [THIS SECTION TO BE REMOVED BY THE RFC EDITOR.] <ins> Changes in version 12: Addressed a bunch of minor editorial issues based on WGLC feedback. Added text about the use of UTF-8 in CoSWID. Adjusted tag-id to allow for a UUID to be provided as a bstr. Cleaned up descriptions of index ranges throughout the document, removing discussion of 8 biut, 16 bit, etc. Adjusted discussion of private use ranges to use negative integer values and to be more clear throughout the document. Added discussion around resolving overlapping value spaces for version schemes. Added a set of expert review guidelines for new IANA registries created by this document. Added new registrations for the "swid" and "swidpath" URI schemes, and for using CoSWID with SWIMA. </ins> Changes from version 03 to version 11: Reduced representation complexity of the media-entry type and