stac-extensions / stac-extensions/application
Deprecate processing:expression in favor of this extension?
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 3
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
This seems generally the better place, but on the other hand processing:expression allows embedding some cases where this requires linking.
See also https://github.com/stac-extensions/processing#expression-object and https://github.com/stac-extensions/processing/issues/31
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read the application extension description alongside the referenced processing:expression expression-object documentation and processing issue #31. Determine whether processing:expression should be deprecated in favor of this extension, accounting for embedded cases versus linking; done requires a documented decision and agreed scope.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100