w3c / dxwg

Data Catalog Vocabulary (DCAT)
https://w3c.github.io/dxwg/dcat/
Other
144 stars 55 forks source link

Alignment with new version of GeoSPARQL #1425

Open andrea-perego opened 2 years ago

andrea-perego commented 2 years ago

Following from https://github.com/w3c/dxwg/issues/1392 - in particular, see summary of the discussion thread in https://github.com/w3c/dxwg/issues/1392#issuecomment-907498910 :

  1. Re-use reference vocabularies for use cases where DCAT spatial properties are not enough: The new version of GeoSPARQL can do the job, also because it addresses those gaps that led to the definition of spatial properties in the DCAT namespace.

[...] there's of course the issue of having two alternative ways to specify the same information, which does not help interoperability. However, this might be mitigated by defining mappings [...].

andrea-perego commented 2 years ago

A preliminary proposal for the mapping of DCAT spatial properties to the current draft of GeoSPARQL 1.1.

Have I missed anything?

GeoSPARQL Relation DCAT Comment
owl:propertyChainAxiom(geosparql:hasBoundingBox geosparql:hasSerialization) rdfs:subPropertyOf dcat:bbox The domain of dcat:bbox (dcterms:Location) is broader than the one of geosparql:hasBoundingBox (geosparql:Feature).
owl:propertyChainAxiom(geosparql:centroid geosparql:hasSerialization) rdfs:subPropertyOf dcat:centroid The domain of dcat:centroid (dcterms:Location) is broader than the one of geosparql:hasCentroid (geosparql:Feature).
geosparql:hasMetricSpatialResolution rdfs:subPropertyOf dcat:spatialResolutionInMeters The domain of dcat:spatialResolutionInMeters (rdfs:Resource) is broader than the one of geosparql:hasMetricSpatialResolution (geosparql:Geometry)
andrea-perego commented 2 years ago

@dr-shorthair , @nicholascar , could you please review this proposal?