Josh Moore

See discussion in https://github.com/Unidata/netcdf-c/issues/2474 which suggests as part of this effort (and ASAP e.g. v0.5 if not retroactively for the previous versions) _ARRAY_DIMENSIONS should be moved into the individual xarray-compatible...

Hey Lee! Good to hear from you. Short answer is capturing all the content of the OME-XML model in the Zarr (though likely in JSON rather than XML) is definitely...

So this issue has come up again recently with the interest from the aicsimageio team (cc: @jacksonmaxfield) of starting to consume the `METADATA.ome.xml` file from `bioformats2raw` sooner rather than later....

Copying an update from https://github.com/zarr-developers/zarr-specs/issues/112 that the most likely interpretation of additional files will would enable under Option 1.

Note: a related conversation is ongoing under "NCZarr - Netcdf Support for Zarr" (https://github.com/zarr-developers/zarr-specs/issues/41), especially relevant regarding situations where we might want to join together two or more specs (here,...

see also: https://github.com/ome/ngff/issues/104

If we can balance that with readability and maintainability, :+1: (To some extent, it'd be nice if ome_zarr_test_suite would _generate_ that matrix, but *shrugs*)

@sbesson has started working on a feature-level matrix for this. It's likely "too much" for the index.bs file itself and may end up in its own repo.

> This type of dimension correspondence is easily expressed in the netcdf data model, but the current proposal does not seem to allow that :+1: for compatibility with the NC...

Agreed. Sounds like a "style-guide" section. There is likely something within bikeshed itself, e.g. https://tabatkins.github.io/bikeshed/#dfn-types but I don't know if if it's use will be too verbose. Failing finding a...