Josh Moore

Is the base branch here intended to be `main`?

:+1: np

> regardless of whether `zarr_extensions` is used, you'll end up with a similar metadata document for a Group. I'm not particularly (at all) familiar with the design decisions of STAC...

``` diff --git a/src/zarr/common.py b/src/zarr/common.py index 342db141..1534fa16 100644 --- a/src/zarr/common.py +++ b/src/zarr/common.py @@ -127,6 +127,7 @@ def parse_named_configuration( if "configuration" in data: configuration_parsed = parse_configuration(data["configuration"]) elif require_configuration: + return name_parsed,...

The same testing for https://github.com/zarr-developers/zarr-python/issues/2029 applies: * this error was occurring with 3.0.0a0 * but *not* with 3.0.0b1 :tada:

@d-v-b: I also don't remember an explicit examination of the impact of this, but more that there was a general drive to unify the extensions mechanism. Of course it's not...

I don't know of anything off-hand in Python-land. We do have this in Java between various models (Bio-Formats, OME, OMERO, etc.) It might be that this is a package we...

cc @jhamman for where this is related to the refactoring WG.

Hmmm .... looks like this is true for all of the extensions. They point to the extension table which then links to the individual lists.

I'd certainly prefer a PR with all of them. :+1: I was going to just add to #362 but then realized that it needed more cross-checking / linking so held...