opengeospatial / ogc-geosparql

Public Repository for the OGC GeoSPARQL Standards Working Group
71 stars 19 forks source link

URI inconsistencies between Standards document and URIs submitted to the OGC-NA #440

Open ghobona opened 9 months ago

ghobona commented 9 months ago

There are some URI inconsistencies between Standards document and URIs submitted to the OGC-NA. An example is shown on the attached screenshot.

Screenshot 2023-09-22 at 10 56 23

This suggests that once the URIs submitted to the OGC-NA are agreed upon and registered, the Standards document should then be updated to match them.

ghobona commented 9 months ago

The following steps need to be completed to close this GitHub Issue.

situx commented 9 months ago

The namespaces you point out are the function and rule namespaces which have already been registered since GeoSPARQL 1.0 and which are also used in the funcsrules TTL file. Should we create one TTL file per namespace, i.e. one TTL file for http://www.opengis.net/def/function/geosparql and one for http://www.opengis.net/def/rule/geosparql instead of creating a joint file for both called funcsrules.ttl?

ghobona commented 9 months ago

@situx Ok, understood. We'll leave the URIs as they are and register the URIs that have been submitted by the SWG, without modification.

I have just finished checking that every URI that is in the Standards document is also in the TTL files. I only found two issues #441 and #442.

situx commented 8 months ago

@ghobona is there a problem rendering certain function URIs in the GeoSPARQL spec? I just tried to resolve https://defs.opengis.net/vocprez/object?uri=http://www.opengis.net/def/function/geosparql/minZ the minZ function and even though it is classified as a skos:Concept, vocprez returns the error messages that the function is no skos:Concept. Any ideas?

VladimirAlexiev commented 6 months ago

Now it's ok: shows on VocPrez, and has

@prefix ns2: <https://w3id.org/function/ontology#> .

<http://www.opengis.net/def/function/geosparql/minZ> a skos:Concept,
        <http://www.w3.org/ns/sparql-service-description#Function>,
        ns2:Function ;

A bit related to #467?