Open VladimirAlexiev opened 6 months ago
Hi @VladimirAlexiev
Vocprez is having trouble rendering linking these blank nodes correctly as it seems. You can find the original file for all functions that was used to generate the vocprez representation here: https://opengeospatial.github.io/ogc-geosparql/geosparql11/functions.ttl
We are still working on some issues with NA though, namely whether we should create a parameter registry for the function parameters for instance. The ns1 indeed seems like a duplicate, but it would seem it was added during NA processing as well.
Thanks @situx! Can you also answer bullets 2 and 3 from the original issue?
BTW:
funcs:buffer_param1 -> funcs:buffer_output
)@VladimirAlexiev @situx The namespaces are not changed nor automatically generated at upload. However, the namespace prefixes are indeed automatically generated. This is necessary because of the size (more than 240k statements) of the triple store and the variety of models stored within it.
We are waiting for some performance issues to be resolved on the UI update (VocPrez->Prez) - that will give us enough control to render more complex structures such as blank nodes adequately.
The other thing is that we must have labels in the "graph closure" - so we need an ontology with labels for "https://w3id.org/function/ontology#expects" etc.
At this point we are in the "T-box" of the knowledge graph, and required ontologies must be submitted along with the resources, and we will need to vet these for conflicts before uploading them to the knowledge graph to support better rendering.
The T-box is essentially the meta-model for standards and will control rendering options for resources. The meta-model is governed by the OGC-NA, managed with COSI team support. We havent yet formalised the process, but as more information models get published this will need to scale.
(I guess this issue is not for this project because vocprez is maintained by OGCNA. But the repo https://github.com/opengeospatial/ogcna-auto-review is not appropriate. @nicholascar Can you dispatch this issue to the correct project?)
I'm trying to find RDF details about
geof:buffer
to make our own documentation more precise.Look at http://defs.opengis.net/vocprez/object?uri=http://www.opengis.net/def/function/geosparql/buffer It shows![image](https://github.com/opengeospatial/ogc-geosparql/assets/536250/176a9e1f-d8d4-420e-b025-bc58fc5b2e19)
expects
andreturns
with 6 resources eachBut if you click you get nothing useful:![image](https://github.com/opengeospatial/ogc-geosparql/assets/536250/783ebe39-2530-4e13-aa88-96d525f3b743)
Look at its Turtle representation:
genid*
andnode*
). Instead, it should traverse the blank nodes and show their data (as the default implementation of DESCRIBE, which is SCBD, does)nsN
which make it harder to read the Turtle_profile=describe
and_profile=concept
return the same data, is it supposed to be like this?ns1
) has been deprecated by DCMI a year (or more?) ago, and the info is duplicate, so you should just drop these triples