Chris Holmes

Cool. I think it'd be a nice little construct for how to advertise the collectionId's that a certain collection may represent. That is not just 'description', but is actually a...

Has there been any progress on a lighterweight extension mechanism? Like just markdown/redoc description and an openapi fragment? Like where we can 'incubate' some of these, and have the community...

@pvretano - interesting. Any chance we can pull that out to be its own small building block extension that any features API can use? And then be able to iterate...

cc @hgs-truthe01 In STAC we just added sorting - currently on dev for 0.6.0, and I believe Tim has an implementation of it. It's defined at: https://github.com/radiantearth/stac-spec/blob/dev/api-spec/extensions/sorting.fragment.yaml We'd be happy...

Seems pretty specific to go into the core specification, while increasing the implementation overhead. But would make a great little extension that implementors who want dynamic user-defined management of precision...

I'd favor option 1, the second seems a bit too complicated. Though would be great to see both tried in implementations. Is there a lightweight way to specify extensions? Like...

Wouldn't those both just be their own extension? Why would they go into the CQL extension? I'd love to see a GraphQL query language as an option, I think @sharkinsspatial...

Sounds great. And going into comment period with at least two publicly accessible servers seems like a good idea. Is it normal to cut new drafts during the comment period?...

Cool, makes sense to limit scope initially. It does seem useful to have online JSON representations of the actual CRS information, but agree that it'd be good to see the...

Another example of requesting properties - http://jsonapi.org/format/#fetching-sparse-fieldsets