- From: Simon Cox via GitHub <sysbot+gh@w3.org>
- Date: Wed, 18 Sep 2019 03:40:42 +0000
- To: public-dxwg-wg@w3.org
The addition of DataService to the DCAT vocabulary is perhaps the most significant enhancement in this version. It was in response to a number of use-cases submitted in the early phase of the work. We worked on the details of the model starting around 18 months ago, and the detailed model was finalized and merged into the head 28 March (sha 33035d5fa4076fce19b221d173eba2b2b6ed98e9) The specific requirement that you are raising now was not visible to us while we were preparing the solution. In the example above I show that the available formats from a `dcat:DataService` can be made available on the path dcat:servesDataset/dcat:distribution/dct:format` . So the model is competent to express the information in this requirement, though perhaps not optimized for it. The model is integrated and consistent with the original DCAT view (which separates conceptual datasets from their serializations) and I disagree that this path is particularly 'file-oriented', especially when implemented with blank-nodes as shown. However, in every model (ontology) choices are made about which relationships to give names to, and which ones to leave as paths through a graph. These choices are usually informed by known applications. This issue is now tagged as a future priority, so let's look again when the dust on the CR/Rec process has settled. -- GitHub Notification of comment by dr-shorthair Please view or discuss this issue at https://github.com/w3c/dxwg/issues/1055#issuecomment-532505060 using your GitHub account
Received on Wednesday, 18 September 2019 03:40:45 UTC