Kris West

The issue description is slightly conflating the API event [userChannelChanged event](https://fdc3.finos.org/docs/next/api/ref/Events#fdc3eventtypes) with the (related) DACP message that delivers it (from the DA to the app), [`ChannelChangedEvent`](https://fdc3.finos.org/schemas/next/api/channelChangedEvent.schema.json). The first thing we...

Do you want to try and fit in a quick a chat on this in today's meeting, or defer to a later one @robmoffat ?

Colour channels are a long established pattern in a multi-application environments in finance, enabling users to visually link windows they see on their desktop. All UIs I've seen demonstrated for...

P.S. I remember that we debated going with 6 or 8 channels when the recommend set was established. It was decided that we would go with 8 for future proofing...

There is more detail on the discussions around the recommended channel set in: - the issue: #717 - the PR: #727 - Bridging discussion group meeting minutes, including at least:...

> So clearly some earlier thought existed around making this configurable too? Yes, but configurable was intended to mean offline / read on or during start-up of the environment, rather...

@robmoffat I think we probably do need to vary the `type` value for different CDM schemas, rather than just expressing that its a CDM model. Granted you could just listen...

>data... or can someone think of a better name for the container? How about just `cdm`? >I think it would be also useful to include some kind of schema reference...

P.S. schemas not living at their $id URLs is inconvenient, but doesn't prevent and isn't required: > Common Pitfall > In JSON Schema, schema identifiers are merely identifiers and no...

Edited - the release to NPM should happen from the release tag itself (so the SHA of the release points to exactly whats in the corresponding NPM packages) rather than...