URI inconsistencies between Standards document and URIs submitted to the OGC-NA
Opened this issue · 5 comments
The following steps need to be completed to close this GitHub Issue.
- 1. Agree on URIs to be registered by the OGC-NA.
- 2. Revise the TTL/JSON files to match the revised URIs that have been agreed with the OGC-NA. See the URIs here (def) and here (ont).
- 3. Update the Standards document to use the revised URIs
- 4. Check that all URIs in the Standards document can be found in the TTL/JSON files
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 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?
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?