Alistair Miles

Also relevant here, [documentation of xarray zarr encoding conventions](http://xarray.pydata.org/en/latest/internals.html#zarr-encoding-specification), thanks @rabernat.

> 1. zarr makes a distinction between _hierarchies_ and _groups_. I am not quite certain if there is a difference. The way I read the spec, having nested datasets is...

> * zarr: supports `C` and `F` indexing, which determines how chunks are indexed and how chunks are stored. This is determined via the key `order`. In zarr, the "C"...

Endianness is important given data may be produced on one system and consumed on another. I don't know of any cases where endianness differs between different arrays in the same...

> * zarr: chunks are stored _flat_ by `.` seperated keys, e.g. `2.4`. I think somewhere @alimanfoo mentioned that zarr also supports nested chunks, but I can't find this in...

Many thanks @constantinpape, great summary. Hopefully comments have clarified a few points, but very happy to expand on any areas.

Thanks @jrbourbeau for reviving this. Just a short technical note, there are at least two possible scenarios here, when a compressor is involved. 1. One scenario is when the whole...

Just to say that the [v3 core protocol](https://zarr-specs.readthedocs.io/en/core-protocol-v3.0-dev/protocol/core/v3.0.html) currently includes the concepts of data type, array shape, chunk shape, chunk memory layout, array metadata. I imagine that protocol extensions can...

Hi @Carreau, > I'm trying to understand the reasoning, choices and trade-off made when the DirectoryStore on disk layout was created. > > As far as I can tell it...

> Thinking out loud, but I wonder if it would be better to deal with this within the v3 core protocol **above** the layer of the store interface. In other...