Compression and filters as properties of chunk instead of variable

It is possible that different netCDF/HDF5 files have different variable configuration. For example, for https://s3.amazonaws.com/era5-pds/2021/05/data/air_pressure_at_mean_sea_level.nc, time0 is contiguous but for https://s3.amazonaws.com/era5-pds/2021/01/data/air_pressure_at_mean_sea_level.nc it is chunked.

Although it is easy to simulate chunks from a contiguous variable, when setting the time0/.zattrs properties, filters and compression will affect variables with different configurations and produce an error.

Would it be possible to implement compression and filters as properties of chunks instead of variables? It would be something like:

{
  ".zgroup": "{\n    \"zarr_format\": 2\n}",
  ".zattrs": "{\n    \"Conventions\": \"UGRID-0.9.0\n\"}",
  "x/.zattrs": "{\n    \"_ARRAY_DIMENSIONS\": [\n        \"node\"\n ...",
  "x/.zarray": "{\n    \"chunks\": [\n        9228245\n    ],\n   \"dtype\": \"<f8\",\n  ...",
  "x/0": {
    "store": "s3://bucket/path/file.nc",
    "location": 294094376,
    "size": 73825960,
    "compressor": {...},
    "filters": [...]
  }
}

Example files:

https://s3.amazonaws.com/era5-pds/2021/06/data/air_pressure_at_mean_sea_level.nc
https://s3.amazonaws.com/era5-pds/2021/07/data/air_pressure_at_mean_sea_level.nc

No repository files, tests, or entry points are named. Start by tracing how variable .zattrs/.zarray metadata and chunk locations are generated, then verify that files with differing chunk compression and filters can be represented without configuration errors.