CoSWID triple needs transformation and processing sections

[nedmsmith]

CoSWID triples coswid-triple-record needs a transformation section and possibly a processing section. The transformation section will map contents of a coswid tag to internal representations for evidence, reference, and endorsements. If the mapping comes up with gaps (something that doesn't map) then a processing section may be needed.

CoSWID field mappings are as follows:
payload-entry : Reference Values
evidence-entry : Evidence
software-meta.activation-status : Evidence? (if so, how should it be reported since concise-evidence omits it)
channel-type : Endorsement
colloquial-version : Endorsement
description : Endorsement
edition : Endorsement
entitlement-data-required : ??? (feels like policy)
entitlement-key : Endorsement
generator : tag info
persistent-id : Should be used in the construction of Environment-maps
product : Endorsement
product-family : Endorsement
revision : Endorsement
summary : Endorsement
unspsc-code : Endorsement
unspsc-version : Endorsement

Extension to sw meta should describe their internal representation mapping / transformation.

Concise Swid Tag:
software-name : Endorsement
software-version : Endorsement
version-scheme : Endorsement
media : Endorsement (for example, it may contain a stringified representation of environment-map)

All other members of concise-swid-tag are tag specific.

[deeglaze]

What form of evidence is expected for communicating software information in a module at the granularity of CoSWIDs? Is there a real usage of this triple that the spec can reference to point a reader at something plausible?