Closed simsong closed 2 years ago
it's a great idea to use the qualifiedAttribution
, but we still need to define each of the kinds of attributions with some sort of controlled vocabulary. That's because the curator really is different from the owner which is different from the steward.
There is the contributor role ontology, which is based on the CASRAI Contributor Roles Taxonomy (CRediT). Also ongoing work on the CASRAI RDM terminology may cover some aspects of attribution/roles.
The contributor role ontology looks like it has what is needed! What is involved in bringing it into DCATv3?
The CASRAI RDM terminology also looks good. Thanks for telling me about these! I will reference both of them moving forward.
We would be unlikely to 'bring it into DCAT', but it could be added to the usage notes in https://www.w3.org/TR/vocab-dcat-2/#qualified-attribution Generally the choice of which controlled-vocabulary to use in the range of a property will be a community decision, since different communities have different needs, while they can all use DCAT as the overall framework or 'schema'.
Thanks for the comments, @simsong. Are there any aspects we haven't covered in the discussion above? Otherwise, I suggest closing this issue.
Thanks for the nudge, @riccardoAlbertoni . Yes, we can close this issue.
Distinguish dataset owner, curator, steward, and other functions
Status:
Identifier:
Creator: (your name)
Deliverable(s): DCATv3
Tags
dcat,profile,dataset,documentation,provenance
Stakeholders
Governmental entities, be they data producers, data publishers or data consumers.
Problem statement
Within governments, it imay be important to distinguish multiple entities that have responsibility for data. Specific roles that require distinguishing in some applications include:
Currently, DCATv3 lacks a way to formally represent this.
Each of these could be properties with a range of
foaf:Agent.
Existing approaches
Largely this is not formally tracked by most data producers or consumers, but is tracked with a variety of informal mechanisms.
Links
Requirements
RPIF, https://github.com/w3c/dxwg/issues/76
Related use cases
UC13
Comments