No multiple parents #1279
Open
No multiple parents #1279
+27
−16
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
m-mohr
reviewed
May 7, 2024
| @@ -12,6 +12,8 @@ and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0. | |||
| - The `keywords` field known from Collections is available in common metadata. ([#1187](https://github.com/radiantearth/stac-spec/issues/1187)) | |||
| - The `license` field additionally supports SPDX expressions and the value `other`. | |||
| - The `roles` field known from Assets and Providers is available in common metadata. ([#1267](https://github.com/radiantearth/stac-spec/issues/1267)) | |||
| - `collection` relationship type for link in catalog and collection | |||
| - Clarification on unique parent link requirement | |||
There was a problem hiding this comment.
Should be moved to Changed or Fixed, I think.
m-mohr
reviewed
May 7, 2024
| @@ -657,6 +657,13 @@ So if you are writing a STAC client it is recommended to start with just support | |||
| turn, if your data is published online publicly or for use on an intranet then following these recommendations will ensure | |||
| that a wider range of clients will work with it. | |||
|
|
|||
| #### Unique Parent Link | |||
|
|
|||
| STAC catalogs do not support multiple parents. Links with `rel` of type `parent` and `collection` must be unique. | |||
There was a problem hiding this comment.
- The following sounds like a requirement but is in best practices. Should this be moved to the spec?
STAC catalogs do not support multiple parents.
- There can be multiple parent links for different encodings (e.g. application/json and text/html). We should clarify that this only applies for STAC-specific media types.
- This may need a discussion about collections first. I'm a bit hesistant here, because OGC looks into supporting multiple collections, I think.
On the other hand, we should also clarify thatrootshould be unique.
|
This PR is set at the agenda of the next STAC meetup along with the collections discussions. |
|
Discussed in STAC meetup:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related Issue(s): #1230, #1236, #1273
Proposed Changes:
PR Checklist:
or a CHANGELOG entry is not required.
and I have opened issue/PR #XXX to track the change.