- From: Bert Van Nuffelen via GitHub <sysbot+gh@w3.org>
- Date: Mon, 22 Mar 2021 08:36:20 +0000
- To: public-dxwg-wg@w3.org
bertvannuffelen has just created a new issue for https://github.com/w3c/dxwg: == distribution > dcat:accessURL == In https://www.w3.org/TR/vocab-dcat-2/#Property:distribution_access_url > dcat:accessURL matches the property-chain dcat:accessService/dcat:endpointURL. In the RDF representation of DCAT this is axiomatized as an OWL property-chain axiom. is stated. Why is this stated in this way, and why is it axiomatized? This brings a very strict one-on-one relationship between dataservice and distribution which I do not think is often the case. In many services the dataservice endpointurl points to many datasets, and thus many distributions. Eg. consider https://docs.github.com/en/rest/reference all are on the same endpoint (https://api.github.com), but for each entity there is a different dataset. See https://docs.github.com/en/rest/reference/projects where there is a collection of projects per organisation and the collection of all projects. So I have for the same endpoint many access urls. Also inversely, starting from the distribution, the accessURL for a distribution of github projects is https://docs.github.com/en/rest/reference/projects and not https://api.github.com/projects. The above axiomatisation is maybe possible in some (selective) contexts, but it is for me more a severe restriction than a gain. Also this axiomatisation creates a binding between distribution and data service which should be clarified at the level of Distribution. Please view or discuss this issue at https://github.com/w3c/dxwg/issues/1334 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 22 March 2021 08:36:22 UTC