Chris Holmes

I wonder if there's a way to do this that's more compatible with web architectures? I'm not sure of the exact mechanism, but something with etags / cache-control feels more...

@Mec-iS - yes, I was imagining something along those lines, where the response could just be the ref's. But I share your question on whether that is compliant with GeoJSON,...

Yeah, that could accomplish it most likely. Would just want to be sure we're getting all the cache control headers right so the client can query right. Though I'm still...

> Warning: as I pointed in https://github.com/geopandas/geo-arrow-spec/issues/8#issuecomment-1026800848, a SRID is a pointer to an entry in a spatial_ref_sys table. SRID != EPSG code. This works for GeoPackage as such table...

Fully agree that ogr2ogr is a key step. I think after we get a 0.1 'release' then it'd be a good time to push on that.

I don't think it'd prevent easily looking at the JSON responses. Indeed I'd put in a recommendation to have a clear link to it. I like how pygeoapi does it...

I'm ok to have this closed for beta.2, but I'm not giving up on this completely. At the very least I do think we should recommend a rel=alternate type=html so...

Yeah, this is definitely in scope, and has been talked about a number of times. I _think_ the current thought is to try to get the API spec to 1.0.0...

Discussed this is in STAC meeting 8/15/22, and reached consensus that we should add browseable to the core foundational specification, but just as an optional conformance class. @philvarner will update...

(and I'm happy for any clarifications too - happy to take time to read those as well, but marked as approved since I'm sure those changes will be good).