# oztest cases that yaozarrs does not pass, and the status each one gets, as of the
# commit pinned in the justfile.  Format: `<status> <slug>`.

# Questionable case: `image-label` without `multiscales` isn't a label image here.
fail  parse_attributes/v0.4/core/valid/label/minimal
fail  parse_attributes/v0.4/core/valid/label/minimal_properties
fail  parse_attributes/v0.5/core/valid/label/minimal
fail  parse_attributes/v0.5/core/valid/label/minimal_properties
fail  parse_attributes/v0.6/core/valid/label/minimal
fail  parse_attributes/v0.6/core/valid/label/minimal_properties

# Questionable case: identical files, and it's unclear what makes them invalid.
fail  parse_attributes/v0.6/core/invalid/image/invalid_multiscale_transform_output
fail  parse_attributes/v0.6/core/invalid/image/invalid_multiscale_transform_input_output

# Questionable case: the vector field's multiscale has 3 axes (vector, y, x) but a
# 2-value `scale`, which breaks "MUST equal the length of the `scale` array".  The
# spec's own example (examples/transformations/displacements/displacement_field.json)
# does the same.
fail  validate_zarr/v0.6/transform_coordinates/valid/transforms/coordinates
fail  validate_zarr/v0.6/transform_coordinates/valid/transforms/coordinates_interp
fail  validate_zarr/v0.6/transform_displacements/valid/transforms/displacements
fail  validate_zarr/v0.6/transform_displacements/valid/transforms/displacements_interp

# Policy: the `strict` profile uses the strict schemas, which make SHOULD fields
# required (acquisition `name`/`maximumfieldcount`, plate `name`, and in v0.4 the
# plate/well `version`).  A missing SHOULD field isn't an error here.
fail  parse_attributes/v0.4/strict/invalid/plate/missing_acquisition_maximumfieldcount
fail  parse_attributes/v0.4/strict/invalid/plate/missing_acquisition_name
fail  parse_attributes/v0.4/strict/invalid/plate/missing_name
fail  parse_attributes/v0.4/strict/invalid/plate/missing_version
fail  parse_attributes/v0.4/strict/invalid/well/missing_version
fail  parse_attributes/v0.5/strict/invalid/plate/missing_acquisition_maximumfieldcount
fail  parse_attributes/v0.5/strict/invalid/plate/missing_acquisition_name
fail  parse_attributes/v0.5/strict/invalid/plate/missing_name
fail  parse_attributes/v0.6/strict/invalid/plate/missing_acquisition_maximumfieldcount
fail  parse_attributes/v0.6/strict/invalid/plate/missing_acquisition_name
fail  parse_attributes/v0.6/strict/invalid/plate/missing_name

# Questionable case: dataset `path: "1"` with `input.path: "s1"` (a half-done rename;
# the spec's published example uses "s1" for both), which breaks "The `input` object
# MUST specify a `path` field matching the `path` field of the dataset".
fail  parse_attributes/v0.6/strict/valid/image/multiscales_example
