Minutes Line 62: * Proposal: Extensions field will be encapsulated in Profile and removed from Core Model type.
Discussion: The goal of extensions is to easily identify non-standardized content by inspection. The current "extensions Map(URI, any)" clearly labels extensions but has the flavor of serialization rather than logical model (minutes line 59). It also follows the (undesirable IMO) practice of shoving everything up into Element rather than down into the types where they apply. New Proposal * remove "extension" property from Element * define "Extension" abstract class in Core with an "extensionId URI" property. * non-standard profiles extend only the Extension class This segregates extension types from standard types like Gary's hack of extending Annotation to support CycloneDX information. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#4776): https://lists.spdx.org/g/Spdx-tech/message/4776 Mute This Topic: https://lists.spdx.org/mt/93524612/21656 Group Owner: [email protected] Unsubscribe: https://lists.spdx.org/g/Spdx-tech/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
