pull: Add deprecated SPDX identifiers #14
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
These identifiers are deprecated, but they haven't yet been dropped from the SPDX spec. That means that, although they're not recommended, they're still valid identifiers to use where you can use other License List 3.0 identifiers. Listing them here makes it easy for folks using the deprecated identifiers to look up the associated FSF metadata. An alternative approach would be to stick with only non-deprecated SPDX identifiers here and have users hit the SPDX API to resolve those before coming to this API. But the SPDX API does not currently expose obsoletedBy migration recommendations [1]. [1]: spdx/LicenseListPublisher#12
goneall
approved these changes
Apr 15, 2018
|
Agree with adding the deprecated ID's as a solution. We can pick these up on the next update of the license list data. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
These identifiers are deprecated, but they haven't yet been dropped from the SPDX spec. That means that, although they're not recommended, they're still valid identifiers to use where you can use other License List 3.0 identifiers. Listing them here makes it easy for folks using the deprecated identifiers to look up the associated FSF metadata.
An alternative approach would be to stick with only non-deprecated SPDX identifiers here and have users hit the SPDX API to resolve those before coming to this API. But the SPDX API does not currently expose
obsoletedBymigration recommendations (spdx/LicenseListPublisher#12).CC @goneall.