I'm bothered by the same question that's bothering Kate. We discussed: 1) a collection of elements under a single namespace is a "Document" 2) the elements don't have to be related, they could be a bunch of identities 3) the document lists zero or more root elements 4) the document contains zero or more relationship elements (from_id : type : to_id) 5) properties have types, i.e. both structured "relations" and simple "attributes":
*OWL object properties data properties* E-R relations attributes OOP range is class range is datatype Since we can no longer say that a Document is a single SBOM that describes some target of analysis, how do we signal that a Document contains zero, one, or more SBOMs? (Document is no longer a synonym for SBOM, it is now a synonym for "bundle of stuff that can be serialized". If we are going to deprecate the "id_x DESCRIBES id_y" relationship element, we're going to need a way of designating that a root element in a bundle is an SBOM. Without having concrete serializations to play with, it's not obvious that root element X traces down to Artifact -> ContextualCollection -> BOM -> (and finally arriving at) SBOM. I think we need a way of defining the "content type" of each root element without using relationship elements, but we haven't yet documented how to do it. Dave -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#4109): https://lists.spdx.org/g/Spdx-tech/message/4109 Mute This Topic: https://lists.spdx.org/mt/84386487/21656 Group Owner: [email protected] Unsubscribe: https://lists.spdx.org/g/Spdx-tech/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
