Fix openapi examples in extent and edr-geojson

[havardf]

Adjust examples in the OpenAPI description so they match the schemas.

[chris-little]

Looks good to me. Thank you @havardf

[m-burgoyne]

I have modified the file to add the missing [].

[havardf]

I have modified the file to add the missing [].

I dont think that is quite correct, but I might be wrong of course. This - [[-180, -90, 180, 90]] will result in a: array of array of array of numbers, since the outer - is yaml syntax for creating an array, in addition to the [] syntax. Maybe it would be better use either - or [], rather than a mix?

[m-burgoyne]

The section is intended to show an array of example values

[havardf]

The section is intended to show an array of example values

Right, ok. But as I understand it, it is not allowed in the OpenAPI standard to use the example field to provide a list of examples. The type of example has to match the schema it is part of. There is the examples, which is a map of multiple examples, but that one seems to be allowed only in parameter and response objects.

[m-burgoyne]

And it looks like example has been deprecated as part of OpenAPI 3.1; JSON schema uses examples instead so all of the example values in the EDR schema will need to be reviewed. The errors you have identified are probably best fixed as part of the update for v1.2

[havardf]

Nice, the changes for examples in 3.1 seems very useful, and as far as I can tell, it will make it possible to do what you already have now :) It would be great to have this 3.1 version of the openapi soonish, I mean even as a draft version as part of ongoing work for v1.2.

[chris-little]

EDR API SWG 2024-12-05 agreed to fix as part of OpenAPI V3.1 support