All profiles will require the service to be described by OpenAPI

[havardf]

Each service that conforms to one of the RODEO profiles must be described by OpenAPI 3.0 or higher.

Which means:

• it must have a link with rel service-desc to the openapi file in the landingpage.
• All collections in the service needs to be compliant with that openapi description.

E.g snippet from landingpage:

 {
      "href": "https://example.com/openapi.json",
      "rel": "service-desc",
      "type": "application/json",
      "title": "API description in JSON"
  },

Any other requirements? And, how would be best define the requirement about collections beeing compliant to the openapi spec?

[havardf]

I think this one is relatively straightforward, I will create a PR for adding it to the profile.

[havardf]

@tomkralidis I have a couple of questions regarding the standard specification for openapi. 1. There are requirements for OpenAPI already in EDR, albeit not mandatory. Its also described in the OGC-API Common specification? Should we copy and paste, or can we refer to a requiremnts class in another spec?

2. The requirements classes for OpenAPI all specify 3.0. We need to allow for 3.1, and maybe also just 3.0.3 or higher. Are there any previous work on specifying this?

[havardf]

Or, for future proofing, require OpenAPI 3.1 or higher?

The services in RODEO seems already to have adopted 3.1. I am guessing mainly because they use FastAPI and FastAPI probably generate 3.1 by default.

[ways]

Or, for future proofing, require OpenAPI 3.1 or higher?

The services in RODEO seems already to have adopted 3.1. I am guessing mainly because they use FastAPI and FastAPI probably generate 3.1 by default.

We decided in a video meeting to go for >= OpenAPI 3.1.

[ways]

"type": "application/json",

Instead of this we should have a type mentioning openapi.

@tomkralidis What was the correct one?

[tomkralidis]

We should make sure that by supporting OpenAPI 3.1+ (and not OpenAPI 3.0) that this doesn't affect compliance to EDR proper. cc @m-burgoyne for clarification/confirmation.

[tomkralidis]

"type": "application/json",

Instead of this we should have a type mentioning openapi.

@tomkralidis What was the correct one?

application/vnd.oai.openapi+json;version=3.0 (for OpenAPI 3.0).