Add a recommendation (SHOULD) for the use of the `.ome.zarr` suffix
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- python
- Domain
- data, documentation
Research direction
Read the specification section that describes how OME-Zarr stores are identified, along with the transferred discussion in issue #228. Decide where the suffix recommendation belongs and how it should be phrased as a SHOULD. Done means the spec recommends .ome.zarr while retaining the stated identification by the ome attribute.
Written by the indexing model from the issue text.
Description
This is transferred from
- #228
While the answer for the the original question is that an OME-Zarr is identifiable by the presence of an "ome" attribute, there is an outstanding request/suggestion by @thewtex:
We may want to encourage, i.e.
SHOULD, the use of.ome.zarrin the spec to improve awareness of OME-Zarr and be able to identify an OME-Zarr directly from a path / URL.
- Dominant language
- Python
- Stars
- 180
- Forks
- 81
- Avg merge
- 5d 7h
- Merged PRs (30d)
- 9
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from ome/ngff
-
leftover mention of `path` in v0.6 scale/translation transforms?Possibly taken @tlambert03 claimed this 1 day ago. Open0.6 post-release patch bug
Difficulty 1/5 Under an hour Newbie friendliness 72/100
ome/ngff#661 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
0.6 post-release patch bug
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
Maintainers usually reply within 1 day
-
should byDimension inputAxes/outputAxes be "integer" in the schemaPossibly taken @tlambert03 claimed this 1 day ago. Open0.6 post-release patch bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
0.6 post-release patch
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
ome/ngff#634 · 1 reaction · 1 assignee ·
Maintainers usually reply within 1 day
-
rfc-8
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
Similar issues
-
[BUG] HTTP lifecycle dispatch treats a NO_PROXY-only environment as corporate egress and skips the resolve-and-pinned sessionPossibly taken @bodapatisaikrishna claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
external
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
langchain-ai/docs#7652 ·
Maintainers usually reply within 1 day
-
[oblt-aw][autodoc] Document new e2e-secret-leak-artifacts workflow and update e2e-all leaf listOpen
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
elastic/oblt-aw#2513 · 1 comment ·
Maintainers usually reply within 1 day
-
bug p2
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 1/5 Under an hour Newbie friendliness 75/100
NCAR/CLM-Tutorial#113 · 1 comment ·
Maintainers usually reply within 1 day