Jeremy Maitin-Shepard

https://zarr-specs.readthedocs.io/en/latest/v3/core/v3.0.html#node-names We basically leave it up to the underlying store.

Would it be sufficient for your implementation to just impose some additional semantics and constraints on dimension names? For example, you could require that if the same name is used...

Regarding the zarr spec: The zarr v2 spec does not mention stores at all --- and in practice the supported stores vary greatly between implementations. In zarr v3 there may...

I took a look at your zip file --- the issue is that your chunks are way too small for efficient access or storage. Some of your chunks contain just...

No, the hex string always has the sign bit as the most significant bit (i.e. first) and does not depend on endianness. Perhaps you can create a PR to clarify.

> Is that an implementation detail of the C function referenced in the spec? No, and actually the warning about `strtod` was in relation to the NaN syntax `nan(1234)` that...

> Writing the PR using this language > > > where the first (most significant) bit is the sign bit, followed by the exponent bits, followed by the mantissa bits...

Note that an IEEE 754 NaN value is indicated by any sign bit, all 1 exponent bits, and any non-zero mantissa. By specifying the sign and mantissa we fully specify...

When it can be determined independent of the data, just based on e.g. shapes, implementations can already (and do already) do this. Some compression codecs also store the decoded size....

> For an example of a community that has successfully used semver in a spec with multiple implementations, check out STAC: https://github.com/radiantearth/stac-spec/blob/master/process.md Can you provide some pointers to examples of...