Skip to content

2026 11 18

Chris Little edited this page Nov 5, 2026 · 1 revision

CoverageJSON Community Meeting, 2026-11-18, 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

  • V1.0.1 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.json but in separate folders. 2020 dialect has been tested by @mrauhala in API-EDR context.
  • V1.0.1 onwards The Community Sandbox needs updating with CoverageJSON version or JSON Schema version choice, or rebuilt in OGC GitHub-Pages
  • 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:

  • Scott Simmons will request formal TC vote, 45 day review period
  • V1.1 Jerome will demonstrate an easily built client with support for multiple extra dimensions [tbd]
  • V1.1 PR for adding generic dimensions for Domain DataCube only with some schema checking [tbd]
  • V1.1 PR for a PR to add a single extra dimension e("extra"/"ensemble") and added to each existing pre-defined Domain types, with stricter and easier schema checking than more generic dimensions. [Mark, tbd]

Alignments:

  • Consistent approach to schema bundles needed across APIs.

Any Other Business:

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

Clone this wiki locally