I 36 Update specification to OpenAPI 3.1

Description

Update the specification to OpenAPI 3.1.

Owner

• Gantert Clemens(DB)
• Schlapbach Andreas (SBB)
• Selleslagh Nicolas (BENE)

Business Value

Using OpenAPI 3.1 assures that we do not invest in outdated standard.

Business Outcomes

*The measurable benefits that the business can anticipate if the epic hypothesis is proven to be correct.3

Supporting the latest version of OpenAPI 3.1 avoids that we have to upgrade later with high efforts.

Leading Indicators

The early measures that will help predict the business outcome hypothesis.

The first implementations of the OSDM specification will use OpenAPI 3.1.

Nonfunctional Requirements

Nonfunctional requirements (NFRs) associated with the epic.

None

Context

The changes are defined here: https://noti.st/lornajane/YRdDlZ/whats-new-in-openapi-specification-3-1

Specification Effort: EXTRA SMALL