Mark Keller

Related to https://github.com/vitessce/vitessce/issues/656 and https://github.com/vitessce/vitessce/issues/135

## Proposal Goes along with #1128. ### Background / motivation Along with the `spatialRasterLayer` coordination type, we also currently have the two coordination types `spatialCellsLayer` and `spatialMoleculesLayer`. In #1209 I...

Relevant slides from my recent lab meeting presentation     

Related to #1089

Yes definitely would approve of this. If there is an easy way to do it via file:// URLs that would be nice but would also be open to filePath. I...

I previously thought about naming the object `entityTypes` but I think the more general `coordinationValues` name may be better, since we may need something like: ```js datasets: [ { uid:...

An alternative name which is shorter than `coordinationValues` is `match`, since it is kind of like pattern matching

For a more concrete example, the implicit schema does not generalize to per-spatialLayerType coordination mappings: See https://github.com/keller-mark/vitessce-fom-config-proposals/blob/496339ef7c91a0ee6fe271a2a7ec7fe3db7255c8/codeluppi.orig.json This is how it would look with the more explicit schema:

This is also related to https://github.com/vitessce/vitessce/issues/830

> So this issue is resolved by https://github.com/vitessce/vitessce/pull/1250? This PR is independent of #1250. > the above codeluppi example actually would not work unless you implemented a custom component for...