nicholascar commented on issue #3828: URL: https://github.com/apache/jena/issues/3828#issuecomment-4174059950
Hi all, in the GeoSPARQL meeting we just had, @situx, I and others agreed to establish a GeoSPARQL Extensions namespace ([GeoSPARQL Issue 672](https://github.com/opengeospatial/ogc-geosparql/issues/672)) for things not yet in GeoSPARQL 1.1 but being tested for later versions. > 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) Correct. We can easily add a unit registry to OGC Definitions Server (https://defs.opengis.net/prez/). In the best case, this would just be a collection of units already defined by QUDT. I have previously linked subsets of QUDT's units to the [QUDT Homepage](https://www.qudt.org/), such as the [Loop3d Profile](https://github.com/qudt/qudt-public-repo/tree/main/src/main/rdf/community/extensions/loop3d), so if we create such vocabs, we could indicate them there too. Here is a geology domain subset of units: http://linked.data.gov.au/def/geou. We could make a spatial or perhaps semantic spatial one (and replace the OGC's variaous bad ones). -- 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]
