Trevor Manz

Thanks for looking into this! This definitely makes sense to me to provide defaults in `omexml.ts`. https://github.com/hms-dbmi/viv/blob/master/src/loaders/omexml.ts I think in general `omexml.ts` could be improved by thoroughly looking into the...

> How to validate config when everything comes from plugins. Should all fileType plugins need to provide partial schemas if they support non-standard `options`, and coordinationType plugins providing schemas for...

A recommendation before going this route: reserve org scope on npm (e.g., `@vitessce`) before refactoring everything. I just found out `@viv` is taken and had to do a large find...

Nice! Also npm organizations are allowed to publish non-scoped packages as well (that's the default), it's just the org `vitessce` is the only entity which can publish under the `@vitessce/*`...

I'll have a look at this today. Sorry for the delay

I have the same rankings as Jackson. With regard to Option 5, I kind of think the `store` itself captures the idea of a `File` object in Zarr, it's just...

It should be straightforward to find and return this metadata for OME-NGFF once a format/location are decided on. As it stands, Viv is fairly unopinionated about _what_ the metadata is;...

Agreed, great idea! This table is already useful to point to (and have the information collected). I especially like how the links in the table above provide a nice preview...

demo: https://deploy-preview-80--vizarr.netlify.app/?source=https://s3.embassy.ebi.ac.uk/idr/zarr/v0.1/plates/2551.zarr

> Certainly for the whole plate demo, the zooming is a bit painful compared to the current viewer. Which is a shame as the functionality of loading higher resolution tiles...