Relation of various Agent classes used throughout the specification #112
Labels
release:3.0.0
Actively being worked on for GeoDCAT-AP 3.0.0
status:fixed
Resolution applied in draft
type:improvement
Improvement of current handling of a problem
webinar:2024-04-23
To be discussed in the 2024-04-23 webinar
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:rangeIncludes
instead of defining ardfs:range
. This may be therefore changed tofoaf:Agent
foaf:Agent
- as range of agent role properties (publisher, creator, ...) in Specification part, e.g. as range of Catalog publisherprov:Agent
- as range ofprov:agent
in AttributionWhat 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:foaf:Agent
definition:prov:Agent
definition:Proposal
dct:Agent
withfoaf:Agent
to be consistent, also with DCAT-AP (DCAT only recommendsfoaf:Agent
as range), andfoaf:Agent
andprov:Agent
and the expectations on each one, e.g. regarding usage of properties. Suggest double typing ofprov:Agent
withfoaf:Agent
or a specific subclass.The text was updated successfully, but these errors were encountered: