Add clarification around collection-level assets in item-assets. #880
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.
This PR adds language to the
item-assets
spec to clarify that collection-level asset objects should not contain properties that are not explicitly stated in the item's asset objects themselves.This comes out of a discussion during STAC Sprint 6. It was determined that while allowing for asset properties to be defined in only the collection-level asset objects was a way to save space, it would be more in line with the spec to have items explicitly contain all asset property information.
If you're currently using the item-assets extension to consolidate item-level asset object properties in an API setting, consider storing the STAC items without those consolidated properties internally as 'invalid' STAC items, and merge in the desired collection-level asset object properties at serving time.
PR Checklist: