On 21/02/2022 09:07, Lorenz Buehmann wrote:
Any experience or comments so far?
Using SubsystemLifecycle, could make the conversions by
GeoSPARQLOperations.convertGeoPredicates
extensible.
Andy
But having coordinate location (P625), located on astronomical body
(P376) as properties of a thing, is dangerous because of monotonicity in
RDF:
SELECT * { ?x wdt:P625 ?coords }
the association of P625 and P376 is lost.
What is the range of P625? It is not "earth geometry" any more.
What if there is no P376 on ?x?
As with any n-ary-like relationship, the indirection keeps the related
properties together.
This is not unique to geo. Temperatures with units for example.
