Jeremy Maitin-Shepard

@normanrz Please take a look.

Agreed that this should be separate from ZEP 1. I should update this document to not mention ZEP 1. But perhaps there should be a lighter weight process --- it...

This proposal doesn't indicate a default compression level if `level` is unspecified --- the `level` parameter is intended to be required, though I should clarify that. When creating an array,...

Default values are only really needed to support evolving the spec. Default values in the initial version of the spec basically just serve to save space in the stored metadata,...

We could permit the parameters to be left unspecified in the metadata if only read operations are performed, and fail if any write operations are performed. However it is not...

> > A few points that I think need to be addressed: > > > > * Specifying cropping and other coordinate transforms (see https://google.github.io/tensorstore/index_space.html#index-transform for inspiration) > > URL...

> Q: Should `"chunk_shape"` be inferred by readers, or written out explicitly like in [ZEP003](https://github.com/zarr-developers/zeps/blob/main/draft/ZEP0003.md)? In tensorstore it is inferred, but for each array in the stack it is required...

> > Is this question regarding URL syntax? > > No I meant I don't understand the context of the coordinate transform stuff. I'm not sure how the concatenation would...

> Thanks for all this quick feedback @jbms ! > > > However, I would suggest considering the tensorstore approach of "layers" with arbitrary coordinate transformations instead of concatenation. Just...

> > n tensorstore, [index transforms](https://google.github.io/tensorstore/index_space.html#index-transform) provide a relatively compact json representation of any combination of: > > So when implemented, the original proposal above implies that implementations might want...