I see in the example files for OGC services (WMS and WFS) that use a bounding box specified in the specifications as {minx,miny,maxx,maxy} that these have been incorrectly translated as having fixed meaning,
so for example
http://resource.europe-geology.eu/service/wmsGeologicUnit/operation> a hydra:Operation;
hydra:method "GET"^^xsd:string;
hydra:returns "image/png";
hydra:property[ a hydra:IriTemplate;
hydra:template "http://resource.europe-geology.eu/service/wmsGeologicUnit{?service, version, request, layers, crs, format, width, height}&bbox={minlatitude, minlongitude, maxlatitude, maxlongitude}"^^xsd:string;
bbox is above being set not as minx,miny,maxx,maxy as per the specification, but as minlatitude, minlongitude, maxlatitude, maxlongitude
It should be noted that x can be latitude, or longitude (or indeed another dimension), as can y. (time, elevation...)
it looks like what is missing are some concepts like
I see in the example files for OGC services (WMS and WFS) that use a bounding box specified in the specifications as {minx,miny,maxx,maxy} that these have been incorrectly translated as having fixed meaning,
so for example
bbox is above being set not as minx,miny,maxx,maxy as per the specification, but as minlatitude, minlongitude, maxlatitude, maxlongitude
It should be noted that x can be latitude, or longitude (or indeed another dimension), as can y. (time, elevation...)
it looks like what is missing are some concepts like