Kris West

A few notes from meeting: - #596 Notes: - Would be great to see some JSON examples of a context container a rich text block. - This is a fairly...

Thanks @Yannick-Symphony this looks good. A couple of quick first thoughts: - I think you should add an entity for just a context (in addition to intent+context) as the API...

Hi @Yannick-Symphony, I think this is likely to come up again (on notifications), so perhaps we should create a full context type for an 'action', e.g.: ```js { type: "fdc3.action",...

@pgn-vole Is fdc3.getCurrentContext() a thing? I don't see it in the spec/docs. There is however fdc3.getCurrentChannel() and channel.getCurrentContext(); @rikoe Broadcasting null would/could work for channel.getCurrentContext(), but, as a channel retains...

As per comments on #361 we might be better served to create a `NullContext` context for this. We wouldn't have to change any API signatures, it has other potential uses...

Good point @pgn-vole, if you had added a typed context listener, e.g.: ``` const contactListener = fdc3.addContextListener('fdc3.contact', contact => { ... }); ``` then you would not receive the `NullContext`...

See #375 for the Null context type

A Standards Working Group vote is needed on this issue; there are two options to choose from, or the issue can be closed. ### Options 1. (🎉) Use the `fdc3.nothing`...

After the last SWG meeting (#459), and based on the informal votes received, it was decided to remove this issue from the FDC3 2.0 milestone - but not to close...

> FYI @kriswest we added the "intent" (which is actually an intent name + context) definition to the schemas (previously it was only in a [separate yaml](https://github.com/finos/FDC3/blob/master/src/intents/Intent.yaml)), so that we...