- From: Bert Van Nuffelen via GitHub <sysbot+gh@w3.org>
- Date: Thu, 09 Dec 2021 13:00:53 +0000
- To: public-dxwg-wg@w3.org
In DCAT-AP there is the property _dcatap:availability_ defined for distributions. Having now as just published controlled vocabulary https://op.europa.eu/en/web/eu-vocabularies/concept-scheme/-/resource?uri=http://publications.europa.eu/resource/authority/planned-availability W.r.t. accessRights, the DCAT profile for Flanders has identified that there is a difference between the accessrights to the dataset versus the accessRights to the service providing access to the data. The first is a legal right: by law it is public data, or it has restricted access. In government context, this accessrights is connected with Public Information transparency (PSI directive etc.) But that right to be public is not the same as for a service. A public API is a service for which no check happens to whether the user of that service has the right to access the data. This still can mean their are security and access monitoring, but solely with the purpose to have fair use of the service. E.g. to prevent DOS attacks. A non-public API is then a service where the security and access monitoring is connected with a granting system checking conditions (age/gender/profession/kind of user/...). Observe that these are different interpretations of access per kind of resource: The first is bound to inherit legal basis, while the second is more about the measures taken to make the service operational. Note that for file-based access this distinction is also present in accessURL / downloadURL. The first is used when the second (no limitations) cannot be fulfilled. -- GitHub Notification of comment by bertvannuffelen Please view or discuss this issue at https://github.com/w3c/dxwg/issues/1432#issuecomment-989830674 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 9 December 2021 13:00:55 UTC