You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be useful to have the conformance classes directly specified in the schemas. We could use it to automatically generate the landing page in the case of a STAC API framework leveraging code generation.
It would be possible to specify them at schema or operation level for a fine granularity. For instance with item-search:
openapi: 3.0.3info:
title: STAC API - Item Searchversion: 1.0.0-rc.2description: >- This is an OpenAPI definition of the SpatioTemporal Asset Catalog API - Item Search specification.contact:
name: STAC Specificationurl: 'http://stacspec.org'license:
name: Apache License 2.0url: 'http://www.apache.org/licenses/LICENSE-2.0'conformance: [ "https://api.stacspec.org/v1.0.0-rc.2/item-search" ]tags:
- name: Item Searchdescription: essential characteristics of a STAC APIpaths:
[...]
The text was updated successfully, but these errors were encountered:
These were added to the Foundation specs. I've made a mental note to add it to the extensions (but not filed the ~8 issues against every extension that could use it)
It would be useful to have the conformance classes directly specified in the schemas. We could use it to automatically generate the landing page in the case of a STAC API framework leveraging code generation.
It would be possible to specify them at schema or operation level for a fine granularity. For instance with
item-search
:The text was updated successfully, but these errors were encountered: