Skip to content

Conversation

kovalch
Copy link
Contributor

@kovalch kovalch commented Jul 29, 2024

1 - parsing of the dataset:
License output of opendata.swiss should only be our 4 terms of use with the corresponding URIs https://www.dcat-ap.ch/vocabulary/licenses/20210623.html

Via ckan dataset API we see licence URIs, example:
instead of
"license": "NonCommercialAllowed-CommercialAllowed-ReferenceNotRequired",
we show
"license": "https://opendata.swiss/terms-of-use#terms_open"

instead of
"rights": "Creative Commons Namensnennung - Weitergabe unter gleichen Bedingungen (CC-BY-SA)",
we show
"rights": "http://www.opendefinition.org/licenses/cc-by-sa

In case we do not have License we check if rights is there and if it one of 4 terms we take it from rights.

2- dataset to graph:

we export licences and rights in a way:
<dct:license rdf:resource="http://dcat-ap.ch/vocabulary/licenses/terms_open"/>
<dct:rights rdf:resource="https://creativecommons.org/licenses/by-sa/4.0"/>

3- if rights are not in our vocabulary https://www.dcat-ap.ch/vocabulary/licenses/20210623.html
we do not show it

@bellisk
Copy link
Contributor

bellisk commented Jul 30, 2024

Via ckan dataset API we see licence URIs, example:
instead of
"license": "NonCommercialAllowed-CommercialAllowed-ReferenceNotRequired",
we show
"license": "https://opendata.swiss/terms-of-use#terms_open"

Shouldn't the URI here be http://dcat-ap.ch/vocabulary/licenses/terms_open ?

@bellisk
Copy link
Contributor

bellisk commented Jul 31, 2024

I have a couple more questions just to check I understood everything.

In our license vocabulary, each license has a URI, a description, a code, and a link to the license text - that link to the license text is what we're calling homepage_uri, right?

  • Is there another PR to change the output of the CKAN API so that the license and rights values for existing resources are URIs instead of the license names as they are currently? Or to migrate the existing data?
  • Why are we using the homepage uri for this instead of the license URI?
  • Is there another PR to change the display of the licenses on the frontend? Currently the frontend expects the opendata.swiss license names (e.g. NonCommercialAllowed-CommercialAllowed-ReferenceNotRequired) and maps those to the icons for the different licences.
  • On the CKAN dataset pages, we display the licenses with these names, and on the CKAN resource pages, we display the licenses yet another way, as text, e.g. Non-commercial Allowed / Commercial Allowed / Reference Not Required. Will we keep these like so or will we display the homepage uris here, the same as in the API?

(Sorry for the late addition of this comment - I was typing it up when I had to restart my laptop yesterday.)

@bellisk
Copy link
Contributor

bellisk commented Jul 31, 2024

I have another question - maybe this is a misunderstanding on my part. For the Creative Commons licenses, with the updates here and here, I noticed that the homepage urls for each license are on the Open Definition site, e.g. http://opendefinition.org/licenses/cc-by-sa/. Why are we using those urls and not the respective Creative Commons urls where the licenses are actually defined, e.g. http://creativecommons.org/licenses/by-sa/4.0/?

@bellisk bellisk merged commit c13a28c into master Aug 8, 2024
@bellisk bellisk deleted the fix_licenses_uri branch August 8, 2024 13:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants