Optional
acknowledgement?: LicenseAcknowledgementEnumerationOptional
bomRef?: stringAn optional identifier which can be used to reference the license elsewhere in the BOM. Uniqueness is enforced within all elements and children of the root-level bom element.
Optional
licensing?: LicensingLicensing details describing the licensor/licensee, license type, renewal and expiration dates, and other important metadata
Specifies optional, custom, properties
Optional
text?: AttachedTextSpecifies the optional full text of the attachment
Optional
url?: stringThe URL to the attachment file. If the attachment is a license or BOM, an externalReference should also be specified for completeness.
Declared licenses and concluded licenses represent two different stages in the licensing process within software development. Declared licenses refer to the initial intention of the software authors regarding the licensing terms under which their code is released. On the other hand, concluded licenses are the result of a comprehensive analysis of the project's codebase to identify and confirm the actual licenses of the components used, which may differ from the initially declared licenses. While declared licenses provide an upfront indication of the licensing intentions, concluded licenses offer a more thorough understanding of the actual licensing within a project, facilitating proper compliance and risk management. Observed licenses are defined in
@.evidence.licenses
. Observed licenses form the evidence necessary to substantiate a concluded license.