- Title: Versioning Indicators
- Identifier: version
- Field Name Prefix: -
- Scope: Item, Collection
- Extension Maturity Classification: Proposal
This extension allows to version STAC Collections and STAC Items. Therefore, it also allows to deprecate legacy versions. Only fields and possible link relation types are defined in this extension, but it does NOT suggest any versioning best practices to structure static or dynamic catalogs. Instead check the Versioning Best Practices for Catalogs.
This extension applies to STAC Items and STAC Collections.
- Examples: Collection, Item
- JSON Schema
For Items, the fields are placed in the properties. For Collections, the fields are placed on the top level of the Collection.
| Field Name | Type | Description |
|---|---|---|
| version | string | REQUIRED. Version of the Collection or Item. |
| deprecated | boolean | Specifies that the Collection or Item is deprecated with the potential to be removed. Defaults to false. It should be transitioned out of usage as soon as possible and users should refrain from using it in new projects. A link with relation type latest-version SHOULD be added to the links and MUST refer to the resource that can be used instead. |
The following types should be used as applicable rel types for the Link Object to reference the latest version, the predecessor version and successor versions. These are all following RFC 5829.
| Type | Description |
|---|---|
| latest-version | This link points to a resource containing the latest (e.g., current) version. |
| predecessor-version | This link points to a resource containing the predecessor version in the version history. |
| successor-version | This link points to a resource containing the successor version in the version history. |
None yet, still in proposal stage.