Change:
5. <del> This specification defines the following URI schemes for use in </del> <ins> This specification defines the following expressions for use in </ins> CoSWID and to provide interoperability with schemes used in SWID. <del> Note: These URI schemes are used in SWID without an IANA registration.  The present specification ensures that these URI schemes are properly defined going forward. </del> <ins> 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. </ins> 5.1. <del> There is a need for a scheme name that can be used in URIs that point to a specific software tag by that tag's tag-id, such as the use of the link entry as described in model-link.  Since this scheme is used both in a standards track document and an ISO standard, this scheme needs to be used without fear of conflicts with current or future actual schemes.  In swid-reg, the scheme "swid" is registered as a 'permanent' scheme for that purpose. URIs specifying the "swid" scheme are used to reference a software tag by its tag-id.  A tag-id referenced in this way can be used to identify the tag resource in the context of where it is referenced from.  For example, when a tag is installed on a given device, that tag can reference related tags on the same device using URIs with this scheme. </del> <ins> Expressions specifying the "swid" scheme are used to reference a software tag by its tag-id.  A tag-id referenced in this way can be used to identify the tag resource in the context of where it is referenced from.  For example, when a tag is installed on a given device, that tag can reference related tags on the same device using expressions with this scheme. </ins> <del> For URIs that use the "swid" scheme, the scheme specific part MUST consist of a referenced software tag's tag-id.  This tag-id MUST be URI encoded according to RFC3986. </del> <ins> For expressions that use the "swid" scheme, the scheme specific part MUST consist of a referenced software tag's tag-id.  This tag-id MUST be URI encoded according to RFC3986 Section 2.1. </ins> The following expression is a valid example: 5.2. <del> There is a need for a scheme name that can be used in URIs to identify a collection of specific software tags with data elements that match an XPath expression, such as the use of the link entry as described in model-link.  The scheme named "swidpath" is used for this purpose in SWID, but not registered.  To enable usage without fear of conflicts with current or future actual schemes, the present document registers it as a 'permanent' scheme for that purpose (see swidpath-reg). URIs specifying the "swidpath" scheme are used to filter tags out of a base collection, so that matching tags are included in the </del> <ins> Expressions specifying the "swidpath" scheme are used to filter tags out of a base collection, so that matching tags are included in the </ins> identified tag collection.  The XPath expression W3C.REC- xpath20-20101214 references the data that must be found in a given software tag out of base collection for that tag to be considered a matching tag.  Tags to be evaluated (the base collection) include all <del> tags in the context of where the "swidpath URI" is referenced from. For example, when a tag is installed on a given device, that tag can reference related tags on the same device using a URI with this scheme. </del> <ins> tags in the context of where the swidpath expression is referenced from.  For example, when a tag is installed on a given device, that tag can reference related tags on the same device using an expression with this scheme. </ins> For URIs that use the "swidpath" scheme, the following requirements apply:

Discussion:
Removed IANA registrations for swid and swidpath and updated text to note these are not technically URIs but just expressions using URI syntax.