Finalizing v0.4

[constantinpape]

• MUST DO
  • Finalize axes & transformations Finalize axes & initial transformation #85
  • Update the example data (e.g. in https://github.com/ome/ome-ngff-prototypes) for changes in Finalize axes & initial transformation #85
  • Finalize support in ome-zarr-py/ome-zarr-napari, vizarr coordinateTransformations scale list napari-ome-zarr#32
  • Finalize support in BDV/MoBIE
  • Updates to the HCS spec (cc @sbesson; I am not sure what the current status or related PR is)
  • jsonschema for v0.4 json-schema for v0.4 spec #82
• CAN DO
  • top level version information just one top-level version #83 (Decoupling version numbers of different specifications #47)
  • specify zarr version Specify which zarr version ome.zarr is using #80 PR: Define OME-Zarr and add Zarr v2 requirement #88
  • specify encoding in json Specify the encoding of the json metadata #81
  • specify purpose of multiple multiscales Multiscales questions #17
• POST-RELEASE: write up a quick summary about how to contribute a spec extension (PR & release process)

Decided to push to next release:

• Origin definition Define the origin w.r.t. the pixel corner or center #89, see Define the origin w.r.t. the pixel corner or center #89 (comment)

Timeline: I will work on this next week during the hackathon and hope that we can release in the next 2 weeks or so.

[sbesson]

@constantinpape for the HCS point, I'll review the recording of the evening session for the 6th NGFFcommunity call as I missed it. In the absence of vetoes, the next step will be to merge #24

[constantinpape]

See also ome/ome-ngff-prototypes#2 for updating the example data

[constantinpape]

I have updated the example data now, see https://github.com/ome/ome-ngff-prototypes#data-availability.
So now the only important thing left to do is to get the viewers up to speed ... I will ping the MoBIE side about this.

How's the progress on this in python/napari and vizarr, @sbesson @will-moore?

And do you still want to merge #92 before we release @sbesson? I would suggest to leave the other open points for the next minor release, or an intermediate patch release.

[constantinpape]

I just found this old issue, which is still relevant: #2
A good candidate for a patch release. (Just linking it here for visibility)

[sbesson]

And do you still want to merge #92 before we release @sbesson?

Although I suspect this particular PR might be merged soon, I would not consider this as a blocker for the specification release and rather mark it as a CAN DO item. Overall, there is still some work to perform on these JSON schemas including improving the checks in the strict image schemas (units), adding schemas for other specifications (plate, well). I suspect this will be broken out into PRs/issues and continue after the 0.4.0 release.

[sbesson]

https://ngff.openmicroscopy.org/0.4/ is now live 🎉

[constantinpape]

Thanks @sbesson. I will follow up here later today.

[constantinpape]

Hey @sbesson @will-moore @joshmoore,
just a quick follow-up on this from my side: we can read v0.4 in MoBIE now and are still working on writing it. Will hopefully be finished this week and then we will make a new release that fully supports 0.4. (I tentatively marked MoBIE as done now;))
How is the progress on support in napari/vizarr?

I have also moved the minor points to #100, since this will not be part of 0.4.

[will-moore]

PR for 0.4 support in napari is merged (ome/napari-ome-zarr#32), but we still need to release.
Vizarr is done, but that only involved the handling of axis names since it doesn't support scalebar or transformations yet.

[constantinpape]

PR for 0.4 support in napari is merged (ome/napari-ome-zarr#32), but we still need to release.

Great!

Vizarr is done, but that only involved the handling of axis names since it doesn't support scalebar or transformations yet.

Ok, that sounds like it would be a separate effort to integrate, so I suggest to go ahead without waiting for this.
Do we also need a new vizarr release to support reading 0.4?