Addressing IESG evaluation feedback

draft-ietf-sacm-coswid.md

@@ -1005,10 +1005,10 @@ The following table contains a set of values for use in the concise-swid-tag gro
 
 The values above are registered in the IANA "Software Tag Version Scheme Values" registry defined in Section {{iana-version-scheme}}. Additional entries will likely be registered over time in this registry.
 
-These version schemes have partially overlapping value spaces. The following guidelines help to ensure that the most specific version-scheme is used:
+These version schemes have partially overlapping value spaces. A CoSWID producer that is aware of the version scheme behind the version value, it SHOULD include the optional version-scheme item to avoid semantic ambiguity. If the CoSWID producer does not have this information it, SHOULD omit the version-scheme item. The following heuristics can be used by a CoSWID consumer:
 
 - "decimal" and "multipartnumeric" partially overlap in their value space when a value matches a decimal number. When a corresponding software-version item's value falls within this overlapping value space, the "decimal" version scheme SHOULD be used.
-- "multipartnumeric" and "semver" partially overlap in their value space when a "multipartnumeric" value matches the semantic versioning syntax. When a corresponding software-version item's value falls within this overlapping value space, the "semver" version scheme SHOULD be used.
+- "multipartnumeric" and "semver" partially overlap in their value space when a "multipartnumeric" value matches the semantic versioning syntax. When a corresponding software-version item's value falls within this overlapping value space, the "semver" version scheme SHOULD be assumed.
 - "alphanumeric" and other version schemes might overlap in their value space. When a corresponding software-version item's value falls within this overlapping value space, the other version scheme SHOULD be used instead of "alphanumeric".
 
 {: #indexed-entity-role}