Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add new properties to dct:Location #85

Open
NatasaSofou opened this issue Sep 12, 2019 · 3 comments

Comments

@NatasaSofou
Copy link
Contributor

commented Sep 12, 2019

In dct:Location, add properties:

  • lcon:geometry: Associates any resource with the corresponding geometry
  • dcat:bbox: Specifies the geographic bounding box of a resource.
  • dcat:centroid: Specifies the geographic center (centroid) of a resource.
@andrea-perego

This comment has been minimized.

Copy link

commented Sep 12, 2019

Please note that locn:geometry is already supported in GeoDCAT-AP, and I think also in DCAT-AP (at least indirectly).

Related GeoDCAT-AP issue: SEMICeu/GeoDCAT-AP#1

@NatasaSofou

This comment has been minimized.

Copy link
Contributor Author

commented Sep 27, 2019

Proposed resolution: in dct:Location class, add properties:

  • lcon:geometry (optional)
  • dcat:bbox (recommended)
  • dcat:centroid (recommended)
@andrea-perego

This comment has been minimized.

Copy link

commented Sep 27, 2019

Not sure about which should be optional and which recommended.

The point is that these three properties have different purposes. So, whether they are recommended or not depends on their use, as also stated in the usage note of dct:Location of the DCAT2 specification - quoting:

  • For an extensive geometry (i.e., a set of coordinates denoting the vertices of the relevant geographic area), the property locn:geometry [LOCN] SHOULD be used.
  • For a geographic bounding box delimiting a spatial area the property dcat:bbox SHOULD be used.
  • For the geographic center of a spatial area, or another characteristic point, the property dcat:centroid SHOULD be used.

Moreover, as locn:geometry is already being used in (Geo)DCAT-AP - usually for bounding boxes - backward compatibility should be taken into account.

Based on this, an option is to make locn:geometry recommended, and dcat:bbox and dcat:centroid optional, adding however a note saying that they are recommended when the geometry is a bbox or a centroid, respectively.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.