Follow HTTP Link Hints?

[m-mohr]

We have drafted our own Link extensions for the search extension, for example, to add "method": "POST" to links.

@cportele recently made me aware of HTTP Link Hints:

If we want to extend the link object, then we should consider to follow the HTTP Link Hints proposal: https://mnot.github.io/I-D/draft-nottingham-link-hint.html

We should take that into account for the next iteration, especially in case the OGC decided to adopt this.
Therefore we should follow opengeospatial/ogcapi-common#179

[philvarner]

I had not seen that standard before. It looks great -- I've solved this same issue in several different ways in different APIs I've done, that standard seems like it handles this well.

Also, this would be backwards-compatible with out existing scheme, since the name of the property is _links.

[m-mohr]

I was only referring to the hints themselves, not the whole structure. We would inherit this from OGC APIs anyway and they use our link structure, but think about adding hints. See the issue above.