2026 09 23

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

Attendees:

• Chris Little, Met Office
• Mark Burgoyne, Met Office
• Paul Hershberg, NOAA NWS
• Adam Warde, ECMWF

Apologies:

• Tom Kralidis, MSC
• Jon Blower, NOC
• Shane Mill, NOAA NWS
• Tiago Qintino, ECMWF

Agenda:

Progress, including previous actions

Pull Requests - None [but just updated title page with dates and revision number] [PMN - corrected V1.0.1 schema error]

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 seems compatible and recognises Workflows needed to allow the build of Draft-07, 2019 or 2020 dialects and 2020 dialect tested., [Agreed that when workflow to bundle schema is working, bundles in the repo would be named coveragejson-_dialect_.json.
• V1.1 Additional dimensions one only or n generalised as in EDR, Common Part 2 and Coverages APIs [To be discussed at future meetings]
• V1.1 Additional dimensions may cause problems with validating responses. Additional dimensions are already allowed, but not validated.

ACTIONS:

• V1.0.1 Adam previously agreed to create workflow to build schema bundle [DONE, schema error spotted. Now seems to work]
• V1.0.1 All agreed ready for formal approval. [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 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. [tbd]

Alignments:

• V1.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 7 Oct 2026, 15:00 UTC (09:00 MDT, 11:00 EDT, 16:00 BST, 17:00 CEST, 23:00 CST, Thurs 01:00 AET)