Perhaps this is more of a question or preference than an issue but, would you consider changing the order of values in the box url template to match those in the Open Search Geo Spec? From my tests the {B} in the URL is templated as yMin, xMin, yMax, xMax while the Open Search Geo Spec is xMin, yMin, xMax, yMax. This is implemented in a few different RESTful geo web service providers like MapFish, Arc2Earth and FeatureServer (and I'm sure others).
This would make it super easy to return GeoJSON tiles from these providers instead of having to calculate a Lat/Lng bounds from web mercator coordinates.
Perhaps this is more of a question or preference than an issue but, would you consider changing the order of values in the box url template to match those in the Open Search Geo Spec? From my tests the {B} in the URL is templated as yMin, xMin, yMax, xMax while the Open Search Geo Spec is xMin, yMin, xMax, yMax. This is implemented in a few different RESTful geo web service providers like MapFish, Arc2Earth and FeatureServer (and I'm sure others).
This would make it super easy to return GeoJSON tiles from these providers instead of having to calculate a Lat/Lng bounds from web mercator coordinates.