From 4d3c0c11c05b138749f8e101921594f5210aafac Mon Sep 17 00:00:00 2001 From: Marc-Etienne Vargenau Date: Fri, 28 Aug 2026 19:33:27 +0200 Subject: [PATCH] Remove extra spaces in SPDX license id Signed-off-by: Marc-Etienne Vargenau --- docs/AutomotiveSBOM_Specification.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/AutomotiveSBOM_Specification.md b/docs/AutomotiveSBOM_Specification.md index 5d9b5db..03594ae 100644 --- a/docs/AutomotiveSBOM_Specification.md +++ b/docs/AutomotiveSBOM_Specification.md @@ -263,9 +263,9 @@ Specific examples - Case 3 : The SBOM creator changes the license declared by the component creator For example, the OSS component you acquired is dual-licensed (GPL-2.0-only and a commercial license), and you provide software containing that OSS component to a third party, and that party uses the target software as GPL-2.0-only software, you must state this in the SBOM. - In this example, the license expression would be as follows: - - Declared License " GPL-2.0-only or commercial license", - - Concluded License " GPL -2.0 - only" + In this example, the license expression would be as follows: + - Declared License "GPL-2.0-only or commercial license", + - Concluded License "GPL-2.0-only" ### 3.2.3. Checking for Consistency with Existing Industry Standards The results of the consistency check against the definitions of data fields in existing industry standards are shown in Table 2.