OEAPI openapi spec bevat niet nieuwe content-type headers

[EdoBoorsma]

SURFeduhub has fully implemented v6 in the sandbox environment as of today, including the delivery of data to RIO.

We have encountered an issue with the validator. In OEAPI v6, Content-Type response headers are expected to use the format Content-Type: application/vnd.oeapi+json;version=6.1. However, the OpenAPI specification currently defines all response media types as application/json. As a result, the validator rejects responses that implement the new format.

Could you please look into this and update the specification accordingly? Also, do you have any indication of how long such a change would be expected to take?

[EdoBoorsma]

@mjvanlieburg @remco-jak

The issue is that OEAPI v6 introduces versioned media types in the Content-Type response header, for example:

Content-Type: application/vnd.oeapi+json;version=6.1

However, the current OpenAPI specification still defines all response media types as application/json. As a result, validators that rely on the specification reject responses that correctly implement the versioned OEAPI media type.

This was inadvertently not included in the v6 specification and should be corrected. We will discuss the proposed change during the upcoming Technical Working Group meeting on Tuesday. Assuming there is agreement, the specification will be updated accordingly. The implementation timeline will depend on the outcome of that discussion and the subsequent release planning.

[EdoBoorsma]

application/json should be replaced with application/vnd.oeapi+json in all endpoints