- From: Bert Van Nuffelen via GitHub <sysbot+gh@w3.org>
- Date: Fri, 27 Aug 2021 08:04:09 +0000
- To: public-dxwg-wg@w3.org
@dr-shorthair yes this seems close to what I meant. I went through the geosparql spec and there might be compatibility problems with the domains and ranges: a) domain geosparql:hasBoundingBox has as domain geo:Feature, which is a geo:SpatialObject. So now the question rises if one would like to reuse it, is dct:Location a geo:SpatialObject? If that is not the case then reuse creates discussions. Do you know the answer? b) range geosparql:hasBoundingBox has as range geo:Geometry which is different from dcat:bbox which is a rdfs:Literal Although the intend of the property is very similar, the chosen modeling is probably not trivially compatible with eachother. And maybe after a more in depth investigation it are properties that cannot be merged. -- GitHub Notification of comment by bertvannuffelen Please view or discuss this issue at https://github.com/w3c/dxwg/issues/1392#issuecomment-907010589 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 27 August 2021 08:04:10 UTC