In opengeospatial/ogcapi-features#404, preparations have been made to support OpenAPI v3.1 in the next API Features release (v1.1). Since the JSON schemas already reflect the changes for v3.1, the current example document reports several violations (nullable: true instead of type: null).
Therefore, it would be nice to support both the OAS 3.0 & 3.1 requirements classes, plus any other changes in API Features v1.1.
Related to opengeospatial/ogcapi-features#958.
In opengeospatial/ogcapi-features#404, preparations have been made to support OpenAPI v3.1 in the next API Features release (v1.1). Since the JSON schemas already reflect the changes for v3.1, the current example document reports several violations (
nullable: trueinstead oftype: null).Therefore, it would be nice to support both the OAS 3.0 & 3.1 requirements classes, plus any other changes in API Features v1.1.
Related to opengeospatial/ogcapi-features#958.