Property to earmark datasets for specific target audiences

[JonasPauly-initAG]

Current Behaviour

DCAT-AP provides no option for data providers to make annotations regarding the intended target audience of a dataset.

Possible Enhancement

HealthDCAT-AP.de recommends using the Authority Table "Target audience" of the EU Publications Office as the range of a new property, e.g. dcatap:targetAudience.

This would allow data providers to increase the likeliness that datasets are found be the target audience, while data users are supported with additional information whether a specific dataset is suited for their purposes.

[bertvannuffelen]

@JonasPauly-initAG thanks for the suggestion.

However I have the following reflection on your request.

Target audience is for me a rather vague concept. In a dataset context: what does it mean that a dataset is of interest for a particular group? What is your use case for that?
I think this concept is a very portal dependent. And that this choice is an arbitrary choice. More something you would store in a system to connect stories with some datasets. It seems more a property of the story rather than a property of the dataset.

I assume that the codelist referred to is https://op.europa.eu/en/web/eu-vocabularies/concept-scheme/-/resource?uri=http://publications.europa.eu/resource/authority/target-audience.
In this list the following instances are included:

• Children and teenagers
• Consumers
• Education experts
• General public
• Legal experts
• Media experts
• Minorities
• Policy making experts
• Scientists
• Specialised
• Young people

I cannot see why one dataset is more targetting any of these groups. What is the difference between a Policy making expert, a scientist and a specialized group for a dataset on e.g. water levels in rivers? And why would it not be relevant for Media or Consumers or childern.

Therefore for me it is more a property to be maintained from the data story side:
In a eduction book on rivers, the water levels of rivers could be mentioned as background knowledge. And the same dataset can be referred in the yearly national monitoring report. For me any shared dataset is neutral to its target audience, but it might be created and collected within a particular context, and that context may heavily determine is relationship with its reusers.

Maybe I misinterpreted the intentions of your request, but at this moment I see targetaudience more as a portal specific knowledge rather than information that is inherent to a dataset.