spdx / spdx/Spdx-Java-Library

Should license information be available for NONE and NOASSERTION ?

Open
#398 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

question
Dominant language
Java
Stars
71
Forks
44
Avg merge
12h 54m
Merged PRs (30d)
7

Description

In SPDX 3.0.2, the IndividualLicensingInfo values NONE and NOASSERTION are becoming closer to behaving like any other license id, but currently the following code does not return any results:

org.spdx.library.ListedLicenses.getListedLicenses().getListedLicenseById("NONE");
org.spdx.library.ListedLicenses.getListedLicenses().getListedLicenseById("NOASSERTION");

The question is: should it be possible to get the metadata (name, description, etc.) for these "identifiers", and if so how? They're not listed licenses, so perhaps they should be looked up via different methods and/or classes, for example?

Note: I have no specific need for this functionality myself; it was just something I noticed in passing, as I worked on implementing some of the changes in SPDX v3.0.2.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading org.spdx.library.ListedLicenses and its getListedLicenseById method, then compare the SPDX 3.0.2 IndividualLicensingInfo definition for NONE and NOASSERTION. Done means establishing whether these identifiers should expose metadata and identifying the appropriate API or class, with behavior covered by tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
devtools
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.