- From: Stephen Richard via GitHub <sysbot+gh@w3.org>
- Date: Fri, 06 Sep 2019 17:20:02 +0000
- To: public-dxwg-wg@w3.org
As I understand the model, a dcat:Distribution may have multiple dct:format values, and by implication, those formats would be available via any dcat:accessService/dcat:DataService associated with that distribution. I think this addresses your first and second user story. The third user story is about a dcat:DataService that is a data processing service, and agree that the current DCAT model does not handle this, but depends on the dcat:endpointDescription/rdfs:Resource object to provide information about operations, input and output formats, templates for URL parameters, etc. From the discussion in #432 it seems that the data processing functions included in the dcat:DataService definition are construed in the context of access to a particular dataset (subset, reproject, upscale, downscale, regrid...). Your user story (if I understand correctly) is about a data processing service that takes an input resource, does some processing, and returns an output resource. There is other information one would want to have to make a searchable catalog for such data processing services-- for example, a 'function' property (e.g currency-conversion, CSV-to-DCAT-transformation, units conversion, geographic reprojection...). I think these kind of data processing services would need to be represented as another kind of dcat:Resource for a catalog. -- GitHub Notification of comment by smrgeoinfo Please view or discuss this issue at https://github.com/w3c/dxwg/issues/1055#issuecomment-528939244 using your GitHub account
Received on Friday, 6 September 2019 17:20:04 UTC