- From: Andrea Perego via GitHub <sysbot+gh@w3.org>
- Date: Thu, 25 Mar 2021 23:36:55 +0000
- To: public-dxwg-wg@w3.org
Dear @aidig ,
Many apologies for replying so late.
You points 1 & 2 are being addressed in PR https://github.com/w3c/dxwg/pull/1337
About point 3, this issue is under discussion in https://github.com/w3c/dxwg/issues/975 , and we have yet to take a decision.
About point 4:
> 4. Regarding property dcat:spatialResolutionInMeters, it would be beneficial to add the following information from the DCAT spec (from bbox) in the TTL section describing dcat:spatialResolutionsInMeters or - ideally - replacing the current second scopeNote with this text: “The ability of to detect details in an raster image or grid is referred to as spatial resolution. The spatial resolution is stated in metres. The more pixels are included in a raster image of a certain area, the higher the spatial resolution meaning the more details can be observed”.
(source: http://fis.uni-bonn.de/en/recherchetools/infobox/professionals/resolution/spatial-resolution)
I'm not sure about this sentence:
> Regarding property dcat:spatialResolutionInMeters, it would be beneficial to add the following information from the DCAT spec (from bbox) in the TTL section describing dcat:spatialResolutionsInMeters [...]
Exactly, which information from the spec should be added to the .ttl?
About the text you propose, the issue is that it is specifically about the notion of spatial resolution in the geospatial domain, whereas DCAT is meant to be domain-agnostic, and the classes and properties used in DCAT (spatial resolution included) are addressing requirements identified across domains. We can still add it as an example ("For instance, in geospatial data etc."), but maybe the text should be re-phrased to be comprehensible also to non-geospatial people (e.g., not everyone is familiar with the notions of grid / raster images).
--
GitHub Notification of comment by andrea-perego
Please view or discuss this issue at https://github.com/w3c/dxwg/issues/1246#issuecomment-807735420 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 25 March 2021 23:36:57 UTC