Alistair Miles

Btw @martindurant I used fsspec here but I didn't use the FSMap class but rolled my own mapper class for now just because to get this working I needed a...

Thanks @martindurant. Just to note that for v3 I need to be able to distinguish between "files" and "directories" in the result. (I.e., I need to know which results are...

> As I do in my PR you have the same check everywhere that when `path === '/'` then there is s different logic to get the key, as there...

> Your implementation still looks rather similar to mine, of course :) Was it not easier to subclass FSMap directly? Probably, was just hacking it together and did the first...

My 2c, the storage spec (1) seems like the main focus at the moment, so we could start by migrating that here. We could then consider adding a codec registry...

On the subject of extensions/conventions, there are also domain-specific extensions (e.g., we have our own conventions for how we store genome variation data in zarr) as well as general-purpose extensions...

One other relevant comment that has come up in discussion, currently the [zarr storage spec](https://zarr.readthedocs.io/en/stable/spec/v2.html) describes how to store data in any system that can exposes a key-value style interface,...

Thanks @constantinpape for raising this, sorry for coming late to the party. Just wanted to xref this issue: https://github.com/zarr-developers/zarr/issues/245 - @jakirkham raised a requirement for the heterogeneous grid (a.k.a., non-uniform...

Thanks @ryan-williams, this is really helpful. One quick comment, I think it helps to make a distinction between protocols and implementations. A protocol is a definition of how data and...

Speaking generally, for any of the examples given above, I imagine that a spec for a protocol extension would ideally include things like: * What problem is this protocol extension...