Josh Moore

One json-ld based option which wouldn't break multiscales (though we might need to re-evaluate "label-image" and "plate") would be: ``` { "@context": "https://spec.openmicroscopy.org/v0.1", "@type": "Image", "@id": "https://s3.embassy.ebi.ac.uk/idr/zarr/v0.1/6001240.zarr", // or UUID?...

Though looking at `multiscales`, I imagine `rendering` should also be a list `Renderings`. cc: @will-moore @jburel

cc: @manzt @constantinpape

https://github.com/ome/ngff/blob/main/caniuse.md would be one option. Another might be https://nicolas-van.github.io/easy-markdown-to-github-pages/ :+1: for getting something in place ASAP. cc: @tischi

Agreed! Currently we are exporting the OMERO metadata in all of the IDR sample images. You can see what the metadata looks like in the spec: https://ngff.openmicroscopy.org/latest/#omero-md and sample code...

@d-v-b: is there one per channel? Otherwise, looks like there's a good deal of overlap. From https://ngff.openmicroscopy.org/latest/#omero-md: ``` "channels": [ # Array matching the c dimension size { "active": true,...

> Switching to the omero format is on my to-do list actually :+1: but is it worth simplifying the above before you do that? > It would also be interesting...

> https://github.com/ome/ngff/issues/23#issuecomment-788163198 I'd be up for making a spec proposal... how do we do that? The steps from my POV follow, but you can skip any of the former ones...

@d-v-b, does your :+1: on @constantinpape's summary mean that we can see this issue primarily as added discussion for #94 & #101? If so, do we need to keep it...

Would you consider https://github.com/ome/ngff/issues/22 ("Update label properties to include example: prefix") under this banner as well? Or does that count as a spec _change_ since we would basically be saying...