-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Expose obsoletedBy #12
Comments
4 tasks
wking
added a commit
to wking/fsf-api
that referenced
this issue
Apr 13, 2018
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
I'm waiting for the SPDX spec to include license metadata before proposing this change. See: spdx/spdx-spec#46 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Show the data from spdx/license-list-XML#392 to folks consuming our JSON, HTML, etc.
The text was updated successfully, but these errors were encountered: