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

Why rights and not license? #231

Open
peterdesmet opened this issue Feb 11, 2022 · 5 comments
Open

Why rights and not license? #231

peterdesmet opened this issue Feb 11, 2022 · 5 comments
Labels
next meeting agenda Issues to be discussed at next MG meeting term proposal

Comments

@peterdesmet
Copy link
Member

I notice the rights term is used in AC rather than its subproperty license (which is used in Darwin Core): https://www.dublincore.org/specifications/dublin-core/dcmi-terms/#http://purl.org/dc/terms/license

A legal document giving official permission to do something with the resource.

Recommended practice is to identify the license document with a URI. If this is not possible or feasible, a literal value that identifies the license may be provided.

Wouldn't the license property more useful to end users?

@edwbaker
Copy link
Member

I would think so (but I don't know the background), there is also xmpRights:WebStatement in AC. I'll add it to the list of things to discuss in the next meeting.

@edwbaker edwbaker added the next meeting agenda Issues to be discussed at next MG meeting label Feb 11, 2022
@edwbaker edwbaker added future-meeting and removed next meeting agenda Issues to be discussed at next MG meeting labels Feb 21, 2024
@edwbaker edwbaker added next meeting agenda Issues to be discussed at next MG meeting and removed future-meeting labels May 16, 2024
@magpiedin
Copy link
Contributor

Including license makes sense to me, too

I think it would also help to keep rights, though -- with clarification about usage to distinguish it from license & follow the Dublin Core recommendations for http://purl.org/dc/terms/rights -- e.g.:

  • recommend rights term to indicate where media has a particular copyright status using for RightsStatements.org. This could help describe a lot of historical orphan media where rights are unknown but it's otherwise ok or necessary to share.
  • potentially also recommend it for TK (provenance) labels to indicate related cultural authority/rights-types for a given media resource. Or is another term more appropriate for that?
  • point data-publishers towards the license term to indicate Creative Commons or other licenses.

FMNH in Chicago may have one of the first two situations in the future, and we often bump into confusion about the third.

@edwbaker
Copy link
Member

At the Maintenence Group meeting on 22/08/2024 it was decided to work through this and related issues by developing some 'recipes for using rights' in the document here: https://docs.google.com/document/d/1Nv0rNWioJIX-DJRxQExmd22BmaU48qdRYQSzRzdyMQU/edit?usp=sharing.

Please feel free to add usage examples to the document for review at the next meeting.

@klausriede
Copy link

so where are the recipes? I am not sure if this is the right place to discuss this, but I wonder how we do see rights and metadata in downloaded multimedia (sound!) files - in most cases I know with downloadable files (which is good!) any information of origin disappears (which is bad!). Maybe this has already been discussed elsewhere, please indicate

@edwbaker
Copy link
Member

edwbaker commented Sep 5, 2024

Hi @klausriede - we will be working on recipes in this document, hopefully in time for the next maintenance group meeting. I will be doing some audio examples when I get back from the TDWG meeting.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
next meeting agenda Issues to be discussed at next MG meeting term proposal
Projects
None yet
Development

No branches or pull requests

4 participants