This would depend on the serialization format, for example, JSON-LD, XML-Schema have a native way of communicating an object’s type. For formats that don’t have that the type would need to be communicated implicitly via convention and/or specification or explicitly via a property on the object that specifies its type.
Get Outlook for iOS<https://aka.ms/o0ukef> ________________________________ From: [email protected] <[email protected]> on behalf of David Kemp <[email protected]> Sent: Tuesday, July 27, 2021 12:11:56 PM To: Sean Barnum <[email protected]> Cc: SPDX-list <[email protected]> Subject: Re: [EXT] Re: [spdx-tech] Document Describes My question was that in 2.2 every Element is known to be one of Document, Package, File, Snippet, OtherLicensingInfo, Relationship, or Annotation, because elements come only from Documents, and Documents have exactly those 7 sections. If we have Elements that don't come from Documents, plus for those that do, Documents don't have sections, then there must be a list of 7 or 10 or whatever possible kinds of Element. Concrete elements are instantiated, Abstract elements are not. Given that you have an Element in your hand, and given that it does not have a Section name, what do you use to figure out what kind of element it is? Dave On Tue, Jul 27, 2021 at 11:24 AM Sean Barnum <[email protected]<mailto:[email protected]>> wrote: I am not sure if I am reading your comment correctly. If you are suggesting that ContextualCollection and BOM should be abstract then I would disagree as there are use cases for these independent of SBOM and they need to be concrete so that such elements can be expressed. sean -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#4130): https://lists.spdx.org/g/Spdx-tech/message/4130 Mute This Topic: https://lists.spdx.org/mt/84484291/21656 Group Owner: [email protected] Unsubscribe: https://lists.spdx.org/g/Spdx-tech/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
