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

require children endpoint to return all child link objects #265

Merged

Conversation

philvarner
Copy link
Collaborator

Related Issue(s):

Proposed Changes:

  1. require /children to return all child links

PR Checklist:

  • This PR is made against the dev branch (all proposed changes except releases should be against dev, not master).
  • This PR has no breaking changes.
  • This PR does not make any changes to the core spec in the stac-spec directory (these are included as a subtree and should be updated directly in radiantearth/stac-spec)
  • I have added my changes to the CHANGELOG or a CHANGELOG entry is not required.

It is recommended that the Catalog and Collection objects returned by the `/children` endpoint are the same
as those referenced by `child` link relations in the STAC API Landing Page. Following these semantics, it should
return the immediate children of the root Catalog, rather than all descendant catalogs or collections.
it contains using the link relation `children` to an endpoint `/children`. The `/children` endpoint shall
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just a general observation, but I think we mostly use MUST instead of SHALL in the documentation. Your recent PRs use SHALL and I think we should be more consistent here. Could we try to use MUST instead of SHALL? I just had to look it up again whether SHALL was equal to MUST or SHOULD and found it confusing.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I just looked. We use must a lot more than shall. I'd prefer must also, since shall seems overly formal in English. I'll file an issue to make these consistent.

Copy link
Collaborator

@m-mohr m-mohr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, but a proposal regarding the wording.

@philvarner philvarner merged commit 137502e into radiantearth:dev Mar 4, 2022
@philvarner philvarner deleted the children-reflect-root-child-links branch March 4, 2022 01:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants