Use the universally known license code instead of the SPDX-specific.

OpenEnergyPlatform / oeplatform

Repository for the code of the Open Energy Platform (OEP) website. The OEP provides an interface to the Open Energy Family

http://openenergyplatform.org/

GNU Affero General Public License v3.0

61 stars 19 forks source link

Use the universally known license code instead of the SPDX-specific. #1651

Open jh-RLI opened 1 month ago

jh-RLI commented 1 month ago

Description of the issue

We want to harmonise the licences used when they are added to the oemetdata. To archive this, we will implement an autoselect function in our metabuilder tool (create/edit oemeta data) that will help to select licences and provide the corresponding metadata.

This is also relevant for the automatic licence check, which compares the licence identifier with the list of SPDX identifiers.

Ideas of solution

Use a list of universally known licence identifiers
Retrieve all relevant licence metadata

Workflow checklist

[ ] I am aware of the workflow in CONTRIBUTING.md

jh-RLI commented 1 month ago

As suggested by @holycrab13 we could use DALICC. The databus also uses it https://dbpedia.gitbook.io/databus/model/metadata/version#id-2.-legal-provenance-and-attribution

jh-RLI commented 1 month ago

https://api.dalicc.net/docs#/licenselibrary/get_license_by_id_licenselibrary_license__license_id__get

jh-RLI commented 1 month ago

In this article you will find further suggestions and insights:

https://forum.openmod.org/t/public-licensing-ontologies/2756

It states that some information found in DALICC may not be correct - not sure if this is relevant.

It also points to a ontology for SPDX licenses: https://forum.openmod.org/t/public-licensing-ontologies/2756#spdx-ontology-of-open-source-software-licenses-20