Skip to content
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

clarify that the abstract store api is not normative #308

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

jhamman
Copy link
Member

@jhamman jhamman commented Aug 21, 2024

closes #307

@LDeakin
Copy link

LDeakin commented Aug 21, 2024

This would also close #266

@@ -1273,6 +1271,8 @@ when opening a Zarr hierarchy to automatically determine the appropriate store.
Abstract store interface
------------------------

(This subsection is not normative.)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I feel like this could be a lot clearer, e.g:

Suggested change
(This subsection is not normative.)
(This subsection is not normative. It is intended only as a recommendation for API design, but does not need to be strictly followed like the specification for the on-disk storage does.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Abstract store interface should be clarified as descriptive, not normative
4 participants