You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I wasn't aware of the requirement that self and root are required for some endpoints (e.g. /collections).
@philvarner has shown that self is required by OAFeat, which is fine. But root itself seems only required by some endpoints which seems inconsistent.
For example, /search doesn't seem to require it. Static STAC also doesn't require it. OAFeat also doesn't require it in /collections. I'm wondering whether it should be more consistent and only be recommended in all endpoints?
More an issue for discussion rather than a request for change. I'm not sure either yet, but would like to see this being somewhat consistent.
My understanding was that root was always required. I think it is an oversight that it's not required by all conformance classes. For a HATEOAS style of web API, I think always having a link back to the root is important.
Features (and thereby Collections) requires it for all endpoint responses require root
Item Search does not list is as a link rel, but the example has it. Planetary Computer (stac-fastapi) has it, Earth Search (stac-server) does not (but I will add it in the next release!).
I would be in favor of adding this to Item Search.
I wasn't aware of the requirement that self and root are required for some endpoints (e.g.
/collections
).@philvarner has shown that self is required by OAFeat, which is fine. But root itself seems only required by some endpoints which seems inconsistent.
For example,
/search
doesn't seem to require it. Static STAC also doesn't require it. OAFeat also doesn't require it in/collections
. I'm wondering whether it should be more consistent and only be recommended in all endpoints?More an issue for discussion rather than a request for change. I'm not sure either yet, but would like to see this being somewhat consistent.
Started by @m-mohr in #331 (comment)
The text was updated successfully, but these errors were encountered: