Skip to content
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

Update the license fields according to frictionless specifications #127

Closed
1 task done
Ludee opened this issue May 2, 2023 · 1 comment · Fixed by #162
Closed
1 task done

Update the license fields according to frictionless specifications #127

Ludee opened this issue May 2, 2023 · 1 comment · Fixed by #162
Assignees
Labels
documentation Improvements or additions to documentation enhancement New feature or request help wanted Extra attention is needed

Comments

@Ludee
Copy link
Member

Ludee commented May 2, 2023

Description of the issue

Latest version has two additional (custom) fields for the license: attribution and instruction.
They are very useful but not conform with frictionless.

The documentation has specific keys for this:

"licenses" : [{
    "name": "CC-BY-4.0",
    "path": "https://creativecommons.org/licenses/by/4.0/",
    "title": "Creative Commons Attribution 4.0"
  }],
  "copyrightNotice": "© The State of Queensland 1995–2017",
  "copyrightStatement": "https://www.qld.gov.au/legal/copyright",
  "attributionText": "Science, Information Technology and Innovation, Queensland Government, Coastal Data System – Near real time wave data, licensed under Creative Commons Attribution 4.0 sourced on 26 December 2017",

Source: https://frictionlessdata.io/blog/2018/03/27/applying-licenses/#provide-additional-license-information

Ideas of solution

  • Rename key attribution to copyrightNotice
  • Add terms copyrightStatement to a link that proves the data is licensed

Discuss:

  • attributionText is not conform with TASL. Would be a copy of other keys depending on the licenses.
  • instruction is a nice-to-have feature that briefly states the rights and obligation. Do we keep it?

Workflow checklist

@Ludee Ludee added documentation Improvements or additions to documentation enhancement New feature or request help wanted Extra attention is needed labels May 2, 2023
@Ludee Ludee self-assigned this May 2, 2023
@jh-RLI
Copy link
Contributor

jh-RLI commented May 11, 2023

As far as I understand, we don't have to use the exact naming from the frictionless example. They used, this specific names as they are proposed by this guide of the open data institute.

In general, we could also keep our naming, as these fields are additional fields that are not part of the frictionless specification.

Ludee added a commit that referenced this issue Oct 15, 2024
Ludee added a commit that referenced this issue Oct 15, 2024
jh-RLI added a commit that referenced this issue Oct 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation enhancement New feature or request help wanted Extra attention is needed
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants