SPDX full names missing about fsf-api

[goneall]

Conversation copied from original issue:

From @goneall

@davidhedlund Suggest you get the full names of the SPDX licenses from the SPDX JSON file. You can correlate with this JSON file using the SPDX ID's. I realize this is a bit more work programmatically, but the SPDX JSON file is generated from the license-XML and will be more maintained than the fsf-api utility.

From @davidhedlund

Thank you very much. I noticed that you are a contributor to this repository. How much time would it take for you to implement this in the FSF-API tool? It is needed to finish our license list in the Free Software Directory (FSF project).

From @goneall

Since my PR's haven't been merged for over 2 years, I made a fork of this repo at https://github.com/spdx/fsf-api and with the help of other contributors have made several improvements. I'm very interested in the FSF project mentioned above. Let's continue the conversation in the spdx/fsf-api issues.

From @davidhedlund

Sounds promising. Can you please submit this issue there and give me the link?

[goneall]

@davidhedlund Just copied the issue over.

How much time would it take for you to implement this in the FSF-API tool? It is needed to finish our license list in the Free Software Directory (FSF project).

This would create a somewhat circular dependency between the data. The SPDX license list uses data from this project to generate the license-list-data repo which contains the names.

In my opinion, it would be more logical to merge the names (and any other SPDX specific data) from the license-list-data generated JSON file(s) which are available in the github repo or on the spdx.org/licenses website. My suggestion would be to use the latter as it would always be reviewed and released rather than interim data.

[davidhedlund]

@davidhedlund Just copied the issue over.

Thanks again. I'm very happy that you suggested this.

How much time would it take for you to implement this in the FSF-API tool? It is needed to finish our license list in the Free Software Directory (FSF project).

This would create a somewhat circular dependency between the data. The SPDX license list uses data from this project to generate the license-list-data repo which contains the names.

In my opinion, it would be more logical to merge the names (and any other SPDX specific data) from the license-list-data generated JSON file(s) which are available in the github repo or on the spdx.org/licenses website. My suggestion would be to use the latter as it would always be reviewed and released rather than interim data.

I agree.

I added https://github.com/spdx/fsf-api/issues to https://directory.fsf.org/wiki/Free_Software_Directory:SPDX_Group#Issues