Gary O'Neall
Gary O'Neall
> I don't think we want to encourage this use case ;) Good point and I agree. I think the ideal situation is they provide both so that we could...
@davidhedlund Thanks for the feedback on the fields. I think I'll queue this up for discussion on the legal and tech teams for inclusion in the spec if there are...
> Any chance of me handing that over so the FSF can provide its own API? I agree with @wking that this would be a valuable approach. Ideally, the FSF...
Add `obsoletedBys` per request https://github.com/spdx/LicenseListPublisher/issues/12
I recall in the 2.0 spec discussions we decided to add relationships for both directions. The reasoning behind this was if the right side of a relationship was in a...
I thought we added the [SnippetFromFileSPDXID](https://github.com/spdx/spdx-spec/blob/development/v2.2.2/chapters/snippet-information.md#92-snippet-from-file-spdx-identifier-field-) to loosen the requirement for the snippet to follow the file. That being said, the field was added a very long time ago and...
> In my opinion, while it is important for these tools to provide a reference implementation for WRITING the various file types with perfect adherence to the spec, these tools...
One possible short term solution would be to use the Annotation property for the Document with an Annotation Type "OTHER" and a comment field that includes the filename (e.g. `FileLocation:...
When I do audits, I typically use the `AND` operator as suggested by @mlinksva for the [package concluded license](https://spdx.org/spdx-specification-21-web-version#h.ihv636) and whatever is declared at the package level for the [package...
@fulldecent Are you using a full SPDX document to describe the licenses or are you trying to express these conditions as a single file license? If the former, you can...