2026 10 22

CoverageJSON Community Meeting, 2026-10-22, Wednesday, 15:00 UTC (09:00 MDT, 11:00 EDT, 16:00 GMT, 17:00 CET, 23:00 CST, Thurs 01:00 AET)

Attendees:

• Chris Little, Met Office

Apologies: *

Agenda:

Progress, including previous actions

Pull Requests - None

Issues

• The JSON Schema is a build of the Draft-07 dialect. Other dialects are needed, especially 2020-12 for compatibility with OpenAPI 3.1. The current work in IETF on JSON Schema standardisation seems compatible. Repo workflow allows the build of Draft-07, 2019 or 2020 dialects, named coveragejson-dialect.json. 2020 dialect has been tested by @mrauhala.
• V1.1 Additional dimensions one only or n generalised as in EDR, Common Part 2 and Coverages APIs.
• V1.1 Additional dimensions may cause problems with validating responses. Additional dimensions are already allowed, but not validated.

ACTIONS:

• V1.0.1 Create 2020 dialect JSON Schema bundle [tbd]
• V1.0.1 Posted to Pending, Scott requested for formal vote with 45 day review period.
• V1.1 Jerome will demonstrate an easily built client with support for multiple extra dimensions [tbd]
• V1.1 Agreed that any added generic dimensions could be for a new Domain DataCube only, rather than all pre-defined Domain types, such as Grid. Some limited schema checking can then be done.
• V1.1 Mark will open issues and develop a PR for the preferred, simpler option to add a single extra dimension e("extra" or "ensemble") Should be straightforward to add to each of existing pre-defined Domain types. Domain Types allow stricter and easier schema checking than more generic dimensions. [tbd]

Alignments:

• V1.0.1 and OpenAPI V3.1 needed for consistency with API-EDR Part 1: Core V1.2, which is now published.

Any Other Business:

Date of Next Meeting: Wed 4 Nov 2026, 16:00 UTC (09:00 MDT, 11:00 EDT, 16:00 GMT, 17:00 CET, Thurs 00:01 CST, Thurs 03:00 AEDT)