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.

Sign up for GitHub

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 3 commits into
base: main
Choose a base branch
from
Open

clarify that the abstract store api is not normative #308

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
ce740aa
clarify that the abstract store api is not normative
jhamman Aug 21, 2024
10e08be
remove language about store implementation requirements
jhamman Aug 22, 2024
f6cbfb7
Update docs/v3/core/v3.0.rst
jhamman Dec 16, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions docs/v3/core/v3.0.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1258,9 +1258,7 @@ Stores
======

A Zarr store is a system that can be used to store and retrieve data
from a Zarr hierarchy. For a store to be compatible with this
specification, it must support a set of operations defined in the `Abstract store
interface`_ subsection. The store interface can be implemented using a
from a Zarr hierarchy. The store interface can be implemented using a
variety of underlying storage technologies, described in the
subsection on `Store implementations`_.

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

(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.)

The store interface is intended to be simple to implement using a
variety of different underlying storage technologies. It is defined in
a general way here, but it should be straightforward to translate into
Expand Down