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
One rule that we are trying to use in defining APIs is that almost all parameters are optional and that there are default behavour for the lack of them
The text was updated successfully, but these errors were encountered:
I would word it slightly differently which is to say that there should be a default response at each endpoint. For example, features at /collection/{collectionId}/items without any parameters returns N features (based on the default value of the limit parameter). This is equivalent to saying that there should be a default value for each parameter but it is slightly different since some parameters may not have defaults defined in the specification.
Also, each response should include a minimum set of links that allow navigation to other parts of the API (e.g. links to the next/prev, link to landing page, link to source collection, alt links, etc.).
One rule that we are trying to use in defining APIs is that almost all parameters are optional and that there are default behavour for the lack of them
The text was updated successfully, but these errors were encountered: