-
Notifications
You must be signed in to change notification settings - Fork 9
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
cv:Output as a subclass of dcat:Dataset? #91
Comments
Hello @jimjyang , the interpretation of the definition is more Output as a document or artefact it cannot be interpreted as dataset or a subclass of it. The relation between Output and Evidence is not also straightforward, sometimes an Output can be used as an Evidence but not always. |
Examples of "other artefact [...] that permits/authorises/entitles an Agent to (do) something" which are not datasets? |
Hello @jimjyang, an identity card or a permit certificate are not necessary a dataset per se. |
As stated before, this could be an open point to discuss over a future webinar, I don't personally disagree with but an open discussion should be hold, so this issue will be open |
Conf. the chat at the webinar recently about CPSV-AP, where you asked me to provide an example of If and when your application is approved, the |
During the webinar on the review of CPSV-AP on the 7th of November, it was agreed to:
This issue is related to #111. |
As we read the description of the class Output, "In the context of a Public Service, the output provides an official document or other artefact of the Competent Authority (Public Organization) that permits/authorises/entitles an Agent to (do) something", an output is a dataset.
Is it correctly understood?
If yes, similar to that cv:Evidence is a subclass of dcat:Dataset, could we make it explicit in CPSV-AP v.3.0.0 that cv:Output is a subclass of dcat:Dataset? This will promote and make it easier for data sharing and reuse.
The text was updated successfully, but these errors were encountered: