Steve Winslow

Hi all, I have a wrapper framework around existing Fossology (3.6.0) that I use for project scanning, to try to accomplish something along these lines. The code is at https://github.com/swinslow/scaffold...

@NicolasToussaint agreed -- if Fossology had a concept of "projects", I expect it would be very helpful. I've found it particularly useful to be able to combine pulls from multiple...

cc'ing @jlovejoy who may have input and historical knowledge here also! For question 1, my view is that yes, `NONE` and `NOASSERTION` should imply list size is 1. They should...

@kestewart Given the definitions in 2.2 as the spec currently exists, I don't think that NOASSERTION is intended to be used in this way. A LicenseRef can always be used...

Hi @oddhack, there are a couple of things you'll want to look at relating to this. At the top of the [SPDX License List main page](https://spdx.org/licenses/), one of the bullet...

One additional comment -- if you are looking to add SPDX-License-Identifier tags to your own project, the [REUSE Software specification](https://reuse.software/spec/) from FSFE has some recommendations on how to represent this,...

Ah -- so if I follow, it sounds like an `"annotations"` object can appear nested within any SPDX element -- Document, Package, File or Snippet. So the [example JSON file](https://github.com/spdx/spdx-spec/blob/development/v2.2.1/examples/SPDXJSONExample-v2.2.spdx.json)...

@goneall I guess this raises the question -- does this work if someone wants to provide an Annotation for an element that is defined in a separate SPDX Document? For...

@goneall Interesting... yes, in the Golang tools it makes a distinction between two different data types for handling SPDX Identifiers: - [`ElementID`](https://github.com/spdx/tools-golang/blob/8574b91809e949442fa0cbf3174d9ae83cd69f60/spdx/identifier.go#L9), which is just a string; or - [`DocElementID`](https://github.com/spdx/tools-golang/blob/8574b91809e949442fa0cbf3174d9ae83cd69f60/spdx/identifier.go#L11-L29),...

> @swinslow @tsteenbe @SamuraiAku Should we queue this for 3.0 or make the change sooner? One question -- is this an issue for RDF also, or just for JSON? I'm...