Should not allow a path to simultaneously be a Zarr array and a Zarr group?

[krisfed]

Looks like currently something like this is allowed:

>> zarrcreate("myzarr.zarr/A/B/C", [100,100])
>> zarrcreate("myzarr.zarr/A/B/C/D", [100,100])

Here path "myzarr.zarr/A/B/C" should represent a Zarr array (contain .zarray file). From my understanding, writing a Zarr array in "myzarr.zarr/A/B/C/D" should not be allowed (it would be treating "myzarr.zarr/A/B/C" as a group instead of an array)?

Similarly if "myzarr.zarr/A/B/C" is a Zarr group (contains .zgroup file), then I think the following should not be allowed:

>> zarrcreate("myzarr.zarr/A/B/C", [100,100])

as it would be treating "myzarr.zarr/A/B/C" path as both a Zarr array and a Zarr group.

Not 100% sure if my understanding of the Zarr spec is correct though...