Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

link type no longer required #416

Merged
merged 2 commits into from
Apr 13, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,12 +5,21 @@ 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).

## [v1.0.0-rc.4] - TBD

## Changed

- Field `type` is no longer required for all Link objects, but is instead strongly
recommended. This was added as a requirement in 1.0.0-rc.3 based on a mis-reading
of the OGC Features spec, and is now removed as a requirement.

## [v1.0.0-rc.3] - 2023-03-27

## Changed

- Browseable has been moved to an extension, now located at <https://github.com/stac-api-extensions/browseable>
- Link relation `parent` is no longer a required link for Collections or Items
- Field `type` is now required for all Link objects

## Added

Expand Down
4 changes: 2 additions & 2 deletions core/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -63,8 +63,8 @@ but sub-catalogs whose items are all in one database can support search.

## Link Relations

While the STAC definition of Link does not require the `type` field,
*STAC API - Core* requires all Links to have this field.
The STAC definition of Link does not require the `type` field,
but it is **STRONGLY RECOMMENDED** that this field exists.
If the target of a Link's `type` is unknown, `type` SHOULD be set to `application/octet-stream` or `text/plain`.

The following Link relations are defined for the Landing Page (root).
Expand Down
4 changes: 2 additions & 2 deletions item-search/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -49,8 +49,8 @@ Implementing `GET /search` is **required**, `POST /search` is optional, but reco

## Link Relations

While the STAC definition of Link does not require the `type` field,
*STAC API - Item Search* requires all Links to have this field.
The STAC definition of Link does not require the `type` field,
but it is **STRONGLY RECOMMENDED** that this field exists.
If the target of a Link's `type` is unknown, `type` SHOULD be set to `application/octet-stream` or `text/plain`.

This conformance class also requires implementation of the link relations in the [STAC API - Core](../core) conformance class.
Expand Down
4 changes: 2 additions & 2 deletions ogcapi-features/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -100,8 +100,8 @@ by *STAC API - Core*, the

These conformance classes also requires implementation of the link relations in the [STAC API - Core](../core) conformance class.

While the STAC definition of Link does not require the `type` field, this is required by OAFeat,
and is thereby required by the *STAC API - Features* conformance class.
The STAC definition of Link does not require the `type` field,
but it is **STRONGLY RECOMMENDED** that this field exists.
If the target of a Link's `type` is unknown, `type` SHOULD be set to `application/octet-stream` or `text/plain`.

### Landing Page (/)
Expand Down