Davis Bennett

@MSanKeys963 yes!

how can we move forward with this? I think it's important to make these changes quickly, before we get skew between implementations.

> @d-v-b: do you want to take a look at the conflict? done!

> I think we could stand to be more opinionated here and require that the config is kept in its own sub-object: this avoids name collisions and keeps everything together....

Why should conventional zarr hierarchies be responsible for expressing which conventions they adhere to? (This amounts to the question of why nominal, rather than structural, typing is the right solution...

I'm not too familiar with the OLAP conceptualization, but I tend to think of the N-dimensional array API as a special case of a table, where 1 column contains numeric...

>> since Zarr doesn't have good support for variable-length types. > > Can you explain this a bit more? Would this be like string or varchar support? Zarr is designed...

> The question is: suppose I want to have two arrays of type "datetime", Do I need to repeat the above declaration in each array? Yes, because in principle the...

I'm not sure if the spec can be authoritative on how applications should handle cases outside "chunk exists" and "chunk does not exist" In the case of missing chunks, the...

previous discussion: https://github.com/zarr-developers/zarr-specs/issues/184