Skip to content

Remove extra spaces in SPDX license id #73

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
vargenau wants to merge 1 commit into
base: develop
Choose a base branch
from
Open

Remove extra spaces in SPDX license id #73

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions docs/AutomotiveSBOM_Specification.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down