osdu:bbox is not properly defined about osdu-ontology HOT 3 CLOSED

Thanks for the catch on this important issue. This has been corrected in our latest commit of the ontology. osdu:bbox is renamed to osdu:hasBBox now has a range of an object named osdu:BBox. osdu:BBox may use the property osdu:hasPoint with range osdu:Point, which may use the properties osdu:hasValue for unordered value arrays, or osdu:xCoordinate and osdu:yCoordinate for specified coordinate values.

from osdu-ontology.

Is this really fixed?

• hasValue will return 2 coordinates in random order, which seems fatal to me.
• hasPoint will return 2 Points in random order, which may be ok if you don't care which is which corner... But to check what falls into the bbox, you'd need to sort them.

More to the point: isn't it best to use the GeoSPARQL standard (#5), which is supported by most semantic repositories?
GeoSPARQL geometries are indexed in special geospatial indexes, so finding all points (or other features) within a bbox is a very fast operation: you don't need to enumerate all points and check them one by one.

from osdu-ontology.