Use s prefix for multiscale example

[mkitti]

There is a tendency to replicate the examples exactly. Having multiscale paths only being a number can be easily confused with chunk paths. Overall, the examples are being interpreted as recommended conventions so we may want to consider the implications of the names used in the examples.

This is a minor change since it just modifies the example without modification to the actual schemas. Having a path that is just a number remains valid. This would also match the existing n5 convention:

https://github.com/saalfeldlab/n5-viewer?tab=readme-ov-file#n5-viewer-metadata

[d-v-b]

related: #277

[will-moore]

Agreed that s prefix is nicer than plain integers.
We should think about adopting this behaviour in ome-zarr-py too.

What about updating the index.html spec page itself? It contains a bunch of places that use plain integer for multiscale paths.

Build failure is Config file not found at default path The required .readthedocs.yaml configuration file was not found at repository's root

[mkitti]

Cc: @StephanPreibisch @tpietzsch

[mkitti]

What about updating the index.html spec page itself? It contains a bunch of places that use plain integer for multiscale paths.

Which index.html is that?

[will-moore]

Ah, it's actually index.bs: e.g.

ngff/index.bs

Line 82 in 8cbba21

├── 0 # Each multiscale level is stored as a separate Zarr array,

"...is often a sequence starting at 0"
I got there by clicking on the "0.5" submodules link from https://github.com/ome/ngff

[mkitti]

@will-moore anything else to do here?

[will-moore]

No blockers to the changes here.
But if this is to be propagated to future copies of the spec, it'll need to be copied over to the new repo at https://github.com/ome/ngff-spec/ where all the 0.6dev changes are happening now (probably after 0.6dev2 is done)

cc @jo-mueller

[jo-mueller]

Thanks for the heads-up @will-moore . Yes, changing it here will mean it'll have to be changed over at ngff-spec, too. Since the change is minor, I think it could be added there already. Otherwise, the order of PRs that would have to go until then would be

#350 --> ome/ngff-spec#17 --> this (and everything else)

[will-moore]

@jo-mueller I'll work on moving this to ngff-spec...

[will-moore]

PR opened: ome/ngff-spec#56

[mkitti]

See also ome/ngff-spec#24

[jo-mueller]

Ugh sorry @will-moore, I had this ported already a while ago and forgot to raise the hand here clearer 😬 My bad!