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

Display attribution in footer #46

Open
Stephen-Gates opened this issue Nov 9, 2017 · 2 comments
Open

Display attribution in footer #46

Stephen-Gates opened this issue Nov 9, 2017 · 2 comments

Comments

@Stephen-Gates
Copy link

Stephen-Gates commented Nov 9, 2017

As a data reuser, I want to provide attribution, so that I comply with licence requirements

Optionally display an attribution link at the bottom of the table using best practices.

This should be able to generated from the datapackage.json

e.g.

<a href="resource.url">resource.name-or-title</a> 
by <a href="resource.sources.url">resource.sources.name</a> 
is licensed under <a href="resource.licenses.url">license.name</a>

You would need to cater for:

  • resources can inherit metadata properties from a data-package
  • arrays of values
@rufuspollock
Copy link
Contributor

Ditto comment here to #45 - i think this is definitely something to do but it should be up to app that is using this library to add that in. for example, we may do this differently on https://datahub.io/ than others would do it.

Not absolutely certain though - so happy to have pushback 😄

@Stephen-Gates
Copy link
Author

I guess I saw this feature as an easy way to help people comply with their licence obligations. As the display of attribution would be optional, the app using the library is able to address attribution in other ways.

In general, I'm regularly deliberating over just complying with Frictionless Data vs promoting good practices through software constraints. E.g. In other software, I won't let someone export a data package unless the data has been validated successfully against the schema. I.e. prevent people doing the "wrong thing" / make it easy to do the right thing.

I feel firmer about this issue than #45 (which can be closed or put on the backlog).

@zelima zelima added this to the Backlog milestone Jul 19, 2018
@roll roll removed this from the Backlog milestone Jun 11, 2019
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

No branches or pull requests

4 participants