ome
RFC5: not clear what the scope of unique transform names is
Under "coordinateTransformations metadata" RFC5 currently says:
MAY contain the field “name” (string). Its value MUST be unique across all “name” fields for coordinate transformations.
It's not clear to me how to interpret 'across all “name” fields for coordinate transformations', ie what is the scope of all coordinate transformations. My guess would be this is intended to be scoped to individual OME-Zarr groups:
'across all "name" fields for coordinate transformations in any one OME-Zarr group.
or similar, since there are examples in the official set of examples for RFC5 that have a coordinate system called "physical" in more than one OME-Zarr group in the same hierarchy.
since there are examples in the official set of examples for RFC5 that have a coordinate system called "physical" in more than one OME-Zarr group in the same hierarchy.
True, but that's coordinateSystems, not coordinateTransformations. I think that you are right with the scope being the individual ome-zarr group. Otherwise, choosing generic names (i.e., scale0_to_physical) would be overly restricted.
True, but that's coordinateSystems, not coordinateTransformations.
Ah of course! Maybe it would be worth putting in a similar statement about sytems too (if there isn't one already)?
👍 to scoping transform names to individual groups too.