- From: Nicholas Car via GitHub <sysbot+gh@w3.org>
- Date: Wed, 21 Feb 2018 23:03:06 +0000
- To: public-dxwg-wg@w3.org
I don't follow, how can `locn:geometry` be used? Range for `dct:spatial` is `dct:Location` and I see no `locn`/`dct` links (subclassing).
Assuming I've missed something and this can work,
`locn:geometry` seems allows for WKT/GML representation as per GeoSPARQL. From @stijngoedertier 's example:
```
locn:geometry "POLYGON((-10.58 70.09,34.59 70.09,34.59 34.56,-10.58 34.56, -10.58 70.09))"^^gsp:wktLiteral ;
```
However we have more sophisticated feature/geometry handling elsewhere, like in GeoSPARQL itself which has Geometry & Feature classes. Using GeoSPARQL, a site's location in SOSA:
```
<http://pid.geoscience.gov.au/site/17943> a <http://vocabulary.odm2.org/samplingfeaturetype/borehole>,
geosp:hasGeometry [ a geosp:Geometry ;
geosp:asWKT "SRID=GDA94;POINT(137.8563726 -33.7108293)"^^geosp:wktLiteral ] .
```
I can't see any normative links from locn to GeoSPARQL though, only suggestions for use. Perhaps Andrea, a locn editor, can indicate the intention of locn? Otherwise, I'd be more inclined to allow the use of GeoSPARQL directly.
--
GitHub Notification of comment by nicholascar
Please view or discuss this issue at https://github.com/w3c/dxwg/issues/83#issuecomment-367508146 using your GitHub account
Received on Wednesday, 21 February 2018 23:03:52 UTC