search

opengeospatial / ogcapi-records

An open standard for the discovery of geospatial resources on the Web.
https://ogcapi.ogc.org/records
Other
59 stars 28 forks source link

Add informative text cross-walking OARec concepts with STAC concepts. #306

Closed pvretano closed 10 months ago

pvretano commented 1 year ago

It was suggested, at the Sept 2023 members' meeting, to add information text to the specification cross walking OGC API Records concepts with STAC concepts.

m-mohr commented 1 year ago

So pretty much this? https://github.com/stac-utils/stac-crosswalks/tree/master/ogcapi-records

m-mohr commented 1 year ago

By the way, we also discussed the Records / STAC alignment during our STAC sprint.

We will align the license field with Records. The required and additional fields that Record has, but STAC doesn't has or doesn't require: We can't require in a 1.1 as it would be breaking. Also, for some fields it doesn't make sense in STAC (e.g. title in an Item - are you sure you want to require that?)

We discussed having a STAC extension that requires those fields and adds things to STAC that are missing from Records Core. If clients then find this extension in the stac_extensions array, they can assume that the STAC is also a valid OGC API - Records extension.

pvretano commented 1 year ago

So pretty much this? https://github.com/stac-utils/stac-crosswalks/tree/master/ogcapi-records

@m-mohr yes.

pvretano commented 11 months ago

30-OCT-2023: The concensus seems to be to reference the cross walk rather than copy it into the document. We still have to OAB review ahead and hopefully they can tell us the correct path in this case. @pvretano will archive the current asciidoc version (just in case we need it later).