Josh Moore

Testing to see if a re-open will re-generate the comment (after f5c1193ed011e28be8c2019fad5c1f810b78b640)

One more time (from 3f10889bb30511b70b973ca6d483368e411d863a)

Should be ok to give it a try, @will-moore.

No, the comments get updated in place. Moving forward, it should be the first comment on a PR directly under the description.

As we move towards a merging of this work, it might be worth also considering @melissalinkert's https://github.com/melissalinkert/ngff/commit/056b4e905a0edfaa275fd352888f5b7edd410adb (on top of this PR). It proactively adds a feature that's currently needed...

Followed the cherry-pick strategy from above but updated the semantics to be more permissive of missing "series" indices. cc: @melissalinkert

Thanks for the feedback, @will-moore! Changes pushed.

Likely a last call for comments here. I'm going to move on to the various PRs: - [x] https://github.com/ome/ZarrReader/pull/31 - [x] https://github.com/glencoesoftware/bioformats2raw/pull/157 - [x] https://github.com/ome/ome-ngff-validator/pull/13 - [ ] https://github.com/ome/ome-zarr-py/pull/174 -...

> Is the proposal still to port this transitional metadata specification only to the current stable 0.4 specification? Yes. I'll do once all edits are made (Hopefully this morning).

From my POV, I think we are ready to move forward with this PR as well as the bioformats2raw PR itself. Python I think will follow _relatively_ quickly and then...