Clarify version field

[d-v-b]

For the various metadata objects with a version field, this PR makes explicit that version is a string, and that it must be the current version.

[github-actions]

Automated Review URLs

• Readthedocs
• render latest/index.bs
• diff latest modified

[normanrz]

I wonder if you'd want to integrate that with #206?

[d-v-b]

Definitely. I see that you are building on #138 -- is there a timeline for getting that finalized (it's been nearly a year)?

[joshmoore]

is there a timeline for getting that finalized (it's been nearly a year)?

Let's not start that discussion on this thread. Unless there's a major change in priorities, the next major version (0.5) would include transforms and so it makes sense for @normanrz to be building on top of it since the bump to Zarr v3 will need to be its own major version. If you'd still like to target this earlier then I'd suggest not building on top of #206, but 👍 for having them work together to prevent unnecessary churn.

[d-v-b]

I think the changes here are essentially a patch to the latest version of the spec? So I'm not sure what I should build off other than main?

[joshmoore]

Agreed.

[normanrz]

This is now clarified in 0.5

The version of the OME-Zarr Metadata is denoted as a string in the version attribute within the ome namespace.