Gary O'Neall

> > > Thank you [@goneall](https://github.com/goneall). I believe the "derived from" relationship could be appropriate for scenario 2 — file to package. However, this relationship is not currently included in...

I agree with the points above, however, just note that some of the tools that read the SHACL file _may_ rely on these constructs and _may_ need to be updated...

@JPEWdev - I know we have explicitly allowed CreationInfo - do we now also allow other non-Element nodes?

> Btw, we have two places documenting serialization to JSON-LD. I wonder if we should consolidate all the serialization information into the spec and remove the serialization folder from this...

@VladimirAlexiev - Thanks for the review and all the suggestions. The descriptions referenced above are defined in the markdown files in the model directory. It would be very helpful to...

@swinslow Just a reminder - once this is updated to the new structure consistent with https://github.com/spdx/LicenseListPublisher/pull/216, I can merge in the changes to to the publisher.

Couple specific package manager uses: - Node Package Manager (NPM - [reference](https://docs.npmjs.com/cli/v8/configuring-npm/package-json#license)) - Python package managers([reference](https://packaging.python.org/en/latest/specifications/license-expression/)).

Another use case you can add is the license matching guidelines for determining if 2 different blocks of texts represents the same license.

I think specializing to a type is fine - agree that these should not be breaking changes - even the additional restrictions in the second table is OK IMHO. I...

@jlovejoy - Just saw it now @xsuchy - I would prefer to keep the simpleTestForGenerator directory since I would need to change some of my release workflows for the LicenseListPublisher....