Skip to content

Update maturity classification to Stable - #48

Open
emmanuelmathot wants to merge 2 commits into
mainfrom
maturity-stable
Open

emmanuelmathot wants to merge 2 commits into
mainfrom
maturity-stable

Conversation

@emmanuelmathot

Copy link
Copy Markdown
Member

Change the maturity classification of the extension from Candidate to Stable in both the README and CHANGELOG files. This reflects the current status of the extension.

A survey of public STAC APIs (November 2026) found the extension in ten catalogs from different organisations:

Catalog Schema version Fields in use
Copernicus Data Space Ecosystem v1.2.0 level, version, datetime, facility, software, lineage
Element 84 Earth Search v1.1.0 software, derived_from links
EOPF Sentinel Zarr Samples v1.2.0 level, lineage, version, facility, software
INPE Brazil Data Cube v1.0.0 lineage, level, software, facility
CNES GEODES v1.2.0 level
EODC v1.2.0 level, datetime
VITO Terrascope v1.2.0 level, version
NASA MAAP v1.2.0 level
Destination Earth HDA v1.2.0 level
Microsoft Planetary Computer (goes-glm) v1.1.0 level

The qualifiers and the lineage fields carry the adoption. The survey found no use of processing:expression or of the processing-* relation types. It read mostly collection documents, so use in Items is possible.

Comment thread README.md
Comment on lines +198 to +204
### Changes to the extension

This extension has the maturity classification *Stable*.
All changes to the fields, the relation types or the JSON Schema require a pull request,
a review by the extension owner and at least one other member of the STAC community, and a new version number.
Breaking changes require a new major version.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we don't need to repeat this, can just link back to the upstream extensions maturity/... document in stac-spec.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants