Problem statement
There are different classes for Agents used throughout the GeoDCAT-AP 2.0.0 specification. These include:
dct:Agent - as range of agent role properties (publisher, creator, ...) in Bindings overview - probably coming from the Dublin Core definitions, which, however, since 2020 only state dcam:rangeIncludes instead of defining a rdfs:range. This may be therefore changed to foaf:Agent
foaf:Agent - as range of agent role properties (publisher, creator, ...) in Specification part, e.g. as range of Catalog publisher
prov:Agent - as range of prov:agent in Attribution
What are the relations among the occurences of those classes in the specification? What are the expected properties, when only foaf:Agent has its section in the specification?
dct:Agent definition:
A resource that acts or has the power to act.
foaf:Agent definition:
The Agent class is the class of agents; things that do stuff.
prov:Agent definition:
An agent is something that bears some form of responsibility for an activity taking place, for the existence of an entity, or for another agent's activity.
Proposal
Replace dct:Agent with foaf:Agent to be consistent, also with DCAT-AP (DCAT only recommends foaf:Agent as range), and
Add an explanatory text on the difference or similarity of foaf:Agent and prov:Agent and the expectations on each one, e.g. regarding usage of properties. Suggest double typing of prov:Agent with foaf:Agent or a specific subclass.
Problem statement There are different classes for Agents used throughout the GeoDCAT-AP 2.0.0 specification. These include:
dct:Agent- as range of agent role properties (publisher, creator, ...) in Bindings overview - probably coming from the Dublin Core definitions, which, however, since 2020 only statedcam:rangeIncludesinstead of defining ardfs:range. This may be therefore changed tofoaf:Agentfoaf:Agent- as range of agent role properties (publisher, creator, ...) in Specification part, e.g. as range of Catalog publisherprov:Agent- as range ofprov:agentin AttributionWhat are the relations among the occurences of those classes in the specification? What are the expected properties, when only
foaf:Agenthas its section in the specification?dct:Agentdefinition:foaf:Agentdefinition:prov:Agentdefinition:Proposal
dct:Agentwithfoaf:Agentto be consistent, also with DCAT-AP (DCAT only recommendsfoaf:Agentas range), andfoaf:Agentandprov:Agentand the expectations on each one, e.g. regarding usage of properties. Suggest double typing ofprov:Agentwithfoaf:Agentor a specific subclass.