-
Notifications
You must be signed in to change notification settings - Fork 28
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
Abstract store interface should be clarified as descriptive, not normative #307
Comments
the normativity of that section also stood out to me. I don't know why we need normativity here; in fact, it's probably healthy to allow different implementations to use whatever internal APIs seem appropriate. If there is a "right way" to implement zarr, then it can probably only be discovered empirically (and I doubt there is a "right way"). |
FWIW the wording is strong:
|
Agreed that this is not intended to specify the actual API in any implementation. |
I would like to understand why the spec includes a Abstract store interface section and ask if this section should be clarified as descriptive, not normative.
Why should the spec care what interface and implementation chooses for the Store abstraction? So long as the store does the right thing, surely the implementation is free to choose a different abstract interface?
The text was updated successfully, but these errors were encountered: