Skip to content

Commit 8dc7796

Browse files
committed
Add feedback from ZSC
1 parent 6c1a027 commit 8dc7796

File tree

1 file changed

+10
-2
lines changed

1 file changed

+10
-2
lines changed

docs/v3/core/index.rst

Lines changed: 10 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1593,6 +1593,9 @@ by only lower case letters a-z, numerals 0-9, underscores, dots and dashes.
15931593
backwards compatibility with existing extensions, URIs names are still
15941594
permitted.
15951595

1596+
A proposal to additionally support multiple registration mechanisms is under
1597+
discussion in https://github.com/zarr-developers/zarr-specs/pull/330 .
1598+
15961599
.. _extension-guidance:
15971600

15981601
Guidance for extension authors
@@ -1605,9 +1608,14 @@ The Zarr maintainers endeavor to make the registration of names as
16051608
straight-forward as possible. We encourage all authors to make use of the extensions
16061609
repository to prevent duplicate efforts across the community where possible.
16071610

1608-
* **Well-known extensions**: If you are implementing a well-known extension
1611+
* **During development**: Authors should use whatever name makes sense
1612+
for their extension, provided it is not already reserved in the registry.
1613+
Once there is a working implementation of the extension (e.g. a PR to an
1614+
existing Zarr implementation), the extension should be submitted to the registry.
1615+
1616+
* **Well-known extensions**: Authors implementing a well-known extension
16091617
like a data type or codec that is already referred to by name in the
1610-
community, you may want to check the `zarr-extensions`_ repository to see if
1618+
community may want to check the `zarr-extensions`_ repository to see if
16111619
someone has already implemented the extension.
16121620

16131621
* **Production extensions**: Authors intending to create significant amounts of

0 commit comments

Comments
 (0)