Edward Slavich

CRDS doesn't return meaningful error codes (255 is used for all fatal errors). We'll need to see the output of that process to troubleshoot the problem. Run the same command...

I'm concerned about the impact this will have on interoperability with ASDF readers in other languages. General support for numcodecs compression is convenient for Python developers, but someone working in...

Re metadata in the block vs the tree: I can see arguments for both. The ndarray objects in the tree are views over the block data, and we support multiple...

> Does anything prevent a second level, variable-length prefix? The id in the block header can indicate that there is a prefix to the data in the data section, the...

Another option is to require the custom compressor to be configured at the file level. Then, any blocks in the file with `cust` would have to be compressed with the...

Of the options so far, I find the variable length block header field the most appealing. It's nice to let the plugin format the metadata however it wishes, and headers...

> Just so I understand, is the 2 bytes to indicate the length of the header (i.e. up to 64K)? Or something else? Yes, if I understand @perrygreenfield's idea correctly....

If the library sees multiple compression plugins installed, how would it determine which one to use? Or would users only be permitted to install one at a time? I suppose...

I like this idea a lot! We actually have a situation where extensions across multiple packages depend on one another, and updating a tag lower down in the dependency tree...

Looking at the other JSON schema features, it seems that regular expressions are the pattern matching tool of choice. For example: https://json-schema.org/draft/2019-09/json-schema-validation.html#rfc.section.6.3.3 https://json-schema.org/draft/2019-09/json-schema-core.html#rfc.section.9.3.2.2 and some general guidance on how to...