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
Agent: Alignment with DCAT-AP and CCCEV #36
Comments
Definitions of Agent: dct:Agent: A resource that acts or has the power to act. foaf:Agent: An agent (eg. person, group, software or physical artifact). How it's done in related models: CCCEV To align with DCAT and CCCEV the Catalogue of Services team proposes to change dct:agent to foaf:agent in CPSV-AP. |
This issue has been discussed during the webinar of the 09 December 2020. Given that no objections were raised when the proposed resolution was presented, the change will therefore be included in the next release of CPSV-AP. |
This change has been made in CPSV-AP 3.0, therefore this issue will be closed. |
In DCAT-AP (inherited from DCAT) and CCCEV there is usage of foaf:Agent while in CPSV-AP there is dct:Agent.
In addition in CPOV the class Organization is subclass of org:Organization which is subclass of foaf:Agent
The people from Foaf say that the 2 classes are equivalent:
http://xmlns.com/foaf/spec/#extns_dc
"Dublin Core's notion of Agent is much like FOAF's; Dublin Core says "A resource that acts or has the power to act.", we say "things that do stuff". As nobody has provided a counter-example of something fitting one definition but not the other, we say here that foaf:Agent stands in an 'equivalent class' relationship to dct:Agent (and vice-versa)."
There is one consideration to take in account:
dct:publisher has range dct:Agent
Such relation exists already in DCAT-AP and linked to foaf:Agent
To keep this observation in mind:
w3c/dxwg#111 (comment)
The text was updated successfully, but these errors were encountered: