Gary O'Neall

Actually - it probably makes sense to just go ahead and merge in case there is a dot release - merging

Agree with @pmonks - ABNF should be the "source of truth" for the license expression. @kestewart - thoughts?

The online tools are still using the Java implementation - so the validation may be different. From a quick check, I don't think the verify method in the Java implementation...

@ssbarnea The JSON files are published to https://spdx.org. A summary list of all licenses can be found at [https://spdx.org/licenses/licenses.json](https://spdx.org/licenses/licenses.json). Details for an individual license can be found at https://[license-id].json where...

@ShubhankarVN I believe the syntax allows for `NONE` and `NOASSERTION` without the preceeding `DocumentRef-`. So the following should work: ``` { "spdxElementId": "SPDXRef-Package-1", "relatedSpdxElement": "NOASSERTION", "relationshipType": "DESCRIBED_BY" } { "spdxElementId":...

> What can be done in this scenario? The spec currently doesn't support referring to an unknown SPDX ID within an external document. What I would suggest is creating a...

Are these due to some kind of encoding issue? These are copied from the [test license text](https://github.com/spdx/license-list-XML/tree/main/test/simpleTestForGenerator) which are typically copy/pasted from the original license. @jamin-aws-ospo Can you check of...

> I'd be happy to check them, but I'm not sure what source(s) you consider to be the original. I would just look at the files in this test file...

Thanks @jamin-aws-ospo for the analysis. It looks like this is an issue with the source of the text files. If we want to clean these up, we can just do...

> I believe the text files should be cleaned/purged of non-printing characters. I also believe that (like myself) others will use the text files as direct inputs/reference for other license...