One of the semi-surprising topics we discussed today was the existence of Collection elements that are meaningful at the logical level without considering serialization. That makes the "Document name" discussion much easier!
- The traditional understanding of "document" = "file" is accommodated by using Document as the element type that describes a file containing elements. - The knowledge-graph understanding of "collection" as a set/bag of logical/unserialized elements is accommodated by NOT calling that element "Document". Call it "Bundle" for now as a placeholder. With that understanding, BOM/SBOM MUST NOT extend Document. They are the collection of elements that make up a BOM without regard to serialization. I *think* BOM must be a set because I can't think of any reason for a BOM listing an element more than once should be treated as semantically different from a BOM listing that element only once. If there is a use case for them to be semantically different, then bag would be the correct type. Document is a different type than the box shown in the model - it is metadata about a file with the collection of elements that are serialized in that file. It doesn't matter whether it extends Artifact and has an element property, or extends Collection and has an artifact property. That Document type must exist in order for externalMap in one file to reference elements serialized in a different file. Regards, Dave > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#4653): https://lists.spdx.org/g/Spdx-tech/message/4653 Mute This Topic: https://lists.spdx.org/mt/92327773/21656 Group Owner: [email protected] Unsubscribe: https://lists.spdx.org/g/Spdx-tech/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
