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
The approach to represent hyperlinks in JSON is unfortunately different from the encoding
proposed by OGC 14-055r2 which means that an OpenSearch implementation based simultaneously on OGC 14-055r2 and OGC 17-047 in combination with OGC API Common will have different encodings for links in search responses and in other resource representations (e.g. /conformance, /etc).
The text was updated successfully, but these errors were encountered:
Spacebel comment from the API Hackathon ER
The approach to represent hyperlinks in JSON is unfortunately different from the encoding
proposed by OGC 14-055r2 which means that an OpenSearch implementation based simultaneously on OGC 14-055r2 and OGC 17-047 in combination with OGC API Common will have different encodings for links in search responses and in other resource representations (e.g. /conformance, /etc).
The text was updated successfully, but these errors were encountered: