HTTP(S) supports language negotiation, but at the API resource level. Users of OGC APIs, such as Records and EDR, have requested multiple language versions of some metadata in a single response, typically using IETF BCP47.
Many international standards have adopted such an approach. E.g. see https://raw.githubusercontent.com/w3c/sdw/gh-pages/time/rdf/time.ttl and search for prefLabel.
To ensure interoperability, this should this be part of OGC API-Common, rather than OGC API adopting inconsistent approaches.
HTTP(S) supports language negotiation, but at the API resource level. Users of OGC APIs, such as Records and EDR, have requested multiple language versions of some metadata in a single response, typically using IETF BCP47.
Many international standards have adopted such an approach. E.g. see https://raw.githubusercontent.com/w3c/sdw/gh-pages/time/rdf/time.ttl and search for
prefLabel.To ensure interoperability, this should this be part of OGC API-Common, rather than OGC API adopting inconsistent approaches.