Merge remote-tracking branch 'upstream/main' into consolidate-version-history

Author: jo-mueller

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1 @@
+blank_issues_enabled: false

.github/ISSUE_TEMPLATE/issue.yml

@@ -0,0 +1,16 @@
+name: Issue
+description: Report an ngff-spec technical issue
+title: "[Issue]: "
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Note: spec-level considerations should usually go to https://github.com/ome/ngff/issues.
+        Please use this repo for typos, docs structure, or website/build issues.
+  - type: textarea
+    id: details
+    attributes:
+      label: Describe the issue
+      placeholder: Write your issue here...
+    validations:
+      required: true

index.md

@@ -78,6 +78,7 @@ Note that the number of dimensions is variable between 2 and 5 and that axis nam
     │   ...                   # which is a folder containing chunk files which compose the array.
     ├── n                     # The name of the array is arbitrary with the ordering defined by
     │   │                     # by the "multiscales" metadata, but is often a sequence starting at 0.
+    │   │                     # All arrays must have the same datatype and number of dimensions.
     │   │
     │   ├── zarr.json         # All image arrays must be up to 5-dimensional
     │   │                     # with the axis of type time before type channel, before spatial axes.
@@ -1262,7 +1263,7 @@ which is an array of objects describing the arrays storing the individual resolu
 Each object in `datasets` MUST contain the field `path`,
 whose value is a string containing the path to the Zarr array for this resolution relative to the current Zarr group.
 The `path`s MUST be ordered from largest (i.e. highest resolution) to smallest.
-Every Zarr array referred to by a `path` MUST have the same number of dimensions
+Every Zarr array referred to by a `path` MUST have the same number of dimensions and datatype,
 and MUST NOT have more than 5 dimensions.
 The number of dimensions and order MUST correspond to number and order of `axes`.
 

version_history.md

@@ -22,6 +22,7 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/).
 - style: Homogeneous use of backticks in spec document
 - specification: Changed the constraints for valid `path` values in `wells` for HCS plates to allow some non-alphanumeric characters.
 - specification: Corrected that `version` field is not required under plate/well/labels metadata. 
+- specification: Constrained datatype of multiscales datasets to be the same across all resolutions
 - style: Adopted JSON terminology for "object" and "array" in the spec document.
 
 ### Removed