Support for version 0.5 of OME-Zarr

[dstansby]

This is an issue to track implementing version 0.5 of the spec. The plan is to open several sub-issues to track changes that need to be made.

• zarr-python 3 zarr-developers/pydantic-zarr#33
• Add the "ome" field to all attribute data models #89
• Check that zarr dimension names match axes names #90
• Stop validating omero data structure (?) #91
• New labels metadata #92
• Enforce plate metadata version #93

[will-moore]

Hi @dstansby - I was just testing a tool to generate TypeScript types from Pydantic - see https://github.com/marketplace/actions/pydantic-to-typescript

When I ran it on the _v05 classes...

$ pydantic2ts --module src/ome_zarr_models/_v05/image.py --output image05.ts

It gave me a Multiscale with version?: "0.4" | null; and I also don't see the "version": "0.5" which is required on ImageAttrs I think?

Apologies if this is already on your radar but I didn't recognise it in the issues above. Thanks.

/**
 * Model for the metadata of OME-Zarr data.
 *
 * See https://ngff.openmicroscopy.org/0.4/#image-layout.
 */
export interface ImageAttrs {
  /**
   * The multiscale datasets for this image
   *
   * @minItems 1
   */
  multiscales: [Multiscale, ...Multiscale[]];
  omero?: Omero | null;
  [k: string]: unknown;
}
/**
 * An element of multiscales metadata.
 */
export interface Multiscale {
  axes: Axis[];
  /**
   * @minItems 1
   */
  datasets: [Dataset, ...Dataset[]];
  version?: "0.4" | null;
  coordinateTransformations?: [unknown] | [unknown, unknown] | null;
  metadata?: {
    [k: string]: unknown;
  };
  name?: JsonValue | null;
  type?: {
    [k: string]: unknown;
  };
  [k: string]: unknown;
}

[dstansby]

Thanks - I opened a new issue because that makes it a bit easier to keep track fixing.