search

opengeospatial / ogc-geosparql

Public Repository for the OGC GeoSPARQL Standards Working Group
77 stars 20 forks source link

Specify geometry types in definitions of geometry functions #206

Closed FransKnibbe closed 3 years ago

FransKnibbe commented 3 years ago

Now that there is a vocabulary for Simple Features geometry types, can geometry types be used for improved definitions of GeoSPARQL functions? The types could be used to specify input and output of GeoSPARQL functions, which would help users and implementers know what to expect, and lessen the risk of unintended function usage.

By the way, does anyone know of a semweb vocabulary to describe (new) SPARQL functions?

situx commented 3 years ago

I only know of this http://www.ldodds.com/schemas/sparql-extension-description/ but it might be outdated

FransKnibbe commented 3 years ago

I only know of this http://www.ldodds.com/schemas/sparql-extension-description/ but it might be outdated

It does not seem to have terms that could be useful for GeoSPARQL.

The Service Description vocabulary does have sd:Function and sd:Aggregate, which could be useful.

nicholascar commented 3 years ago

The sd ones you mention are really the only ones I've thought much about. In the RDFlib Python GeoSPARQL extensions for DGGS, we just use informal naming such as functions being "property" or "filter" functions in line with sd.

I think other extension implementers, like GraphDB, just use an OpenAPI, not a semantic, description of the functions.

jabhay commented 3 years ago

Ensure this is covered off by #212