Aklakan commented on issue #3828: URL: https://github.com/apache/jena/issues/3828#issuecomment-4171086117
> We would need to agree on a namespace for non-GeoSPARQL geo functions. There are these existing namespaces in https://jena.apache.org/documentation/geosparql/ ```sparql PREFIX spatialF: <http://jena.apache.org/function/spatial#> # F → Filter Functions PREFIX spatial: <http://jena.apache.org/spatial#> # Namespace for property functions ``` If I understand correctly, one central change in GeoSPARQL 1.1 is, that different unit ontologies can be mixed. So perhaps some kind of `UnitRegistry` would be needed. GeoSPARQL 1.1 also introduces unit-less metric properties (i.e. the value is an xsd:double assumed to be in meters) such as: https://docs.ogc.org/is/22-047r1/22-047r1.html#_property_geohasmetriclength Relevant namespaces: ```sparql # GeoSPARQL 1.0 used uom: PREFIX uom: <http://www.opengis.net/def/uom/OGC/1.0/> # Afaik GeoSPARQL 1.1 should in addition support qudt units: PREFIX qudt: <http://qudt.org/schema/qudt/> ``` @LorenzBuehmann and I were thinking that actually this would probably something that a coding agent should be able to get right to a high degree with high coverage: check which functions are in geosparql 1.1, compare to what's in jena and set up the TODO list. then familiarize with existing implementation style in jena. finally go through each function, upgrade/add it and then test it. But so far we also didn't get around to try that out - and since @situx already did so much work there, he might want to give it a try first ;) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
