-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
draft blog post #21
base: main
Are you sure you want to change the base?
draft blog post #21
Conversation
intermediary groups. | ||
|
||
- Zarr V3 has an explicit root, while v2 roots and groups could not be | ||
distinguished. This mean that you can only open a zarr v3 at a specific |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This was one of the first things that readers commented on to me. I wonder if the implementation details could discuss walking up the implicit hierarchy to detect the root a la git?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've clarified; having a single root is a spec difference, automatically finding the root is an implementation and user convenience. The core function can perfectly refuse to open a non-root, but the user exposed one can do all the magic they want.
In the same way that right now a store can be just a string that start with s3://
and will converted to an actual Store()
Co-authored-by: Josh Moore <j.a.moore@dundee.ac.uk>
@MSanKeys963 : thoughts on resurrecting this? |
I can see using some parts of this draft for my next blog post on Zarr v3 spec. |
Whatever works best. |
No description provided.