Merge pull request #3 from stac-api-extensions/pv/release-1.0.0-rc.2

updates for release 1.0.0-rc.2

Author: philvarner

CHANGELOG.md

@@ -4,24 +4,29 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
-## [Unreleased] - TBD
+## [v1.0.0-rc.2] - TBD
 
 ### Fixed
 
 - Clarify that the names for fields can either be prefixed by `properties` or not.
 
-## [v1.0.0-rc.1](https://github.com/radiantearth/stac-api-spec/tree/v1.0.0-rc.1) - 2022-03-17
+## [v1.0.0-rc.1] - 2022-03-17
 
 None
 
-## [v1.0.0-beta.4](https://github.com/radiantearth/stac-api-spec/tree/v1.0.0-beta.4) - 2021-10-05
+## [v1.0.0-beta.4] - 2021-10-05
 
 ### Added
 
 - Support binding Fields Extensions to STAC Features items resource
   endpoint (`/collections/{collectionId}/items`)
 
+## Older versions
+
 Versions [v1.0.0-rc.1](https://github.com/radiantearth/stac-api-spec/tree/v1.0.0-rc.1) and
 prior can be found in the [stac-api-spec](https://github.com/radiantearth/stac-api-spec/) repo
 
-[Unreleased]: tbd
+[Unreleased]: <https://github.com/stac-api-extensions/fields/compare/v1.0.0-rc.2..main>
+[v1.0.0-rc.2]: <https://github.com/stac-api-extensions/fields/tree/v1.0.0-rc.2>
+[v1.0.0-rc.1]: <https://github.com/radiantearth/stac-api-spec/tree/v1.0.0-rc.1>
+[v1.0.0-beta.4]: <https://github.com/radiantearth/stac-api-spec/tree/v1.0.0-beta.4>

README.md

@@ -2,12 +2,12 @@
 
 - **OpenAPI specification:** [openapi.yaml](openapi.yaml)
 - **Conformance Classes:** 
-  - `STAC API - Item Search` binding: <https://api.stacspec.org/v1.0.0-rc.1/item-search#fields>
-  - `STAC API - Features` binding: <https://api.stacspec.org/v1.0.0-rc.1/ogcapi-features#fields>
+  - `STAC API - Item Search` binding: <https://api.stacspec.org/v1.0.0-rc.2/item-search#fields>
+  - `STAC API - Features` binding: <https://api.stacspec.org/v1.0.0-rc.2/ogcapi-features#fields>
 - **Extension [Maturity Classification](https://github.com/radiantearth/stac-api-spec/tree/main/README.md#maturity-classification):** Candidate
 - **Dependencies:**
-  - [STAC API - Item Search](https://github.com/radiantearth/stac-api-spec/tree/v1.0.0-rc.1/item-search)
-  - [STAC API - Features](https://github.com/radiantearth/stac-api-spec/tree/v1.0.0-rc.1/ogcapi-features)
+  - [STAC API - Item Search](https://github.com/radiantearth/stac-api-spec/tree/v1.0.0-rc.2/item-search)
+  - [STAC API - Features](https://github.com/radiantearth/stac-api-spec/tree/v1.0.0-rc.2/ogcapi-features)
 
 By default, STAC API endpoints that return Item objects return every field of those Items. However,
 Item objects can have hundreds of fields, or large
@@ -16,8 +16,8 @@ fields in an Item are used, so this
 specification provides a mechanism for clients to request that servers to explicitly include or exclude certain fields.
 
 This behavior may be bound to either or both of 
-[STAC API - Item Search](https://github.com/radiantearth/stac-api-spec/tree/v1.0.0-rc.1/item-search) (`/search` endpoint) or
-[STAC API - Features](https://github.com/radiantearth/stac-api-spec/tree/v1.0.0-rc.1/ogcapi-features)
+[STAC API - Item Search](https://github.com/radiantearth/stac-api-spec/tree/v1.0.0-rc.2/item-search) (`/search` endpoint) or
+[STAC API - Features](https://github.com/radiantearth/stac-api-spec/tree/v1.0.0-rc.2/ogcapi-features)
 (`/collections/{collectionId}/items` endpoint) by advertising the relevant conformance class. 
 
 When used in a POST request with `Content-Type: application/json`, this adds an attribute `fields` with 
@@ -45,7 +45,7 @@ must be returned and the Item entities will not contain that
 attribute. 
 
 If no `fields` are specified, the response is **must** be a valid
-[ItemCollection](https://github.com/radiantearth/stac-spec/tree/v1.0.0-rc.1/itemcollection/README.md). If a client excludes
+[ItemCollection](https://github.com/radiantearth/stac-spec/tree/v1.0.0-rc.2/itemcollection/README.md). If a client excludes
 attributes that are required in a STAC Item, the server may return an invalid STAC Item. For example, if `type` 
 and `geometry` are excluded, the entity will not even be a valid GeoJSON Feature, or if `bbox` is excluded then the entity 
 will not be a valid STAC Item.

openapi.yaml

@@ -2,7 +2,7 @@ openapi: 3.0.3
 info:
   title: The SpatioTemporal Asset Catalog API - Fields
   description: Adds parameter to control which fields are returned in the response.
-  version: 1.0.0-rc.1
+  version: 1.0.0-rc.2
 paths: {}
 components:
   parameters: