W3C home > Mailing lists > Public > public-dxwg-wg@w3.org > May 2021

Re: [dxwg] ranges for `dcat:bbox` and `dcat:centroid`. (#1359)

From: Andrea Perego via GitHub <sysbot+gh@w3.org>
Date: Mon, 03 May 2021 18:37:27 +0000
To: public-dxwg-wg@w3.org
Message-ID: <issue_comment.created-831451188-1620067046-sysbot+gh@w3.org>
@init-dcat-ap-de said:

> @andrea-perego not sure if this is just a missunderstanding. I understood your post from 3 days ago as an argument, why bbox and centroid should remain with a range of rdfs:Literal.
> 
> But they have the same usage note as locn:geometry had previously, which stated that the range was "intentionally generic, with the purpose of allowing different geometry encodings."

Exactly. The original usage note for the three properties was referring to `rdfs:Literal` as range, and therefore we have not seen the need of changing it for `dcat:bbox` and `dcat:centroid`.

Based on what you say, it seems that the note is not clear enough about the fact that `dcat:bbox` and `dcat:centroid` are supposed to be used only with literals:

> The range of this property is intentionally generic, with the purpose of allowing different geometry encodings. E.g., the geometry could be encoded as WKT (geosparql:wktLiteral [GeoSPARQL]).

Note that here with "generic" we mean that, by specifying `rdfs:Literal` as range, we are not prescribing any specific datatype (e.g., `geosparql:wktLiteral`, `geosparql:gmlLiteral`, `geosparql:geoJSONLiteral`).

I wonder whether revising the note as follows may help clarify this point:

> The range of this property **(rdfs:Literal)** is intentionally generic, with the purpose of allowing different geometry **literal** encodings. E.g., the geometry could be encoded as **a WKT literal** (geosparql:wktLiteral [GeoSPARQL]).


-- 
GitHub Notification of comment by andrea-perego
Please view or discuss this issue at https://github.com/w3c/dxwg/issues/1359#issuecomment-831451188 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 3 May 2021 18:37:30 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:28:37 UTC